Ref: Implementing-Project-Financial-Management-and-Grants-Management.pdf Chapter 3 - Define Project Organizations Page # 12 Topic - Selecting Organization Hierarchies for the Business Unit The following conditions are required for an organization to be eligible to be a project expenditure organization:
You must assign the Project Expenditure Organization classification to the organization.
The organization must belong to the hierarchy that you specify in the project implementation options for the business unit.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapjc/allocate-project-costs.html#OAPJC94831 Spread Evenly The allocation rule divides the source pool amount equally among all the chargeable target tasks included in the rule. This is the most simple and direct basis method.
Target Percentage and Spread Evenly
Specify the percentage of the source pool that is required to allocate to each target line. The total specified target percentage must always equal 100 percent. The allocation rule calculates the amount to allocate to the target line, and then spreads the results evenly among the chargeable tasks.
Prorate
The allocation generation uses the attributes defined in the allocation rule to derive the rate at which the source pool amount is apportioned among the target projects and tasks. For this basis method, the allocation rule uses the basis attributes to apportion the source amount among all the tasks defined by the rule. The Prorate basis method provides precise control over how the rule distributes the source pool.
Target Percentage and Prorate
The allocation rule first uses the target percentage to calculate the amount to allocate to the line, and then apportions the results among all the tasks. The Target Percentage and Prorate basis method provides precise control over how the rule distributes the source pool.

Reference https://docs.oracle.com/cloud/latest/projectcs_gs/FAPFM/FAPFM1192914.htm Topic - Creating Calendars for Projects and Resources: Procedure Project Schedules are used as a base for project and resource calendars in Project Execution Management applications. The smallest scheduling unit is a day. For example, you can define the number of hours in a day but, you can't schedule work for a specific time of the day.
The following are the elements of a schedule:
Shifts
Workday patterns
Exceptions

Reference https://docs.oracle.com/cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM1125357 Assignment of Supporting References Supporting references may be used to capture transaction values on journal entry lines. A supporting reference can be used on a journal entry rule set only if it's assigned a source from the event class of the journal entry rule set.
Creating Supporting References: Explained
Supporting references are used to store additional source information about a subledger journal entry at the line level.
Supporting references with balances establish subledger balances for a particular source and account for a particular combination of supporting references plus the account combination.
For example:
If a journal line contains a supporting reference that includes two sources, Customer Type and Customer Name.
Balances are created for the account combination, plus customer name and customer type.
Examples of how you may want to use supporting reference balances are to:
Facilitate reconciliation back to the subledgers and source systems by tagging journal entries with transaction and reference attributes.
Create balances by dimensions not captured in the chart of accounts.
Reporting using dimensions not captured in the chart of accounts.
Enrich Oracle Fusion Business Intelligence Applications reporting on subledger journals.
Profit and loss balances by dimensions not captured in the chart of accounts Define supporting references to hold additional supporting information for detailed account balance maintenance or reconciliation and reporting requirements.

Reference https://docs.oracle.com/cloud/latest/projectcs_gs/FAPFM/FAPFM1225328.htm