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. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio- management/20c/oapfm/set-up-project-financial-management.html#OAPFM2355971

Reference: https://fusionhelp.oracle.com/helpPortal/topic/TopicId_P_87F467307D50416BE040D30A68816855 Spread curves let you distribute quantity, cost, and revenue amounts automaticallyacross accounting or project accounting periods. You assign a spread curve to each resource class. Planning resources (in the planning resource breakdown structure) inherit the spread curve setting from the associated resource class.
You can change the spread curve for the planning resource and for any corresponding task assignments, or budget or forecast lines.

To sell items not tracked in inventory, inventory items, and services, you can create two contract lines with different line types. The line type of "sell intent, free-form, project-based" allows you to sell any item or service without specifying the item number or quantity. The line type of "sell intent, item, project-based" allows you to sell inventory items by specifying the item number and quantity. Both line types are project- based, meaning they are linked to a project and generate revenue based on project performance.Reference:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-contracts.
html#OAPFM2355835

According to Oracle sources1, the inheritance between requirements, tasks, and deliverables works as follows:
* You can associate a deliverable with a task independent of associating a requirement with a task. You can also associate a deliverable with a requirement independent of associating a task with a requirement
1.
* A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. You must manually associate the deliverable with the tasks that produce it1.
Therefore, the correct answer is B and D.
1: Can deliverables for projects and tasks be inherited from associated requirements? - docs.oracle.com (index
1)
In Oracle Project Management, you can define requirements, tasks, and deliverables for your project based on your project methodology and lifecycle. Requirements are statements of needs or expectations that must be met by the project outcome. Tasks are units of work that must be performed to complete the project.
Deliverables are products or services that are produced or provided as part of a task or requirement. Two correct statements about how the inheritance between requirements, tasks, and deliverables works are:
* You associate a deliverable with a task independent of associating a requirement with a task. This means that you can create a deliverable for a task regardless of whether the task is linked to a requirement or not.
* A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. This means that you have to manually associate a deliverable with a task even if both the deliverable and the task are linked to the same requirement.

Budget 5,000Actuals 800Commitment 600
ETC = Budget - Actuals - Commitment
ETC = 5,000-800-600 = 3,600 Budget available for next 4 months = 3,600/4 = 900/month