Symptoms

• AP checks that were reissued show incorrect or duplicate accounting entries.
• The accounting for the reissued checks was generated incorrectly — either because of a patch application or because the reissue selection script ran on already-processed checks.
• XLA accounting events for the affected checks need to be reversed (undo accounting) so that correct entries can be generated.
• The AP Trial Balance or payment registers show the reissued checks with wrong amounts or duplicated entries.

Root Cause

During AP check reissue processing, the accounting entries were created incorrectly — either due to a code defect that was subsequently fixed by Oracle patches 8975671, 9257606, and 9272615, or because the reissue process re-accounted checks that were already properly accounted. The fix runs undo accounting for all XLA events associated with the incorrectly accounted checks, then allows the accounting to be regenerated cleanly.

Resolution

Ensure the following Oracle patches are applied before running this fix:

• Patch 8975671
• Patch 9257606
• Patch 9272615

Run the companion selection script (ap_reissue_sel.sql) to populate the driver table with the affected check IDs.

Run data_fix.sql via SQL*Plus:

sqlplus <user>/<password>@<database> @data_fix.sql

The script prompts for User Name, Responsibility Name, and optionally an email address for log delivery.

The script uses the Oracle GDF framework to:

1. Initialize Apps context.
2. Perform undo accounting for all XLA events associated with the incorrectly accounted checks.
3. Create backup tables for affected records.
4. Update driver table with process results (process_flag = 'P' for success).
5. Generate HTML log output.

After undo accounting completes, re-run Create Accounting for the affected checks to generate correct subledger entries.

Script Inventory

Related Oracle Patches