Overview of General Accounting Integrity Reports (R007021/R007031/R007011/R097001/R09706/R007032/R097011/R09705/R099102/R097041/R097031/R097021/R09707)

NOTE: Integrity reports have no "as of" capability, as they provide information that is current at the time you run them. Consequently, the more often you run them, the easier it will be to determine when a problem occurred.

Preferred Order to Run Integrity Reports

The integrities should be run in following sequential order:

Transactions to Batch Headers (R007021)
Batch to Detail & Out of Balance (R007031)
Unposted Batches (R007011)
Companies in Balance (R097001)
Company by Batch Out of Balance (R09706)
Batches Out of Balance (R007032)
Intercompany Accounts in Balance (R097011)
Account Balance to Transactions (R09705)
Repost Account Ledger (R099102)
Accounts without Business Units (R097041)
Account Balance without Account Master (R097031)
Transactions without Account Master (R097021)
Foreign Account Balances (R09707)

Scope

This document provides an overview of the General Accounting Integrity Reports, why and when to run the General Accounting integrity reports, the preferred order in which to run the reports, suggestions for preventing integrity issues, a brief overview of the functionality of each report and links to more detailed documents for each Integrity Report.

Details

General Accounting Integrity Reports

The JD Edwards EnterpriseOne General Accounting system has four types of GL integrity reports:

Batch Header Reports

Use the batch header reports to identify discrepancies between the Batch Control Records table (F0011) and the Account Ledger (F0911) table. Run the batch header reports in following sequence:

Integrity Report	Overview	KM Document
Transactions to Batch Headers (R007021)	This program lists records from the General Ledger (F0911), AP Ledger (F0411), and AR Ledger (F03B11) that are in error. Either records in the batch do not have a matching batch header in the Batch Control Records (F0011) file or the batch contains unposted records with a matching F0011 record that has been marked as posted.	Overview of Transactions to Batch Headers Integrity Report In EnterpriseOne (R007021)
Batch to Detail (R007031)	The functionality of R007031 Batch to Detail and Out of Balance integrity report from Xe/ERP 8.0 release has been split into following integrity reports in 8.9 release and subsequent releases: R007031 Batch to Detail - Batch to detail update functionality R007032 Batches Out of Balance - Post out of balance verification In all releases, this report updates batch header records to status "D" (posted) when all transactions in the batch are posted. It also deletes batch header records if no transactions exist in the General Ledger(F0911), AP Ledger (F0411), AR Ledger (F03B11), or Receipts Header (F0312/EnterpriseOne F03B112) files. Additionally in Xe/ERP 8.0 releases, an exception report of all batches with transactions that do not net to zero is printed.	Overview of Batch to Detail Integrity Report (R007031) in EnterpriseOne Financial Management
Unposted Batches (R007011)	The report lists all unposted batches in the Batch Control Records (F0011) table.	Overview of Unposted Batches Integrity Report In EnterpriseOne (R007011)

Out-of-Balance Reports

Use the out-of-balance reports to verify the following:

Transactions within a company are in balance.
Accounts balance match with Account Ledger on a period-by-period basis.
Intercompany settlement accounts are in balance.

Run the Out of Balance integrity reports in following sequence:

Integrity Report	Overview	KM Document
Companies in Balance (R097001)	The report prints net differences by company and fiscal year and identifies: Adjustments posted to a prior year that are not included in the balance forward amounts for an account. Amounts posted after the period cutoff. Missing intercompany settlements.	Overview of Companies in Balance Integrity Report (R097001)
Company by Batch Out of Balance (R09706)	The report totals all posted G/L transactions in the Account Ledger (F0911) file by batch and compares each batch total to the Batch Header (F0011) table. The report then shows all batches that are out of balance, including the amount by which the batch is out of balance and the company number(s) with out of balance batches, along with the portion of the total discrepancy attributable to each company.	Overview of Company by Batch Out of Balance Integrity Report (R09706)
Batches Out of Balance (R007032)	The report locates batches in which the net amount of debits and credits does not equal zero.	Overview of Batches Out of Balance Report (R007032) in 8.9 and above
Intercompany Accounts in Balance (R097011)	The report compares the balances among the company's various intercompany settlement accounts to verify that the account balances net to zero. If you use a multi-currency environment, do not run this integrity report. Instead, run the Companies in Balance report (R097001).	Overview of Intercompany Accounts in Balance Integrity Report (R097011)
Account Balance to Transactions (R09705)	The program compares each account balance in the Account Balance (F0902) file to the total of all G/L transactions by account in the General Ledger (F0911) file, then lists any discrepancies. It reads the F0902 first. If an F0902 record exists, it compares the balance to the total of the corresponding F0911 transactions. If no F0902 record exists for an account, the program will not check the F0911 for that account.	Overview of Account Balance to Transaction Integrity Report (R09705)
Repost Account Ledger (R099102)	The Repost allows you to correct a damaged Account Balance (F0902) record based on the General Ledger (F0911) transactions total and/or recalculate the balances based on changes to the fiscal date patterns. The program reads the F0911 first. If an F0911 record exists, the system compares the total of the F0911 transactions to the F0902 balance. If no F0911 records exist, the programwill not check the F0902 for that account. The Repost cannot be run by batch or by period. Data selection should include an entire fiscal year (or multiple years). Data selection may also include a single Short Account ID (AID), Ledger Type (LT), or Company (CO).	Overview Repost Account Ledger Integrity Report (R099102)

