R12 SLA Tables

http://apps2fusion.com/at/58-pv/303-r12-sla-subledger-accounting

http://oracleapps88.blogspot.com/2011/11/r12-subledger-accounting-tables.html

 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.


Run Create Accounting to Populate Accounting events (SLA)  tables. After running Creating Accounting user can view Accounting.

Key Tables for SLA

XLA_AE_HEADERS
XLA_AE_LINES
XLA_TRANSACTION_ENTITIES
XLA_DISTRIBUTION_LINKS
GL_IMPORT_REFERENCES


XLA_TRANSACTION_ENTITIES.entity_code IN (
'TRANSACTIONS',
"RECEIPTS',
'ADJUSTMENTS',
'PURCHASE_ORDER',
'AP_INVOICES',
'AP_PAYMENTS',
'MTL_ACCOUNTING_EVENTS',
'WIP_ACCOUNTING_EVENTS'
'EXPENDITURES'

-- Mapping Identifiers
--Menu: Setup > Subledger Accounting > Accounting Methods Builder > Events > Event Modal
--Entity Code                     Column Value                                Column in xla_transaction_entities
--EXPENDITURES           EXPENDITURE_ITEM_ID         SOURCE_ID_INT_1
--REVENUE                      PROJECT_ID                                SOURCE_ID_INT_1
--REVENUE                      DRAFT_REVENUE_NUM          SOURCE_ID_INT_2
--AP_INVOICES               INVOICE_ID                                SOURCE_ID_INT_1
--AP_PAYMENTS            CHECK_ID                                   SOURCE_ID_INT_1




Taking the example of Oracle Projects in 11i where after costing the transaction user need to run the ‘PRC: Interface Cost to General Ledger’ followed by ‘Journal Import’ followed by ‘PRC: Tieback process’. But in R12 user only need to run “PRC: Generate Cost Accounting Events” which will register events in SLA and thereafter SLA will take care of accounting the transaction and interfacing it to GL. There is no tieback process in R12, as there is one to one reference of event id between SLA and sub ledger tables.



Other Oracle Table Information
http://oracleappsviews.blogspot.com/2012/06/apps-tables-with-links.html#!/2012/06/apps-tables-with-links.html

XLA_AE_HEADERS XAH,
XLA_AE_LINES XAL,
xla.XLA_TRANSACTION_ENTITIES XTE,
XLA_DISTRIBUTION_LINKS XDL,
XLA_EVENTS XEVENT


R12 Error while running
PRC: Create Accounting
The application accounting definition Projects Standard Accounting owned by Oracle is not validated.  Please validate the application accounting definition or update the application accounting definitions contained in the subledger accounting method Standard Accrual.
Solution
Run Program
Validate Application Accounting Definitions with Ledger and Application Details.


Transaction data not found in XLA_TRANSACTION_ENTITIES
Why are there differences in SELECT * FROM XLA_TRANSACTION_ENTITIES and SELECT * FROM XLA.XLA_TRANSACTION_ENTITIES ? [ID 946314.1]
Solution
Query useing xla.xla_transaction_entities



http://oracle.anilpassi.com/mo-global-dive-into-r12-multi-org-design.html

R12: How to Set the ORG_ID (org context) Before Running a Statement in SQL*Plus? [ID 753178.1]
1. The SQL command to set the ORG_ID prior to running a script is:

SQL> exec mo_global.init('AR');
exec mo_global.set_policy_context('S','&org_id');
2. Enter the org_id when prompted.

exec fnd_global.apps_initialize(11787,20707,201);
exec mo_global.init ('PO');





http://oracle-ramaraj.blogspot.com/2013/01/oracle-app-s-link-between-gl-to.html

Oracle Apps GL Base Table and Interface Table
                          
GL_JE_HEADERS                      GL_INTERFACE
GL_JE_LINES                             GL_INTERFACE_HISTORY
GL_JE_CATEGORIES                GL_DAILY_RATES_INTERFACE  
GL_JE_SOURCES                      GL_BUDGET_INTERFACE
GL_SETS_OF_BOOKS              GL_IEA_INTERFACE
GL_DAILY_RATES
GL_CODE_COMBINATIONS
GL_BALANCES
GL_PERIODS
GL_PERIOD_SETS
GL_CURRENCIES
GL_HISTORICAL_RATES
GL_LOOKUPS   

---------------------------------------------------------------------------------

 
Oracle Apps  :  Link between GL to Subledger Account

GL_JE_BATCHES (je_batch_id)                                   => GL_JE_HEADERS (je_batch_id)

GL_JE_HEADERS (je_header_id)                                  => GL_JE_LINES (je_header_id)

GL_JE_LINES (je_header_id,  je_line_num)                      => GL_IMPORT_REFERENCES (je_header_id, je_line_num)

GL_IMPORT_REFERENCES (gl_sl_link_table, gl_sl_link_id)        => XLA_AE_LINES (gl_sl_link_table, gl_sl_link_id)

XLA_AE_LINES (application_id, ae_header_id)                   => XLA_AE_HEADERS (application_id, ae_header_id) 

XLA_AE_HEADERS (application_id, event_id)                     => XLA_EVENTS (application_id, event_id)  

XLA_EVENTS (application_id, entity_id)                        => XLA.XLA_TRANSACTION_ENTITIES