Accounting entries from Sub-ledger are posted to GL.
1. General LEdger Transfer program, from the respective subledger which will move the data into the GL_INTERFACE table.
2. These entries are imported to GL as Journals with the help of Journal Import program. This information is stored in GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES.
3. This will result in Posting control ID which will be a source of reference to track the various entities posted as part of the current posting process.
4. JE_BATCH_ID will be the primary key on GL_JE_BATCHES which will help track, the headers, lines and import references for the Journals.
5. Import references are stored in GL_IMPORT_REFERENCES, which will help in Drill down from GL to subledger. This is controlled by the Journal Source setup in GL.
6. The imported Journals are the posted to GL. This information hits the GL_BALANCES table.
To identify the various transactions that were posted with the batch,
1. GL provides drilldown from front end in the Journal entry form.
2. From backend, refer to
GL_IMPORT_REFERENCES to obtain the POSTING_CONTROL_ID from REFERENCE_1 and then map it to the subledger accounting tables like RA_CUST_TRX_LINES_GL_DIST_ALL.POSTING_CONTROL_ID.
3. If the Import references are not created, then the only way to drill down will be to refer to the Batch name in GL_JE_BATCHES, obtain the POSTING_CONTROL_ID from the string and map it to the base subledger tables.
