My Oracle Support Banner

E1: FIN: How to Resolve Post Code Discrepancy between Batch Header and Transaction Table (Doc ID 2818897.1)

Last updated on NOVEMBER 02, 2021

Applies to:

JD Edwards EnterpriseOne Accounts Payable - Version XE to 9.2 [Release XE to 9.2]
JD Edwards EnterpriseOne Accounts Receivable - Version XE to 9.2 [Release XE to 9.2]
JD Edwards EnterpriseOne General Ledger - Version XE to 9.2 [Release XE to 9.2]
Information in this document applies to any platform.


In Financial modules transactions are grouped in batches.  Any transaction should be part of a batch and the batches are defined by the Batch Header table (F0011) and transaction table records (for instance: Accounts Payable Ledger (F0411), Accounts Payable Matching Document (F0413), Accounts Receivable Ledger (F03B11), General Ledger (F0911), etc. depending on the specific transaction). The Batch Number (ICU) and the Batch Type (ICUT) are linking the Batch Header and transaction tables. Financial transactions need to be posted in order to finalize the accounting process. Post Status columns exist in the Batch Header and in the transaction tables. The Post Status is indicated by different columns and the success code is as follows:

When the post is successful the Post Status columns should indicate that the post was successful in both the header and the transaction tables. If there is a mismatch, this is an integrity issue.

This document describes how to resolve Post Code discrepancy between Batch Header and Transaction table. This applies to General Ledger, Accounts Payable and Accounts Receivable transactions.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Batch Header (F0011) Unposted / Transaction (XYZ) Posted
 Batch Header (F0011) Posted / Transaction (XYZ) Unposted

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