E1: FIN: How to Resolve Missing Batch Header Integrity
(Doc ID 2818951.1)
Last updated on OCTOBER 27, 2022
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 9.2 to 9.2 [Release 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. Sometimes it can happen that a Batch Header is missing and the transaction is still present in the system and this is a data integrity issue. In order to process the transaction, the Batch Header needs to be added.
This document describes how to resolve missing Batch Header Integrity.
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