Oracle Applications : General Ledger: Sub ledger Accounting)

Subledger Accounting

Oracle Subledger Accounting is a rules-based engine for generating accounting entries based on source transactions from ALL Oracle Applications 

Why SLA? If you look at the history of the E-Business Suite, the development teams of the subledger applications have always been working rather independently from each other. So from an architectural point of view you had implemented one single application but your end users sometimes were left with the feeling that switching responsibility was the gateway to another world. I might be exaggerating a bit but just compare the accounting processes between AR and AP in 11i for example and you know what I mean.
So it was not a bad idea to consolidate all that scattered functionality and while doing so introduce flexibility to the product.

Features of SLA

• Replaces various disparate 11i setups, providing single source of truth for financial and management analysis
• Introduces a common data model and UI across subledgers
• Highly granular level of detail in the Subledgeraccounting model retained
• Accounting Model separate from Transactional Model
• Catering to custom requirements of accounting of transactions in Subledgers
• Allows multiple accounting representations for a single business event
• Optionally Post subledgeraccounting entries to Secondary Ledgers
• Resolves conflicts between Corporate and Local Accounting Requirements
• Accounting created in Draft or Final mode
• Draft: Review Report, Correct errors
• Final:Transferto GL, Post in GL

Benefits of subledger accounting are:

•      Faster, Easier Reconciliation

•      Corporate Rules = Accounting Standardization

•      Local Rules = Improved Local Compliance

•      Automate “Apples to Apples” Adjustments

•      Improved Audit- ability

•      Improved Internal Control


Features

•     The transaction cannot be modified after creation in Final Mode
•     Automatic Journal Import
•     Journal Import failure -Data will be rolled back
•     Journal Import and Correct forms not used
•    Correction is always in the subledger.

    Reconciliation is simpler
Steps

•      Creates the SLA journals in Final mode
•     Transfers the data to GL_INTERFACE    
•     Runs Journal Import
•     Optionally Triggers the General Ledger Posting program
•  

    Event Class

  Payables

•    Invoice
•    Debit Memo
•    Prepayment
•    Payments
•    Refunds

Receivables

•    Invoice
•    Deposit
•    Receipt
•    Bill Receivable

 Assets

•    Additions
•    Adjustments
•    Capitalization
•    Depreciation

Purchasing

•    Requisition
•    Purchase Order

Events:

Represent transactions that have a financial accounting impact
   Captured when transactions are committed in the subledgersi.e. when a particular action is completed
Financial accounting information can be recorded for events