WS: 09: Financial Integrity Reports - Preferred Order to Run and Functionality Overview
(Doc ID 950649.1)
Last updated on AUGUST 12, 2021
JD Edwards World Accounts Receivable - Version A7.3 cume 4 and later JD Edwards World General Ledger - Version A7.3 cume 4 and later JD Edwards World Accounts Payable - Version A7.3 cume 4 and later Information in this document applies to any platform.
This document replaces the following document IDs:
626868.1 - WS: 09: Using the Batch Integrity Programs
The following information documents the preferred order for running integrities and the functionality of the G/L, A/R, and A/P integrities. The steps to run integrities are recommended as follows:
Run integrity reports often and before software upgrades or updates. 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 aides in rapid identification of discrepancies. Users can research and resolve issues more efficiently. No single integrity report will verify all the system data.
Place security on Batch Header Revisions. Action Code security 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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!