Subledger Accounting: How To Avoid and Fix Corruption in Data Transfer from SLA - Negative Ledger_ID, Not Reached GL, Duplicate in GL (Doc ID 883557.1)

Last updated on JULY 02, 2024

Applies to:

Goal

Release 12 introduced SLA - an architectural layer between subledger and GL. Hence, typically, once data has been accounted properly, data transfer happens from subledger to GL through SLA.

During the transfer, some data corruption issues have been reported on the SLA to GL bridge. These issues may be categorized into below categories :

1. Data with negative LEDGER_ID in the General Ledger (GL) tables.
2. Data marked as "Transferred" in SLA but which has not reached GL.
3. Data marked as "Not Transferred" in SLA, but which has reached GL.
4. Multiple posting issues.
5. Data which is in GL but which as been deleted from SLA (This is NOT applicable for 11i data)
6. Journal Import failing with EP01 error while running the Transfer Journal Entries to GL program
7. Data accounted in 11i and transferred to GL in R12 which is missing gl sl link id.

These problems can be visible in the General Ledger (for example, missing journals) but also in the subledgers (for example, Accrual Balance mismatch between Accrual Reconciliation Report and GL).

NOTE:  Please do not cancel the concurrent requests when "Journal Import" program is launched.
Negative Ledger Batches will be created, if you cancel "Create Accounting" or "Transfer to GL" Concurrent Request when the "Journal import" program is launched.
You have to run "Transfer to GL" program again, which will purge the negative LEDGER_ID batches in the next run.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.