Transfer Inventory Transaction Into General Ledger through Subledger Accounting SLA Flow

The goal of this document is to transfer Inventory transaction distributions into the General Ledger (GL) through Subledger Accounting (SLA) in release 12.

Cost Manager Costing Inventory Transactions

After any Inventory or WIP transactions , such as Misc Receipt , Average Cost Update , or Sub inventory Transfer transaction , Cost manager should cost these transactions and distributions should be seen in the Material Distributions form. (In the MT_Transaction_Accounts table).

Launch the Cost Manager
Inventory -- Setup -- Transactions -- Interface Managers --- Tools (Menu Bar) -- Launch Manager --Submit
(No scheduling for the Cost Manager should be done in the Request Form)

Run Create Accounting Program

In R12 , you need to run Create Accounting program

Cost Management  SLA 
Run Create Accounting -Cost Management

( Pl pass the following parameters while running create accounting program..)
Ledger = Appropriate Ledger name
Process Category =
End date = &date
Mode = Final /Draft
Errors only =Yes /No
Report = Detail/Summary
Transfer to General Ledger = Yes
Post in General Ledger = Yes /No
Include User Transaction identifiers =Yes

 

Explanation for the parameters used in the Create Accounting program.

Parameter	Description
Ledger	Primary ledger for which Create Accounting program has to be run.
Process Category	This determines the Transactions of which module like Inventory distributions, WIP distributions. If we set it at NULL , then it will take all the distributions.
End Date	Create Accounting program processes only those events with event dates on or before the end date. i.e , If we set the event date as 31-Aug-2008, All the events created till 31 Aug 2008 and which are not been transferred till now , will be set to transfer by the request triggered.
Mode	Mode determines whether the sub-ledger journal entries are created in Draft or Final Mode. If Draft mode is selected, then the Transfer to General Ledger, Post in General Ledger, and General Ledger Batch Name fields are disabled. Draft entries cannot be transferred to General Ledger. If it is Draft mode then accounting distributions can be amended in SLA.(if required)
Errors Only	This parameter limits the creation of accounting to those events for which accounting has previously failed. If we set this Parameter to YES , the it will try to process all the events which were in the Error status earlier.
Report	This shows the sub-ledger accounting distributions in Detail or Summary format (Whatever the format selected)
Transfer to General Ledger	This field will be enabled only when the Mode parameter is set to Final. If this column value is set to NO, then Journal import program will not be launched. We need to POST the distributions through General Ledger.
Post in General Ledger	If Transfer to General Ledger is set to YES , then only this field will be enabled. If you set column value of Post in General Ledger as YES , posting of General Ledger batches will be done.
Include User Transaction identifiers	If this column value is set at YES , then we can track transaction_id wise distributions in SLA and in General Ledger. This we value is always recommended to set as Yes.

Table Level tracking of Sub-ledger transaction distributions.

1. To Check the Inventory transaction(s) which are been passed to General Ledger through SLA 
   Select * from mtl_transaction_accounts where transaction_id =&transaction_id
   
   
2. To know the inv_sub_ledger_id which is been populated after running the Create Accounting program.. (which is completed normal) We need pass following parameters while running Create accounting program.
   End date = &date
   Mode = Final
   Errors only =No
   Report = Detail
   Transfer to General Ledger = Yes
   Post in General Ledger = Yes
   Include User Transaction identifiers =Yes
   (The request set with these parameters will post the transactions to General Ledger. )
3. Script name : xla_distribution_links 
   Select * from xla_distribution_links
   where source_distribution_id_num_1 in
   (select Inv_sub_ledger_id from Mtl_transaction_accounts
   where transaction_id =&transc_id)
   
   
   From the above script we will come to know the ae_header_id and event_id which can be used to track into the further tables.
4. Script name : xla_transaction_entities_upg
   Select * from xla_transaction_entities_upg
   where source_id_int_1 =&transc_id)
   and application_id =707
   
   From the above script we will come to know the ENTITY_ID and LEDGER_ID
   
   Below mentioned script output will state whether the corresponding transactions from Inventory Sub ledgers have been transferred to Gl or not.
5. Script name = xla_ae_headers
   Select * from xla_ae_headers
   where ae_header_id =&ae_header_id
   (from the script no 3 you will get the Ae_header_id )
   
   
   From the above script you will come to know , Accounting date and Gl_transfer_status_code and Gl_transfer_date.
   If the Gl_transfer_status_code is "Y" , then this transaction can be further tracked to Gl_IMPORT_REFERENCES and GL_JE_lines table.
   
   From XLA_AE_LINES table we will come to know transaction and code combination id wise tracking ..
   Here GL_TRANSFER_MODE_CODE is set at "D" == Detail
6. Script Name : xla_ae_lines
   Select * from xla_ae_lines
   where ae_header_id =&ae_header_id ( From the script no. 5)
   
   From the xla_ae_lines table we will come to know the Gl_SL_LINK_ID which can be used to track in the Gl.
7. Script Name :GL_IMPORT_REFERENCES 
   Select * from gl_import_references
   where gl_sl_link_table = 'XLAJEL'
   and gl_sl_link_id in (&GL SL_LINK_ID)
   
   From the GL_IMPORT_REFERENCES table we will get je_header_id which can be used as evidence as this transaction is been posted to GL.
8. Script Name : GL_JE_LINES 
   Select * from gl_je_lines where je_header_id = &JE_HEADER_ID ( From the Gl_import_references table) 
   
   
9. Script Name : SLA-GL join
   This script will join the SLA tables and Gl tables , and it can be confirmed from the output of this script whether the concerned Gl batch is been posted to General Ledger.
   SELECT DISTINCT glb.name
   FROM xla_ae_lines xle,
   gl_import_references gli,
   gl_je_batches glb
   WHERE ae_header_id = &ae_header_id
   AND xle.gl_sl_link_id = gli.gl_sl_link_id
   AND xle.gl_sl_link_table = gli.gl_sl_link_table
   AND gli.je_batch_id = glb.je_batch_id

From  Oracle Application

• Inventory Responsibility
  > Material Transactions
  > Material Distributions
  
• Cost Management SLA SLA > Inquiry from the menu.
  Select Accounting Events, Journal Entries, or Journal Entry Lines to open the sub-ledger accounting user interface
  
  Select a transaction and choose Tools from the tool bar. Select View Accounting
  Events and the Accounting Events User Interface appears.
  
  We can also choose View Journal Entries to view accounting and journal entry details.