Case 00094256 – AP Payment Accounting Date and Period Moved to New Period (11i)

AP Payment Accounting Date and Period Moved to New Period (11i)

Case Number	00094256
Oracle Module	Accounts Payable (AP)
EBS Version	11i (11.5.10.2)
Functional Area	Payment Processing / Invoice Distributions / Accounting Period
Related Patches	None

Symptoms

AP invoice distributions and payment records are posted with an incorrect period_name and accounting_date — the records are in a closed or incorrect period rather than the intended accounting period.
The affected payment records have posted_flag = 'N' (unposted) but were assigned to a period that has since been closed.
AP_ACCOUNTING_EVENTS_ALL records for the affected checks show an incorrect accounting_date and may have cannot_account_flag set, preventing accounting from completing.

Root Cause

AP invoice distributions and payment records were assigned to an incorrect period (e.g., a December period) when they should have been in the following January period. The records have not yet been posted (posted_flag = 'N') so the period and date can be corrected. The corresponding AP_ACCOUNTING_EVENTS_ALL records also have the wrong accounting date and may have the cannot_account_flag set, preventing them from being processed.

Resolution

Step 1 – Create backup tables

Run data_fix.sql. Backup tables are created for:

AP_INVOICE_DISTRIBUTIONS_ALL — for invoice distributions linked to the affected checks in the incorrect period
AP_ACCOUNTING_EVENTS_ALL — for accounting events for the affected check IDs
AP_INVOICE_PAYMENTS_ALL — for unposted payment records in the incorrect period

Step 2 – Update invoice distribution period and date

Update AP_INVOICE_DISTRIBUTIONS_ALL to set the correct period_name (derived from GL_PERIOD_STATUSES by start date) and accounting_date for invoice distributions linked to the affected checks that are still unposted and in the incorrect period.

Step 3 – Update payment period and date

Update AP_INVOICE_PAYMENTS_ALL to set the correct accounting_date and period_name for the affected unposted payment records.

Step 4 – Update accounting event date and clear cannot-account flag

Update AP_ACCOUNTING_EVENTS_ALL to set the correct accounting_date and clear cannot_account_flag (set to NULL) for the affected check accounting events that are not yet in ACCOUNTED status.

Step 5 – Commit and validate

Issue COMMIT. Re-run the AP accounting process for the affected checks and confirm the records are posted to the correct period.

Note: This fix uses the 11i AP_ACCOUNTING_EVENTS_ALL table (not the R12 XLA events model). Only unposted records (posted_flag = 'N') are updated. The period name for the target date is derived dynamically from GL_PERIOD_STATUSES by matching the correct period start date.

Script Inventory

File	Description
data_fix.sql	Creates backups; updates period_name and accounting_date in AP_INVOICE_DISTRIBUTIONS_ALL and AP_INVOICE_PAYMENTS_ALL for unposted records in the incorrect period; clears cannot_account_flag and updates accounting_date in AP_ACCOUNTING_EVENTS_ALL for affected checks.

Key Tables Affected

Table	Action
AP_INVOICE_DISTRIBUTIONS_ALL	Update period_name and accounting_date to correct period
AP_INVOICE_PAYMENTS_ALL	Update accounting_date and period_name to correct period
AP_ACCOUNTING_EVENTS_ALL	Update accounting_date; clear cannot_account_flag