E1: 04: Accounts Payable Matching Document (F0413), Accounts Payable Matching Document Detail (F0414) and Account Ledger (F0911) Post Code Mismatch Data Integrity Issue (Doc ID 2983304.1)

Last updated on NOVEMBER 16, 2023

Applies to:

Symptoms

The Post Status is not consistent in Accounts Payable Matching Document (F0413), Accounts Payable Matching Document Detail (F0414) and Account Ledger (F0911)
A payment batch is stored in three tables: Accounts Payable Matching Document (F0413), Accounts Payable Matching Detail (F0414) and Account Ledger (F0911). For one Payment Batch there is one F0413 row, one or multiple F0414 rows and if it is posted multiple F0911 rows. If the batch is not posted there should be no F0911 rows.

For a Payment that is posted correctly the Post Code is populated as follows:

• F0413 Post Status Payments (ISTP) should be ‘D’
• F0414 G/L Posted Code should be ‘D’
• F0911 G/L Posted Code should be ‘P’

The users should verify that for each batch in F0413 with the Post Status Payments = ‘D’ all corresponding F0414 rows have G/L Posted Code = ’D’ and all F0911 rows have the G/L Posted Code = ‘P’.

Steps to replicate:

1. Start Databrowser and open F0413, F0414 and F0911 tables.
2. Query F0413 by Batch Number (ICU) and if the F0413 Post Code = ‘D’ and take note of the Payment ID (PYID) of the row that was found.
3. Query F0414 with the Payment ID from step 2 and make sure all rows have G/L Posted Code = ‘D’
4. Query F0911 with Batch Number and Batch Type from step 1 and make sure all the rows have the G/L Posted Code (POST) = ‘P’

Changes

Cause

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