Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-foundation-configuration-define-types-and-categorizations.html#OAPFM222700 Topic - Manage Project Class Categories Setting Up Class Categories: Points to Consider Available as Accounting Source This option indicates if the class category is available as an accounting source so that Oracle Fusion Subledger Accounting can use the category to create mapping sets, account rules, journal line rules, and description rules.
Only one class category at a time is available as an accounting source in Oracle Fusion Subledger Accounting. To change the class category that Oracle Fusion Subledger Accounting uses, deactivate the old class category and create a new one with a different date range.

Selecting the offering you want to implement and enabling optional functional areas and features by opting in are not part of managing an implementation project. These are part of configuring an implementation project, which is done before managing an implementation project. Configuring an implementation project allows you to define the scope and features of your implementation based on your business needs. Managing an implementation project involves assigning tasks to various users who are responsible for managing setup data, monitoring the progress of completing setup tasks, and generating a list of setup tasks. These are part of executing an implementation project, which is done after configuring an implementation project. Executing an implementation project allows you to perform the setup tasks and validate the setup data for your implementation. https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/implement-project-financial-management-applications.html#OAPFM2356021

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapfm/project-foundation-configuration-manage-project-types.html#OAPFM220111 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

Project type is a classification that defines the common attributes and processing options for projects. Some of the correct statements about project type are:
Project type can be used as a source in subledger accounting. This allows you to create accounting rules based on the project type attribute.
Summarization options can be specified at project type. This allows you to control how the project transactions are summarized for reporting and performance purposes.
Project type can be associated with multiple project units. This allows you to share the same project type across different business units or organizations. Project type cannot be enabled for both billing and capitalization, as these are mutually exclusive options. Classifications cannot be assigned at project type, but at project or task level. https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/set-up-project-financial-management.html#OAPFM2355971

Reference https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-control-configuration-manage-financial-and-project-plan-types.html#OAPFM79055 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.