Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapem/analyze-project-management-performance.html#OAPEM1313471 Topic - Project Labor Demand: How It's Calculated Settings That Affect Project Labor Demand Project application administrators must do the following to set up how project labor demand is calculated:
Organize projects into hierarchical groups on the Manage Enterprise Project Structure page.
Change the quarterly FTE hours for the organization on the Define Project Management Implementation Options page, if different from 520 hours.
Note: You can choose to view labor demand annually instead of quarterly. The Project Hierarchy Viewer uses the current date to determine which year or quarter to display.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-project-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 http://www.oracle.com/us/products/applications/fusion/fusion-proj-port-mang-solut-brief-173079.pdf (Page 2) Flexible Contract-Based Billing Traditional contract and billing systems enforce a rigid relationship between a project and a funding agreement, which can constrain project setup and execution. Oracle Fusion Project Portfolio Management provides a highly flexible approach to project contract-based billing via a non-exclusive relationship between multiple projects and tasks with contracts and contract lines. This means that you will have full control over defining contracts, rates and limits, and when and how to recognize revenue and generate invoices while segregating the planning and execution of your projects.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oefpp/overview.html#External_Data_Integration_Services_for_Oracle_Cloud_Overview

Reference https://docs.oracle.com/cloud/farel9/projectcs_gs/FAUAR/F1537947AN10251.htm