Subledger Accounting (SLA) Tables
Subledger Accounting
About SLA:
1.SLA is an intermediate step between subledger products and the Oracle General Ledger
2.Journal entries are created in Subledger Accounting and then transferred to Oracle General Ledger
Tables that are involved in this process are
XLA_TRANSACTION_ENTITIES
XLA_EVENTS
XLA_AE_HEADERS
XLA_AE_LINES
GL_IMPORT_REFERENCES
GL_JE_LINES
GL_JE_HEADERS
GL_BALANCES
XLA_EVENTS
XLA_AE_HEADERS
XLA_AE_LINES
GL_IMPORT_REFERENCES
GL_JE_LINES
GL_JE_HEADERS
GL_BALANCES
NOTE: For every transaction, it will create an entity_id in xla_transaction_entities table. This column we use to make link between transaction entities and xla ae headers table. By default at first time for an entity, one event will be there. Suppose for the same transaction (means for same entity), if we create any adjustment or some other thing, that we treat it as an event. So for one entity there will be more events.
Links Between these tables
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 (APPLICAITON_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_TRANSACTION_ENTITIES (APPLICATION_ID, ENTITY_ID)
|
Draft : Draft will create journal entries, which are not final, which means they are not ready to be transferred to GL.
You can create accounting on this transaction again and again, which will delete the old journal entries and create new ones. You can’t transfer these journal entries to GL.
xla_events.process_status_code = D
xla_events.event_status_code = U
xla_ae_headers.accounting_entry_status_code = D
xla_events.event_status_code = U
xla_ae_headers.accounting_entry_status_code = D
Final : Final will create journal entries, which can be transferred to GL. Once it is finally accounted you can’t run create accounting on the particular transaction (specifically on that event).
Run Transfer Journal Entries to GL program
xla_events.process_status_code = P
xla_events.event_status_code = P
xla_ae_headers.accounting_entry_status_code = F
xla_events.event_status_code = P
xla_ae_headers.accounting_entry_status_code = F
Final Post: Final Post will create journal entries in final mode, transfer them to GL and post them.
xla_ae_headers.accounting_entry_status_code = F
xla_ae_headers.transfer_status_code = Y
xla_events.process_status_code = P
xla_events.event_status_code = P
xla_ae_headers.transfer_status_code = Y
xla_events.process_status_code = P
xla_events.event_status_code = P
---------------------------------------------------------------------------------------------------------
How to join GL tables with XLA (SubLedger Accounting) tables
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 (application_id, entity_id)
No comments:
Post a Comment