Receiving Journal Transfer to GL by Journal Import

[GL] Receiving Journal Transfer to GL by Journal Import

Found a good article on Receiving (Purchasing) Journal transfer to GL by Journal Import.

Related SQL:
SELECT *
FROM apps.gl_interface
WHERE user_je_source_name = 'Purchasing'
AND user_je_category_name = 'Receiving'

In R11i for Inventory Destination Transactions, the Receiving Transaction Processor Debits and Credits the Receiving Account and Inventory AP Accrual Account respectively in GL_INTERFACE and RCV_RECEIVING_SUB_LEDGER. These Transactions in GL_INTERFACE are identified with User_je_source_name ='Purchasing' and user_je_category_name 'Receiving'. In RCV_RECEIVING_SUB_LEDGER these transactions are identified by column accrual_method_flag ='O'
In R11i for Period End Transactions ie Transactions with accrue_on_receipt_flag ='N' in PO_DISTRIBUTIONS_ALL, no accounting transactions are generated on receipt of goods. The Receipt_Accrual_Period-End program generates the Accounting Entries in GL_INTERFACE and RCV_RECEIVING_SUB_LEDGER simultaneously by Debiting Charge Account and Crediting Expense AP Accrual Account. In GL_INTERFACE the Transactions are identified by column names user_je_source_name='Purchasing' and user_je_category_name ='Acccrual'. In RCV_RECEIVING_SUB_LEDGER the Transactions are identified by column Accrual_Method_flag ='P'.

In R11i both On Line Transactions and Period End Transactions are moved from GL_INTERFACE to GL_IMPORT_REFERENCES,GL_JE_HEADERS and GL_JE_LINES by JOURNAL IMPORT.

In R12 GL_INTEFACE TABLE is no longer directly used for Receiving Transactions. The Receiving Transaction Processor only populates the RCV_RECEIVING_SUB_LEDGER with Inventory Destination Transactions. The Receipt_Accrual_Period-End program also only populates the RCV_RECEIVING_SUB_LEDGER with Expense Destination Period End Accruals.

Create Accounting-Receiving Concurrent program from Cost Mangement Responsibility transfers the journals in RCV_RECEIVING_SUB_LEDGER to SLA Tables. Once the accounting entries are created in receiving subledger for the receiving transactions, Create Accounting process gets started depending on the profile option CST:Receiving Accounting option and the encumbrance set up.

On submitting this program, it spawns the Accounting program which will do the validations and picks the data from table rcv_receiving_sub_ledger and process it according to the accrual method set for the POs

Depending on the accrual method and the value for profile SLA:Disable journal import, this spawned program "Accounting program" inserts the data into gl_interface first and then calls the Journal import program and posting program and populates the accounting events in subledger table xla_ae_headers and entries in xla_ae_lines and xla_distribution_links.
If there is any problem with the Journal import, the data will get rolled back from gl_interface. Once the Journal import is completed, data will get populated in gl_import_references,gl_je_headers and gl_je_lines.

......

==========

[GL] Manual Journal Import Needed

A case study:
User submitted "General Ledger Transfer Program" from AR module, "Journal Import" will be called internally. What happened is "Journal Import"completed error with error, "ORA-01653: unable to extend table GL.GL_IMPORT_REFERENCES by 16 in tab".

GL journal batch is not created.

After DBA fixed the tablespace issue, user reran "General Ledger Transfer Program" as the program says no records to be interfaced, completed warning.

What to do next: Go GL module, Journals->Import->Run, submit journal import with the right Group ID (can be retrieved from "General Ledger Transfer Program" log).