Explanation
Reference
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-control-configuration-ma Topic - Project Date Cascade Options Use the Cascade option choice list to determine whether your changes to project dates cascade to tasks.
Use the Basic Information region on the Edit Project Template page to select one of the following options:
* Do not cascade project date changes to tasks: Both start and finish dates are editable. However, you must ensure the following:
* The project start date is not later than the earliest task date.
* The project finish date is not earlier than the latest task date.
* Cascade project start date change to affected tasks: You can edit only the project start date.
* Cascade project finish date change to affected tasks: You can edit only the project finish date.
Do not cascade project date changes to tasks is the default value. You must select the cascade option each time you change the project dates, as your selection isn't saved for future date changes.
If you select to roll up planned dates for tasks or are using an external application for scheduling, then you can't modify the project start or finish dates.

Explanation
Ref:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-project-financial-m 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 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.

Explanation
Reference
https://docs.oracle.com/en/cloud/saas/applications-common/r13-update17d/faser/implementing-security-in-oracle Ref to "Securing Project Financial Management and Grants Management Applications" Table lists predefined enterprise roles and the type of security that grants the role access to data in a work area or dashboard.
Enterprise Role
Work Area or Dashboard
Data Security Based On
Project Accountant
Asset
Project business unit
Project Accountant
Costs
Project expenditure business unit
Project Accountant
Revenue
Contract business unit
Project Administrator
Project Financial Management
Project business unit
Project organization
Project Billing Specialist
Invoices
Contract business unit
Project Creator
Project Financial Management
Project business unit
Project organization
Project Management Duty
Project Management Infolet Dashboard
Project assignment
Project Management Duty
Project Performance Dashboard
Project assignment
Project Manager
Project Management Infolet Dashboard
Project assignment
Project Manager
Project Performance Dashboard
Project assignment
Project Manager
Project Management
Project assignment
Project Manager
Project Manager Dashboard
Project assignment
Project Team Member
Project Financial Management
Project assignment
Grants Accountant
Invoices
Contract business unit
Grants Accountant
Revenue
Contract business unit
Grants Administrator
Awards
Contract business unit
Grants Administrator
Contracts
Contract business unit
Grants Administrator
Project Financial Management
Project business unit
Principal Investigator
Awards
Award assignment
Principal Investigator
Contracts
Award assignment
Principal Investigator
Project Financial Management
Project assignment

Explanation
Ref:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapfm/project-foundation-configuration Topic - Asset Cost Allocation Methods: Explained The asset cost allocation method determines how indirect or common costs incurred on a project are allocated to multiple assets.
You can specify an asset cost allocation method to enable Oracle Fusion Project Costing to automatically allocate unassigned asset lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned to an asset grouping level.
Projects and project templates inherit a default asset cost allocation method from the associated project type.
You can override the default at the project level. If you use capital events to allocate costs, then you can also override the asset cost allocation method at the event level.
The following table describes the available asset cost allocation methods.
Method
Basis of Cost Allocation
Actual Units
Number of units defined for each asset
Current Cost
Construction-in-process (CIP) cost of each asset
Estimated Cost
Estimated cost of each asset
Standard Unit Cost
Combination of the standard unit cost and the number of units defined for each asset Spread Evenly Equal allocation of cost to each asset