Budget 5,000Actuals 800Commitment 600

ETC = Budget – Actuals – Commitment

ETC = 5,000-800-600 = 3,600 Budget available for next 4 months = 3,600/4 = 900/month

Application Composer is a tool that allows you to configure standard objects or create custom objects to include business specific attributes for Project Execution Management. Four of the standard objects that you can configure using Application Composer are:

• Project Gates: These are checkpoints that mark the completion of a phase or stage in a project lifecycle.
• Project Issues: These are problems or risks that affect the progress or outcome of a project.
• Project Milestones: These are significant events or achievements that indicate the status or completion of a project or task.
• Project Deliverables: These are products or services that are produced or provided as part of a project or task. Project Resource Request and Project Resource Assignment are not standard objects that you can configure using Application Composer. These are features that allow you to request and assign resources for projects and tasks based on various criteria such as availability, qualifications, preferences, etc. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356201

To handle a custom spread on budgets and forecasts, you can either create a new spread curve or edit an existing one to match the desired spread points. Then, you can attach the spread curve to a project template or a resource class, depending on whether you want to apply it to all projects using that template or all transactions using that resource class. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/define-project-budgets-and-forecasts.html#OAPFM2355819

Ref: https://docs.oracle.com/cd/E48434_01/fusionapps.1118/e49622/F1125394AN6D254.htm

Primavera P6 Enterprise Project Portfolio Management and Oracle Fusion Project Portfolio Management: How They Work Together

Use Oracle Fusion Project Integration Gateway to integrate Oracle Fusion Project Portfolio Management with Primavera P6 Enterprise Project Portfolio Management. The integration enables project accountants, project billing specialists, and executives to centrally perform project costing, billing, accounting, and executive reporting tasks in Oracle Fusion Project Portfolio Management while enabling each project manager to perform detailed project planning and scheduling in Primavera P6 Enterprise Project Portfolio Management.

Oracle Fusion Project Integration Gateway ensures data security, integrity, and efficiency by defining a set framework in which data is exported from and imported into Oracle Fusion Project Portfolio Management.

The following table and diagram provide an overview of the flow of information.

Information Type

From Application

To Application

Global integration information

Oracle Fusion Project Portfolio Management

Primavera P6 Enterprise Project Portfolio Management

Projects and task definition

Oracle Fusion Project Portfolio Management

Primavera P6 Enterprise Project Portfolio Management

Summarized project actual quantity and cost

Oracle Fusion Project Portfolio Management

Primavera P6 Enterprise Project Portfolio Management

Project plans and progress

Primavera P6 Enterprise Project Portfolio Management

Oracle Fusion Project Portfolio Management

Billing events

Oracle Fusion Project Portfolio Management

Primavera P6 Enterprise Project Portfolio Management

Event completion

Primavera P6 Enterprise Project Portfolio Management

Oracle Fusion Project Portfolio Management

Project gate statuses are values that indicate the progress or completion of a project gate. A project gate is a checkpoint that marks the end of a phase or stage in a project lifecycle. Three of the project gate statuses are:

• Open: This status indicates that the project gate is not yet ready for review or approval.
• In Review: This status indicates that the project gate is under review or approval by the gate reviewers or approvers.
• Closed: This status indicates that the project gate has been reviewed or approved and the project can move to the next phase or stage. Approve and Draft are not project gate statuses, but actions that can be performed on a project gate. Approve is an action that allows a gate approver to approve a project gate and change its status to Closed. Draft is an action that allows a gate owner to create or edit a project gate and change its status to Open. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356251

The source that can be used while defining the account rule to achieve this requirement is Expenditure Organization Cost Center Segment. This source allows you to retrieve the value of the cost center segment based on the expenditure organization of the transaction. The expenditure organization is an attribute of a transaction that represents the organization that incurs or owns the cost of the transaction.

Reference https://docs.oracle.com/cd/E51367_01/projectop_gs/OAPJB/F1087458AN139C2.htm

Topic – Invoice and Revenue Rates: How They Are Determined