NOTE: If a batch has the Exclude Batch from Integrity Report option selected in the Batch Header Revisions program (P0011) and the batch contains an out-of-balance entry, the batch will not appear on the following integrity reports:

Batch to Detail (R007031)
Batches Out of Balance (R007032)
Company by Batch Out of Balance (R09706)
AR to GL by Batch Integrity Report (R03B701)

When you run R007032 and R09706 integrity reports, ensure that the data selection for Include Batch on Integrity (IBOI) flag is not equal to N. No specific data selection is required for R007031 and R03B701 integrity reports.

Chart of Accounts Reports

Use the chart of accounts reports to verify that the company number in the Account Master (F0901) matches the company number in the Business Unit Master (F0006), Account Balance (F0902), and Account Ledger (F0911) tables. You should also run these reports if you move one or more business units to another company. In update mode, run the chart of accounts reports in following sequence:

Integrity Report	Overview	KM Document
Accounts without Business Units (R097041)	This program compares the Account Master (F0901) file to the Business Unit Master (F0006) file and lists any discrepancies where F0901 items do not have a corresponding F0006 record. It also lists company number discrepancies between the two files and updates the company number in the F0901 with the company number in the F0006. Additionally, it identifies accounts with missing levels of detail.	How To Change the Company Number for a Business Unit In EnterpriseOne (R097041/R097031/R097021)
Account Balance without Account Master (R097031)	This program compares Account Balance (F0902) records to Account Master (F0901) records and lists discrepancies where F0902 records do not have a valid, matching F0901 record and where company numbers differ in the two files. It also updates the company number in the F0902 with the company number in the F0901.	How To Change the Company Number for a Business Unit In EnterpriseOne (R097041/R097031/R097021)
Transactions without Account Master (R097021)	This program compares General Ledger (F0911) records to Account Master (F0901) records and lists discrepancies where F0911 records do not have a valid, matching F0901 record and where company numbers differ in the two files. It also updates the company number in the F0911 with the company number in the F0901.	How To Change the Company Number for a Business Unit In EnterpriseOne (R097041/R097031/R097021)

NOTE: This sequence ensures that the company number always originates from the F0006 table. By running the Accounts without Business Units report first, it also ensures that the other two integrity reports use the company information in the F0901 table to update the F0902 and F0911 tables.

Multicurrency

In case of multi-currency, apart from the above mentioned integrities, consider running the following integrity report as well:

Integrity Report	Overview	KM Document
Foreign Account Balances (R09707)	The R09707 integrity reports the discrepancies in foreign account balances in the Account Balance (F0902) table.	Overview of Foreign Currency Account Balances Integrity Report (R09707)

Suggestions for Preventing Integrity Issues

Run integrity reports often. Depending on the size of the company and the volume of transactions processed, users may run integrity reports nightly, weekly, or monthly. Frequent review of integrity reports aids in rapid identification of discrepancies. Users can research and resolve issues more efficiently. No single integrity report will verify all the system data.
Place appropriate security on Batch Header Revisions can prevent erroneous deletion of batch headers and invalid out-of-balance postings.
Place security on System Constants. Changes to system constants impact all users. Changing some options, such as those related to multi-currency can change how records are created, which could cause data issues such as duplicate F0902 records.
Assign responsibility for out of balance batches to a central contact.
Post to one single-threaded job queue. In a single-threaded job queue, only one job runs at a time thus preventing multiple programs from accessing the same record at the same time.
Allow each integrity program to complete prior to running the next (or use a single-threaded job queue).
Assign Post Edit Code "M" to accounts to which the system creates automatic entries, such as intercompany or trade accounts. Posting edit code M allows only the system to make entries to these accounts.
Assign responsibility to a central contact for making changes or deletions to companies, business units, and accounts. This maintains consistency and avoids potential confusion.
Post all batches before running integrities. Some integrity issues are caused by unposted batches.
Run integrity reports after normal business hours. Some reports may read large files, like the Account Ledger (F0911), which takes extended processing time. Other integrity reports update files. Avoid having users access records at the same time the integrity reports are running.