← Back to Cases
AP Payment XLA Accounting Lines CCID and Party Information Incorrect
Case Number00171558
Oracle ModuleAccounts Payable (AP) / Subledger Accounting (XLA)
EBS VersionR12
Functional AreaPayment Processing / XLA Accounting Entries / Cash Clearing and Liability Accounts
Related PatchesNone

Symptoms

Root Cause

AP payment Create Accounting generated XLA accounting lines with incorrect CODE_COMBINATION_ID, PARTY_ID, and PARTY_SITE_ID values on the CASH_CLEARING and LIABILITY line types for multiple payments across multiple AE header pairs. The correct CCID and party/site values must be applied directly to the XLA_AE_LINES rows for each AE header pair. After correcting the lines, the XLA events are marked as processed and the AE headers are marked as Final so the corrected entries can be used for GL reporting and transfer.

Resolution

Step 1 – Create backup tables

Run data_fix.sql. Backup tables are created for:

Step 2 – Update XLA AE lines with correct CCID and party information

For each AE header pair (invoice event header + payment event header), update XLA_AE_LINES to set the correct CODE_COMBINATION_ID, PARTY_ID, and PARTY_SITE_ID filtered by ACCOUNTING_CLASS_CODE:

This pattern is repeated for each AE header pair in the affected set, with the specific CCID and party values varying per payment depending on the payment bank account and supplier.

Step 3 – Mark XLA events as processed

Update XLA_EVENTS to set EVENT_STATUS_CODE = 'P' and PROCESS_STATUS_CODE = 'P' (processed) for all affected event IDs.

Step 4 – Mark XLA AE headers as Final

Update XLA_AE_HEADERS to set ACCOUNTING_ENTRY_STATUS_CODE = 'F' (Final) for all affected AE header IDs. This marks the corrected accounting entries as finalized and ready for GL transfer.

Step 5 – Delete XLA accounting errors

Delete from XLA_ACCOUNTING_ERRORS for all affected event IDs to clear any error records that were generated during the failed or incorrect accounting run.

Step 6 – Commit and validate

Commit. Re-test the accounting by verifying the corrected CCID, PARTY_ID, and PARTY_SITE_ID values appear correctly in the AP Trial Balance and accounting reports for the affected payments.

Note: This fix directly updates XLA subledger accounting lines that may already have been transferred to GL. If the original incorrect entries were transferred to GL, correcting the XLA tables alone will not correct the GL balances — GL Journal correcting entries may also be required. Verify the GL transfer status of the affected AE headers before applying this fix and determine whether GL reclassification entries are also needed.

Script Inventory

FileDescription
data_fix.sqlCreates backups of XLA_AE_LINES, XLA_EVENTS, XLA_AE_HEADERS; updates CODE_COMBINATION_ID, PARTY_ID, PARTY_SITE_ID on XLA_AE_LINES for CASH_CLEARING and LIABILITY accounting class codes across multiple AE header pairs; updates XLA_EVENTS to processed status; updates XLA_AE_HEADERS ACCOUNTING_ENTRY_STATUS_CODE to 'F'; deletes XLA_ACCOUNTING_ERRORS for affected events.

Key Tables Affected

TableAction
XLA_AE_LINESUpdate CODE_COMBINATION_ID, PARTY_ID, PARTY_SITE_ID for CASH_CLEARING and LIABILITY lines
XLA_EVENTSUpdate EVENT_STATUS_CODE and PROCESS_STATUS_CODE to 'P' (Processed)
XLA_AE_HEADERSUpdate ACCOUNTING_ENTRY_STATUS_CODE to 'F' (Final)
XLA_ACCOUNTING_ERRORSDelete error records for affected events