New Features and Functions in Oracle EBS R12 Financials

 Ledgers and Legal Entities

In Oracle EBS 11i GL is configured to support one or many Legal Entities. 11i OU’s are associated with these Legal Entities through Oracle Sets of Books. The Set of Books is the structure defined by the famous 3 C’s in (driven by Oracle GL configuration) – Chart of Accounts, Currency, Calendar.
In R12 the concept of Ledgers and Ledger Sets replaces Sets of Books. Ledgers are now associated with 4 C’s – Chart of Accounts, Currency, Calendar, *Accounting Convention.  R12 Ledgers now associate Oracle OU’s to Oracle Legal Entities. The advantage here is that a ledger can be used to post transactions in one or many Legal Entities originating from a single transaction. Additionally, this single transaction can drive subsequent entries/transactions into various Legal Entities, OUs, Primary and Secondary Ledgers by configuring and utilizing “Accounting Setup Manager”
*Note: The concept of accounting conventions indicates the accounting standards your company follows, for example, International Accounting Standards (IAE), International Financial Reporting Standards (IFRS), USGAAP, etc.

Subledger Accounting (SLA)

In 11i Oracle Subledgers such as Projects, Receivables and Payables offer functionality to configure how
Oracle generates the values for each accounting segment in the Chart of Accounts. This configuration depends on variables such as, the type of transaction, the organization where the transaction originates, and/or the product or service for which revenue/cost will be accounted for. Once accounting rules are defined for each subledger, Oracle will post the transaction directly to GL without an opportunity to modify, split or change the accounting beforehand. This problem is now solved in R12 using Subledger Accounting (SLA). Oracle Subledger accounting (SLA) is essentially an accounting hub. It is used to derive all attributes required to account for a transaction in Oracle General Ledger. In R12, SLA is used to derive the very basic accounting attributes such as entered amount, accounted amount, date, currency code etc., along with complex attributes like Ledger, Code Combination ID, Periods. After
deriving these accounting attributes the transactions are moved to GL from SLA.  Thus in R12 subledgers transactions do not move directly to GL without passing first through SLA. SLA provides flexibility to manage the entire accounting rule from a single place and establishes a single source of truth for GL.