Deep dive into Subledger Accounting: ADRs, JLTs, AADs, and Custom Sources.
Subledger Accounting (SLA) is the central accounting engine in Oracle. It sits between subledgers (AP, AR, FA, INV) and the General Ledger (GL). Instead of subledgers generating their own accounting and sending it directly to GL, they send "Events" to SLA. SLA then applies custom-defined rules to generate the actual Debits and Credits before transferring them to GL.
You must know your GL flexfield structure to write rules that target specific segments (e.g., overriding the Cost Center segment).
Understand exactly WHY standard accounting is failing. (e.g., "When AP invoice is for supplier XYZ, charge to account 5000").
Technical/Functional Consultant
Technical/Functional Consultant
Technical/Functional Consultant
Technical/Functional Consultant
Technical/Functional Consultant
Technical/Functional Consultant
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
Whenever a transaction happens in a subledger (e.g., an AP Invoice is Validated), the subledger creates an "Event" in the SLA tables. This event acts as a trigger for the "Create Accounting" program.
Example: Validating an AP Invoice creates an event in XLA_EVENTS with event_type_code = 'INVOICE_VALIDATED'. SLA sees this event and knows it needs to generate accounting for it.
Navigation Path:
Setup and Maintenance > Manage Subledger Accounting Rules > Event Classes
Key Actions:
The Event Model is pre-seeded by Oracle and generally should not be modified.
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
Sources are the raw data elements pulled from the subledger transaction. If you want to base an accounting rule on the "Supplier Type" or "Project Number", that data must be defined as an SLA Source.
Example: To override a GL account based on the PO Line Category, ensure "Purchasing Category" is available as an SLA Source for the AP Invoice Event Class.
Navigation Path:
Setup and Maintenance > Manage Subledger Application Transaction Objects
Key Actions:
Fusion allows the use of Mapping Sets or extending the transaction objects if a field is missing.
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
An ADR (Account Derivation Rule) tells SLA HOW to build the GL Account string. You can use an ADR to derive the entire account combination, or just a single segment (like overriding only the Cost Center).
Example: Create an ADR named "Custom_IT_Cost_Center". Rule logic: IF Supplier Type = "IT Vendor", THEN return "500" (the IT Cost Center value).
Navigation Path:
Setup and Maintenance > Manage Account Rules
Key Actions:
In Fusion, these are called "Account Rules". You can also use Mapping Sets to map source values directly to GL segment values without complex IF/THEN logic.
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
A Journal Line Type (JLT) represents a specific Debit or Credit line in the resulting journal entry. For example, "Item Expense" or "Liability". You define the Side (Dr/Cr) and attach your ADRs to the JLT.
Example: Copy the standard "Item Expense" JLT. Attach your new "Custom_IT_Cost_Center" ADR to the Cost Center segment of this JLT.
Navigation Path:
Setup and Maintenance > Manage Journal Line Rules
Key Actions:
In Fusion, these are called "Journal Line Rules".
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
A Journal Lines Definition groups your Journal Line Types (JLTs) together for a specific Event Class. It defines the complete balanced journal entry (the Debits and Credits together).
Example: Create a new JLD for "Invoices". Add your custom "Item Expense" JLT (Debit) and the standard "Liability" JLT (Credit) to this definition.
Navigation Path:
Setup and Maintenance > Manage Subledger Journal Entry Rule Sets
Key Actions:
In Fusion, this is called a "Subledger Journal Entry Rule Set".
Actor: Technical/Functional Consultant | Module: Subledger Accounting (SLA)
The AAD groups multiple JLDs together for a specific subledger (e.g., Payables). The AAD is then attached to a Subledger Accounting Method (SLAM), which is assigned to your Primary Ledger.
Example: Assign your new AP Invoices JLD to your custom AAD. Then attach this AAD to your Ledger's Accounting Method. Finally, run the "Validate Application Accounting Definitions" program to compile the rules.
Navigation Path:
Setup and Maintenance > Manage Accounting Methods
Key Actions:
In Fusion, you activate the Accounting Method, which automatically compiles the rules behind the scenes.
See exactly how data flows from AP invoices through the XLA tables to GL.
Read Guide