The Transactions To Batch Headers integrity report (R007021) provides following transaction level information on integrity issues:
Unposted and posted transactions without a batch header record in the F0011 table.
Unposted transactions with batch header status of 'D' (Posted).
Posted transactions with batch header status of either Approved or Pending.
The Transactions To Batch Headers report (R007021) compares batches in the Batch Header table (F0011) with its associated detailed transactions (in tables listed below) & identifies following discrepancies:
The report lists unposted or posted transactions that do have a missing batch header record in F0011 table.
It lists transactions for which F0011 batch header record is marked as 'D' (Posted) but it has the corresponding detail records as ' '(Unposted). For example, if there is a Journal Entry with Batch Status F0011.ICIST = D (Posted) whereas the corresponding F0911 detail transactions have F0911.GLPOST = ' '(Unposted), it would show up as discrepancy on integrity report.
It also lists transactions for which F0011 record is marked as Unposted but it has the corresponding detail records as Posted. For example, if there is a Journal Entry with Batch Status as Unposted whereas the corresponding F0911 detail transactions have F0911.GLPOST = 'P' (Posted), it would also show up as discrepancy.
General Accounting Tables:
Account Ledger (F0911)
Accounts Receivables Tables:
Customer Ledger (F03B11)
Receipts Header (F03B13)
Receipts Detail (F03B14)
Accounts Payable Tables:
Accounts Payable Ledger (F0411)
Accounts Payable - Matching Document (F0413)
Accounts Payable Matching Document Detail (F0414)
Scope
This document provides an overview of the Transactions to Batch Headers Integrity Report (R007021) including the overview, program functionality, setup, and information on reviewing and resolving the integrity report.
Details
Setup
Processing Options
Post/Unposted Tab
1. Posted/Unposted Transactions
Enter '1' to limit the integrity check to only unposted transactions.
A default of blank will cause the report to process both posted and unposted transactions.
Select Tab
1. Date Range (From & Thru Date):
Enter a date range (From & Thru) to limit the records, system selects for processing.
A default of blank will run over the entire table unless a value for Prior Days is entered below.
2. Prior Days:
Enter the number of prior days (to the current date) to limit the records, system selects for processing.
A default of blank will use the From Date and Thru Date. For example, if you specify 30 for this processing option, the system selects records starting 30 days ago through today.
NOTE: Since R007021 is a batch header report, the system uses the batch date (F0011.ICDICJ), not the general ledger date, to select records.
3. Batch Type Range (From & Thru Batch Type):
Enter a batch type range (from UDC 98/IT) to limit the integrity check.
A default of blank will select all Batch Types.
4. Batch Number Range (From & Thru Batch Number):
Enter a batch number range to limit the integrity check.
A default of blank will select all the batch numbers.
5. User ID Range (From & Thru User ID):
Enter a range of user IDs to limit the integrity check.
A default of blank will select all the User Ids.
G/L Tab
1. G/L Integrity check Flag
Enter '1' to expand the integrity check to include the Account Ledger file (F0911).
Blank does not include the F0911 records for comparison with F0011.
NOTE:
If you specify a range of batch types or batch numbers in the Batch processing options and specify '1' for this GL processing option, the system identifies the batches and then compares the corresponding records in the F0911 table to the F0011 table.
If you specify a range of batch types or batch numbers in the Batch processing options and leave this GL processing option blank, the system does not perform an integrity check between the F0911 and F0011 tables.
A/R Tab
1. A/R Ledger File F03B11 Flag
Enter '1' to expand the integrity check to include the Accounts Receivable Ledger file (F03B11).
Blank does not include the F03B11 records for comparison with F0011.
2. A/R Receipts Header File F03B13 Flag
Enter '1' to expand the integrity check to include the Receipt Header file (F03B13).
Blank does not include the F03B13 records for comparison with F0011.
3. Compare Receipts Header and Detail Flag
Enter '1' to expand the integrity check to compare the Receipt Header file (F03B13) with the Receipts Detail file (F03B14).
Blank does not include the comparison between F03B13 & F03B14 records for with F0011.
NOTE: If you specify a range of batch types or batch numbers in the processing options and leave any of these AR processing options blank, the system does not perform an integrity check between the specified table and the F0011 table. For example, assume that you specify the batch type range IB through RB in the processing options. Then you specify '1' for the GL and AP processing options and leave the AR processing options blank. The system will perform an integrity check on the batches within the IB through RB range that exist in the F0911 table and compare them to the F0011 table.
A/P Tab
1. A/P Ledger File F0411 Flag
Enter '1' to expand the integrity check to include the Accounts Payable Ledger file (F0411).
Blank does not include the F0411 records for comparison with F0011.
2. A/P Matching Document File F0413 Flag
Enter '1' to expand the integrity check to include the Accounts Payable Matching Document file (F0413).
Blank does not include the F0413 records for comparison with F0011.
3. Compare A/P Header and Detail Flag
Enter '1' to expand the integrity check to compare the Accounts Payable Matching Document file (F0413) with the Accounts Payable Matching Document Detail file (F0414).
Blank does not include the F0413 & F0414 records for comparison with F0011.
ENHANCEMENT NOTE: In 8.10 & subsequent EnterpriseOne releases, a new Processing Option Tab "Options" is added that allows the report to rebuild batch headers automatically for missing batch headers, and also provides an option to set the default status of newly created Batch Header as either Pending or Approved.
Options Tab
1. Rebuild Missing Batch Header F0011 Flag
Enter '1' to rebuild missing F0011 batch header records. A message would appear on the report Missing batch header record was added.
Blank would not rebuild the missing batch header record. A message would appear on the report No batch header record.
2. Manager Approval Flag
Enter '1' in case Manager Approval is required for newly added batch header records. The system would create the batch header with batch status as ' ' (Pending).
Enter Blank, in case Manager Approval is not required for newly added batch header records. The batch status will be created with status as 'A' (Approved).
Data Selection
Do not specify any data selection criteria for this report.
NOTE:
This report can be lengthy at times. For example, if a 200-line journal entry has an integrity issue, for instance, the batch header shows missing, the system would print all the 200 lines. For this reason, you might want to create different versions of this report and use processing options to specify whether to compare general ledger, accounts payable, or accounts receivable transactions with the batch records.
You must set at least one of the GL, AR, or AP processing options for the system to process records for data discrepancies. Otherwise, the system prints the message No Data Selected on the report.
When missing batch headers are rebuilt, they may need to be updated to a batch status of "D" if the supporting detail records (GA, AR, AP) have already been posted. The Batch to Detail Integrity Report (R007031) can be used to make this update. Please see E1: 09: Overview of Batch to Detail Integrity Report (R007031) in EnterpriseOne Financial Management (Doc ID 1378537.1) for more information about this functionality.
Reviewing the Report
* The report categorizes the discrepancies (if any) under different headings owing to comparison of batch header table with each detail transaction table, depending upon the Integrity Check flag specified under different Processing options tab. The R007021 report would print following messages:
No.
Error Message
Cause of Error Message
1*
No Batch Header (F0011) Record
This would appear if a batch header for any detail transactions is missing from F0011 Batch Header table.
2*
Batch Header (F0011) Unposted / Detail (XYZ) Posted (where XYZ could be either of F0911/F03B11/F03B13/F03B14/F0411/F0413/F0414 tables)
If a particular batch number has Batch Status Unposted whereas the corresponding detail transactions have Post Status as Posted.
3*
Batch Header (F0011) Posted / Detail (XYZ) Unposted (where XYZ could be either of F0911/F03B11/F03B13/F03B14/F0411/F0413/F0414 tables)
This would appear if a particular batch number has Batch Status F0011.IST = 'D' (Batch header shows Posted) whereas the corresponding detail transactions have Post Status as Unposted.
If F03B13/F0413 header record is Posted and all of the corresponding F03B14/F0414 detail records are Unposted. Please note that F03B13 is always associated with F03B14 and F0413 with F0414 table.
5*
Header (F03B13/F0414) Unposted / All Detail (F03B14/F0414) Posted
If F03B13/F0413 header record is Unposted and all of the corresponding F03B14/F0414 detail records are Posted.
6*
No Records in Error
This message would appear if the Integrity check flag is enabled for a particular table and none of the above mentioned discrepancies are found.
Resolving the Integrity
No Batch Header (F0011) Record
To correct this discrepancy, please follow either of the methods to create the missing batch header:
Automatically:
Re-run R007021 by setting the processing option under Options Tab Rebuild Missing Batch Header as '1' to rebuild missing batch header. After it creates a batch header, it would print message: Missing Batch Header (F0011) record was Added.
Manually:
Open P0011 Work with Batches form.
Select Form-exit --> Create.
In Batch header revisions, add the batch header related information. Specify information in all fields except Input Total, Batch Status, and Number of Documents Expected.
NOTE:
If actual Amount is unknown, Oracle recommends that you enter 100 or more in the Amount Entered field.
If the actual number of documents is unknown, Oracle recommends that you enter 10 or more in the Documents Entered field. For example, if you enter only 1 and later delete a single document, the system updates the Documents Entered field to zero and deletes the batch header when you run the Correcting Out-of-Balance integrity report.
To correct this discrepancy, please follow the below steps:-
Inquire the batch in P0011 Work with Batches form.
Select the Batch header record in grid and Row-Exit -> Revise.
Change the status of the batch to 'A' (Approved) on the Batch Header Revisions form.
Post the batch.
Header (ABC) Posted / Detail (XYZ) Unposted and 5* Header (F03B13/F0414) Unposted / All Detail (F03B14/F0414) Posted
For both 4* & 5* error messages, it would be required to export and review the data as follows:
Inquire by PYID Payment Id corresponding to the batch number in question and export the data from respective Header (F03B13/F0413) & Detail (F03B14/F0414)
Export the data from F0011 and F0911 for the batch number
Review the batch status in all the tables collectively and update the Post Status as desired via SQL. There could be numerous possibilities for this scenario. For instance - reset the F03B13 Header table status to Blank, if corresponding F0011/F03B14 records are unposted and there are no corresponding F0911 entries or reset the F03B13 Header table status to Posted, if corresponding F0011/F03B14/F0911 records have status as Posted.
Reasons for Integrity
Missing batch header records
Following may be the probable reasons for this error to appear on R007021 report:
Computer failure.
Conversion or interface program created a batch header incorrectly.
User created a batch header incorrectly.
User did not enter the actual number of documents on the Batch Header Revisions form.
Posted Batch Header Record, No Posted Detail
This error appears on the R007021 report, if a user incorrectly changes a batch header record to a posted status.
NOTE: To prevent future discrepancies, consider assigning responsibility for batch revisions to a single super-user.
