R12 SLA - Subledger Accounting Explained Part 1

Written by Puneet Vishnoi Sunday, 22 June 2008 14:27

Please find first in the series of articles on R12 Subledger Accounting from Puneet Vishnoi. Puneet is a freelance consultant in Europe. Prior to freelancing, he was one of the key developers in Oracle Corporation for Oracle Projects Accounting and Oracle Grants Applications. Puneet has designed numerous critical solutions in Oracle Applications R12 and 11i. He has vast experience in new R12 General Ledger Architecture. Puneet Vishnoi also happens to be an excellent troubleshooter, resolving various business critical issues when he was in Oracle Corporation. This article is Part-1 of Subledger Accounting. Why SLA and what does it do? Oracle Sub Ledger accounting (SLA) is accounting hub in Oracle Application Release 12 (R12). It is used to derive all attributes required to account a transaction in Oracle General Ledger. In R12, SLA is used to derive the very basic accounting attributes like entered amount, accounted amount, Date, Currency code etc and the complex attributes like Ledger, Code Combination ID, Periods etc. After deriving these accounting attributes the transactions are then interfaced to GL from SLA. Thus in R12 no sub ledgers (AP, PO, PA etc) interfaces the transactions directly to GL, but all the transactions are interfaced to GL in following 2 steps: 1. Sub ledgers interface the data to SLA. 2. SLA derives the accounting information and interfaces the data to GL. SLA gives the flexibility to manage the entire accounting rule at one place, which acts as a single source of truth for GL. Note: There is no separate responsibility to access SLA setup or the view the transactions generated by SLA. Rather we can access SLA setup and review accounted transactions with extended menus attached to each sub ledger module. Menu to access the SLA accounted transactions.

Menu to access the SLA Setup.

1/2

R12 SLA - Subledger Accounting Explained Part 1

Written by Puneet Vishnoi Sunday, 22 June 2008 14:27

How does SLA 1.How Register sub ledger transactions in SLA. calls as provided call Payables After EVENT. this SLA validating API by calls API Events SLA. from to this /works? create approving concurrent It API are is up created while a to reference the /soon program user costing by sub creates calling ledgers of PRC: the transaction the validated accounting on Generate public how to API transaction in for call Cost the xla_events_pub_pkg.create_events the the respective Accounting Invoice. API. in SLA. For module, example This Events reference the Oracle and sub Oracle ledger is Projects known While (Will expenditure_item_id unique generated registered discuss calling event_id. in by SLA in xla_events_pub_pkg.create_events, the next This SLA. for step). etc. accounting. event_id Once As Unique event will as ID then is the can successfully act sub be as an ledger a invoice reference oracle created generates id passes or in to a SLA, all po_distribution event the a means unique accounting in SLA, that id and SLA id or event returns transaction an class is Taking run Tieback which and the interfacing id will the PRC: process. between register example Interface it to SLA But events GL. of in and Oracle Cost There R12 in sub SLA to Projects is ledger General no and only tieback thereafter tables. in need Ledger 11i process to where run SLA followed PRC: after in will R12, take costing by Generate as Journal care there the of Cost transaction accounting Import is one Accounting to followed one user the reference transaction by Events need PRC: toof 2. expenditure_item_id does SLA understand as SLA uses whether same unique table to id store is invoice all the id identifier? or a po_distribution id or an event understand In step class 1 we is this discussed used better to distinguish we that will while go thru between creating the seeded the the types event oracle of we transaction information. also need passed to pass for event processing. class. This To Navigation: Responsibility: Projects, Vision Services (USA) Menu: Setup > Subledger Accounting > Accounting Methods Builder > Events >entries Event Modal

This SLA. the directly projects screen Because interfaced shows related the the GL, to above the transactions. GL thats hierarchical from screen why PA we shot but In structure do the they is not entity from are see of Oracle screen routed Invoice different Projects thru we as transactions see one AR. only responsibility of the those entity that transactions can as thus Invoices be it interfaced shows that are only can not to be Identifiers is Identifier columns SOURCE_ID_CHAR_1 XLA_TRANSACTION_ENTITIES. passing that window are expenditure_Item_id can the tells be unique used what to ID are 4 column these that SOURCE_ID_INT_1 for is values entity passed in SLA EXPENDITURE. and table to SLA columns should from to 4, are store sub SOURCE_ID_DATE_1 present Identifier ledgers. expenditure_item_id. in Per Column table the screenshot field to 4, The under identifier Oracle interfaced Event Supplier Oracle Class Types. Projects Cost to window GL. In etc. can PA This Further we interfaces displays level have we of different the could hierarchy only different these classify event is 2 kind known transactions Supplier types of as expenditure like Event Cost Labor from as class, Cost, Expense AP. transactions which Misc Report is Cost, further that Usage and can classified Invoices be Cost, into as 3. Based on the identifiers and event class, how SLA creates accounting lines? XDODTEXE. different executable After registering concurrent for does This example the executable program following: event in Projects in names. SLA, is provided we it is Around can used by create SLA with 160 name concurrent and accounting is PRC: used programs entries by Create all the by Accounting. are sub running uses ledgers executable the This with same a. Gather information from base tables in sub ledgers. b. the accounting attributes based on the data fetched from sub ledgers. c. Derive code combination id based on the business rules. d. Create journal lines based on the seeded Journal definition. e. lines in XLA_AE_HEADERS and XLA_AE_LINES.

2/2