Reference https://docs.oracle.com/cloud/latest/projectcs_gs/OAPFM/OAPFM1125361.htm#OAPFM1125277 (what's a work type?) In billing, you can use work types to classify work for the following purposes:
To determine the default billable status of expenditure items.
To classify cross-charge amounts into cost and revenue for cross-charge transactions.
Tip: To use work types to determine whether an expenditure item is billable you must set the profile option Work Type Derived for Expenditure Item to Yes.
When you create or import expenditure items, the default work type is inherited from the associated task. Tasks, in turn, inherit work type values from parent tasks and ultimately from the project. Project types determine the default work type value for projects and project templates.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapjf/define-project.html#OAPJF220111 Asset Cost Allocation Methods 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 Asset Cost Allocation Methods 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

Reference https://docs.oracle.com/cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM1125357 Assignment of Supporting Reference 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 Reference: 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/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

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/faopm/subjectareas.html#Projects__Cross_Subject_Area_Analysis__Real_Time_SA_20 Analyze real-time information on project performance, including budgets, forecasts, costs, commitments, revenue, and invoices.
This subject area analysis allows cross subject area analysis between Funding, Invoices, Revenue, Budget, forecasts, Costs areas.