Explanation
Reference
http://www.oracle.com/us/products/applications/fusion/fusion-proj-port-mang-solut-brief-173079.pdf (Page 2) Flexible Contract-Based Billing Traditional contract and billing systems enforce a rigid relationship between a project and a funding agreement, which can constrain project setup and execution. Oracle Fusion Project Portfolio Management provides a highly flexible approach to project contract-based billing via a non-exclusive relationship between multiple projects and tasks with contracts and contract lines. This means that you will have full control over defining contracts, rates and limits, and when and how to recognize revenue and generate invoices while segregating the planning and execution of your projects.

Explanation
Reference https://docs.oracle.com/cd/E51367_01/projectop_gs/OAPJB/F1087458AN139C2.htm Topic - Invoice and Revenue Rates: How They Are Determined Oracle Fusion Project Billing uses bill rates, burdening, and transfer price schedules to derive standard bill rates, multipliers, markups, and bases for calculating potential revenue when the revenue method classification on a revenue plan is as billed, as incurred, or rate based. Similarly, bill rates derive invoice amounts when the invoice method classification on a bi

Explanation
Reference https://docs.oracle.com/cd/E51367_01/projectop_gs/OAPJC/F1071488AN1004C.htm

Explanation
Reference
https://docs.oracle.com/en/cloud/saas/applications-common/19b/facia/define-enterprise-structures.html#FACIA4 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.