Oracle 1z0-1057-24 Online Access

To perform revenue recognition based on the Labor and Non-labor Burden schedule types, you need to create a revenue method with a revenue method classification of Rate Based. This classification allows you to use the burdened cost rates of labor and non-labor resources as the basis for revenue recognition. The burdened cost rates are derived from the burden schedules that are assigned to the project or task. Reference:

Ref: tml#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.

Ref:

How can I validate distribution sets for projects information?

Oracle Fusion Projects performs validations on Oracle Fusion Payables distribution sets for payables invoices at the time you create the actual distribution set lines. It validates the project and task number during the invoice validation.

Distribution sets are typically used on recurring transactions, and the associated project does not have transaction controls.When you create a distribution set in Oracle Fusion Payables, the distribution set line is not validated against the project transaction controls in Oracle Fusion Projects because you do not enter anexpenditure item date, which is required for transaction control validation.The expenditure item date is not provided because you use the distribution sets for an indefinite period of time.

Reference

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.