As you know, SLA is an intermediate step between subledger applications and GL. SLA creates the final accounting for subledger journal entries and transfers the accounting to GL.
This stores complete and balanced journal entry for each business event that requires accounting.
This can create more than one accounting representation for each transaction.
This also provides accounting information for reports and inquires. This provides the ability to drilldown to subledger journal entries from GL. There is also the
ability to drilldown to the underlying transactions in the related modules from the subledger journal lines
SLA Table Diagram
Refer to table 1 below, will give a idea about the SLA tables.
This table contains subledger events for cost, revenue accounting. Accounting events will be created upon the baselining of a budget for GL validation.
Encumberance accounting events are created upon a successful funds check. One key column of this table is PROCESS_STATUS_CODE which have several meaning as:
- 'I' stand for Invalid : This means Event in error in SLA
- 'E' stand for Error : This means Event in error in SLA
- 'U' stand for Unprocessed : This means Events generated in SLA
- 'R' stand for Related Event : This means Related event in error
- 'P' stand for Processed : This means Final Accounted
- ‘D’ stand for Draft : This means Draft Accounted
This table Stores subledger journal entries. There is a one-to many relationship between accounting events and journal entry headers.
This table table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines.
This table table stores the link between transactions and subledger journal entry lines. Determines whether supplicate subledger journal lines are merged and whether the accounted amounts are calculated by the SLA or passed through.
This table table stores records for events which have errored during the accounting program. If an event is successfully accounted without issue then it will not have records in this table.
This table table stores additional details for source transactions.Columns Source_id and source_id_char form the link between SLA and subledger (AR,AP, PA etc) base tables.
Releastionship between these table can be easily understood in this ER diagram.
Moreover, you should not forgot the Key Concepts of SLA as:
- Event Model : This gives definition of the subledger transaction types and lifecycle
- Entity- This gives a classification of source of transaction
- Event Class - This gives a classifies transaction types for accounting rule purposes
- Event Type : This is for each transaction type, defines possible actions with accounting significance
Hope this Post will helps you to give more insights on SLA.