Oracle Fusion Project Billing uses bill rates, burdening, and transfer price schedules to derive standard bill rates, multipliers, markups, and bases for calculating potential revenue when the revenue method classification on a revenue plan is as billed, as incurred, or rate based. Similarly, bill rates derive invoice amounts when the invoice method classification on a bill plan is rate based.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oefpp/toc.htm

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio- management/19a/fapfm/introducing-oracle-project-portfolio-management-cloud-services.html#FAPFM428138

Topic - Project Foundation Profile Options

Profile Option Name - Task Managers Must Be Project Team Members

Description - Specify whether task managers must be project team members.

Values – No (Default) / Yes

Setup Task Name - Require Task Managers to be Project Team Members

To enable a task as a business object for social networking, you need to select the task and the project attributes. These attributes allow you to identify the task and the project it belongs to, and to view the social conversations related to them. Task number and creation date are not available as attributes for social networking. Project number is available, but it is not required to enable a task as a business object. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-tasks.html#OAPFM2355891

Reference https://ppm-help.saas.hpe.com/en/9.42/Help/Content/UG/PjMUG/view_pj_cost_data_costtab.htm

Below is an example of the Financial Summary view on the Cost tab of the Project Overview page.

https://admhelp.microfocus.com/ppm/en/9.42/Help/Content/UG/PjMUG/images/ProjectOverviewPage_CostTab.gif

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-pr oject-financial-management-applications.html#FAPFM969761

Topic - Entering Planning Resource Breakdown Structure Details

• Click Navigator > Setup and Maintenance, and search for the Manage Planning and Billing Resource Breakdown Structures task.
• Click the Manage Planning and Billing Resource Breakdown Structures link.

Use the Manage Planning and Billing Resource Breakdown Structures page to create new planning resource breakdown structures and to review existing planning and billing resource breakdown structures.

• Click the Create icon in the Planning Resource Breakdown Structures section.
• Use the Create Planning Resource Breakdown Structure: Basic Information page to provide basic resource breakdown structure information including the name, active dates, and project unit.
• Enter a planning resource breakdown structure name and select a date from which the resource breakdown structure is available for use.
• Optionally, provide a description and a date to which the planning resource breakdown structure is available for use.
• Select a project unit. Only projects created for the selected project unit can use this planning resource breakdown structure.
• If you want to allow project managers to add planning resources at the project level, then select the Allow resource changes at project level check box.

Tip: Changes at the project level don't move back to the parent planning resource breakdown structure. Deselect this option to ensure all project using the planning resource breakdown structure use the same resources.

• Optionally, select a Job Set as a source of jobs for creating planning resources on your planning resource breakdown structure.
• Click Save.

Reference https://docs.oracle.com/cd/E37583_01/doc.1116/e22598/F45890 0AN13D82.htm

How Resource Mapping Is Calculated

You can track the cost impact of every resource that has been assigned to a project task and use the resource breakdown structure to view the breakdown of these costs. Oracle Fusion Projects associates the costs of the resources used for tasks with branches and levels in the resource breakdown structure. The process for determining the correct association is managed by rules of precedence.

Oracle Fusion Projects uses the following rules to associate cost amounts with resources:

• Select the lowest level in the resource breakdown structure to which a transaction can map.
• If there is only one level to which the transaction maps, the cost amounts are mapped to that level.
• If the transaction maps to more than one level, Oracle Fusion Projects sums the precedence numbers for all resource types in the branch and gives precedence to the resource element in the branch with the lowest sum.
• If more than one branch has the lowest precedence number at the lower level, the application uses the precedence number of the next level up.
• If the sum of precedence numbers is the same for more than one branch, precedence is given to the branch with the lowest number at the lowest level.
• If one branch contains a user-defined resource type, precedence is given to the branch that does not contain a user-defined resource type.

Note Oracle Fusion Projects gives more precedence to a lower precedence number. For example, a resource element with a precedence number of 1 is given precedence over a resource element with a precedence number of 10.