11g Release 7 (11.1.7)
Part Number E37979-01
Home
Contents
Book
List
Contact
Us
|
Oracle® Fusion Applications Project Execution Management Implementation Guide 11g Release 7 (11.1.7) Part Number E37979-01 |
Home |
Contents |
Book List |
Contact Us |
 Previous |
 Next |
This chapter contains the following:
FAQs for Manage Project Management Implementation Options: Default Calendar
FAQs for Manage Project Management Implementation Options: Progress Thresholds
Manage Enterprise Project and Task Codes
Define Project Requirement Configuration
Project calendars determine standard working and nonworking times for resources working on projects. For example, a project calendar can designate the total number of working hours per day and any holidays that occur during the project dates. A project calendar is used to schedule project tasks, and to estimate project duration.
Resource calendars determine the total available working hours for resources.
Note
Your implementation team defines the default project and resource calendars that are automatically assigned to new projects and resources. However, a project manager can assign another calendar to a project. Similarly, a project application administrator can assign a different calendar to a resource.
Yes. On the Define Project Management Implementation Options page, you select a default resource calendar that the application automatically assigns to new project enterprise labor resources. If the default resource calendar does not meet the requirements for a specific project enterprise labor resource, then you can assign a different calendar to the resource.
A team member entered a proposed start date, proposed finish date, or an increase to the planned hours for the task that exceeds the progress thresholds entered on the Define Project Management Implementation Options page.
Project codes and task codes enable you to capture information at the project and task level that is specific to your organization.
Create project and task codes based on one of the following data types to determine how project managers and project team members enter information.
Value sets
Free form text
Numeric
Define up to 40 project or task codes based on value sets. When you define a value set, enter at least one value for project managers and team members to select when they create projects or tasks. You can specify a sequence for the values to appear in a specific order.
Define up to 20 text fields to enable users to enter alphanumeric information for project or task codes.
Define up to 10 project or task codes that allow entry of numeric information.
You cannot assign the same code to both project and task codes. After you use a code at the task level, you cannot use it at the project level.
Requirements enable you to analyze, define, track, and prioritize the intended outcomes of a successful project.
The following aspects are important regarding project requirements:
Creating Requirements
Importing Requirements from Excel
Create requirements using the three-level requirement hierarchy that consists of investment area, feature, and backlog item by default.
Note
Names of requirement levels can be changed during implementation.
Create requirements at different levels to focus planning, review, and execution of project work. For example, you can associate requirements with sprints when development will take place, or what the priority of a requirement is. You can also create project tasks based on lowest-level requirements called backlog item by default.
Use desktop integration for Excel to create requirements in a spreadsheet and export the requirements to Oracle Fusion Project Management.
Note
You cannot edit and then export existing requirements from Excel. Use the Manage Requirements page to edit requirements.
You can only create backlog items, the lowest-level requirements, for the project plan.
