Oracle Database Discussions

Environment

• RDBMS : 12.1.0.2.0
• Oracle E-Business Suite R12.2.7
• Module: Oracle Payables (AP)
• Subledger Accounting (SLA)

Issue Summary
We are facing an issue with a few specific AP payments where:

• The Void Payment option is unavailable/does not complete successfully for only a few payments.
• Other payments can be voided successfully.
• The Create Accounting concurrent program completes with Warning for the July accounting period, whereas it completes successfully for periods up to 30-Jun-2026.
• The warning appears to be related to corrupt or orphaned accounting data for specific payment transactions only.

Error Message

There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects.
Please enable the profile option SLA: Enable Diagnostics, create accounting again, and run the report Transaction Objects Diagnostics to identify the problem.

Investigation Performed

1. Enabled profile option SLA: Enable Diagnostics.
2. Re-ran Create Accounting.
3. Reviewed Transaction Objects Diagnostics.
4. Verified that Create Accounting processes all other transactions successfully.
5. The issue is isolated to a small number of payment transactions.
6. Verified that the payment records exist in AP tables.
7. Identified indications of orphaned/corrupt SLA transaction object references.
8. One orphaned payment reference was also identified during validation of AP payment-related tables.
9. No customisation or direct database updates have been performed to these transactions.

Observations

• Only a few payment transactions are affected.
• All other payments are processed normally.
• The issue appears to be caused by inconsistent AP/SLA data rather than a setup issue.
• The affected payments cannot be accounted or voided successfully.

Request
Please review the supplied diagnostics and advise:

1. Root cause of the data inconsistency.
2. Whether this is a known Oracle EBS defect.
3. Recommended Oracle-supported data fix.
4. Any data repair scripts available through Oracle Support.
5. Any additional diagnostics or trace files required.

We would appreciate Oracle's guidance on restoring data consistency without unsupported manual updates.