Complete 1z0-1057-24 Oracle Materials

To access transactions for a business unit, the project accountant needs to be assigned to an external role that grants access to that business unit. The external role is defined by the security profile of the business unit and can be different for each business unit. The job role and the legal entity are not relevant for accessing transactions for a business unit. The ledger is relevant for accounting transactions, but not for project transactions.Reference:

The borrowed and lent cross charge method is a method that allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger. This method does not generate internal invoices or intercompany accounting entries for cross charge transactions. Instead, this method creates accounting entries that move an amount equal to the transfer price between the provider and receiver organizations using borrowed and lent accounts. Two statements that are true about this method are:

Internal Invoice is not generated with this method. This method does not create internal invoices for cross charge transactions, as these transactions are accounted within the same primary ledger using borrowed and lent accounts.

This method allows you to process cross charge transactions across legal entities. This method allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger, as long as they share the same chart of accounts, calendar, currency, and subledger accounting method.

Reference cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM1125357

Assignment of Supporting References

Supporting references may be used to capture transaction values on journal entry lines. A supporting reference can be used on a journal entry rule set only if it's assigned a source from the event class of the journal entry rule set.

Creating Supporting References: Explained

Supporting references are used to store additional source information about a subledger journal entry at the line level.

Supporting references with balances establish subledger balances for a particular source and account for a particular combination of supporting references plus the account combination.

For example:

If a journal line contains a supporting reference that includes two sources, Customer Type and Customer Name.

Balances are created for the account combination, plus customer name and customer type.

Examples of how you may want to use supporting reference balances are to:

Facilitate reconciliation back to the subledgers and source systems by tagging journal entries with transaction and reference attributes.

Create balances by dimensions not captured in the chart of accounts.

Reporting using dimensions not captured in the chart of accounts.

Enrich Oracle Fusion Business Intelligence Applications reporting on subledger journals.

Profit and loss balances by dimensions not captured in the chart of accounts

Define supporting references to hold additional supporting information for detailed account balancemaintenance or reconciliation and reporting requirements.

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: