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

To enable a task as a business object for social networking, you need to select the task and the project attributes. These attributes allow you to identify the task and the project it belongs to, and to view the social conversations related to them. Task number and creation date are not available as attributes for social networking. Project number is available, but it is not required to enable a task as a business object. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-tasks.html#OAPFM2355891

Rapid Implementation for Project Financial Management Applications allows you to configure some common setups for project costing and billing using predefined templates and spreadsheets. Some of the setups that can be configured using Rapid Implementation are expenditure types, project templates, and project types. Work types and project class categories are not part of Rapid Implementation. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/implement-project-financial-management-applications.html#OAPFM2355871

Reference https://docs.oracle.com/en/cloud/saas/applications-common/19b/facia/define-enterprise-structures.html#FACIA462453 Reference Data Sharing Methods Variations exist in the methods used to share data in reference data sets across different types of objects. The following list identifies the methods:
Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate Conventions are defined and assigned to only one reference data set. This set can be shared across multiple asset books, but all the values are contained only in this one set.
Assignment to one set only, with common values. This method is the most commonly used method of sharing reference data that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are assigned to a common set that is available to all the business units. You need not explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specific set of transaction types. At transaction entry, the list of values for transaction types includes the following:
Transaction types from the set assigned to the business unit.
Transaction types assigned to the common set that is shared across all business units.
Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this method. It means that each payment term can be assigned to one or more than one set. For example, you assign the payment term Net 30 to several sets but assign Net 15 to a set specific only to your business unit. At transaction entry, the list of values for payment terms consists of only the set that is assigned to the transaction's business unit.
Note: Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects your entire enterprise in this set. Also update the data set going forward as you create new reference data items.

When an invoice is entered with an invoice date in the open project accounting and closed accounting periods, the accounting date is the same as the original invoice date, but the project accounting date is the first day of the first open project accounting period. This ensures that the invoice is accounted in the correct accounting period and recognized in the correct project accounting period. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-invoices.html#OAPFM2355911