Enterprise Diagnostics Programs

The diagnostics programs protect your files and allow software problems to be resolved before they become major issues. If diagnostics are not run regularly, and a software error is causing a file problem, it may be difficult or impossible to detect the cause of the problem. Minor problems that can easily be fixed can become serious problems if left undetected. Below is a list and brief explanations of our standard program diagnostics.

Accounts Payable:

    AP70 A/P Diagnostic - used to verify that the Accounts Payable sub-ledger balances to the Accounts Payable control accounts in the General Ledger.

    • Recommendation: Monthly as part of your normal month end closing procedure.

Accounts Receivable:

    AR70 A/R Diagnostic - checks that the AR sub-ledger is in balance to the A/R control account(s) in the General Ledger as of the entered Aging date.

    • Recommendation: Monthly as part of your normal month end closing procedure.

    AR73 Print AR-IN Diagnostic List - allows you to check that the AR sub-ledger is in balance to the AR control account in the General Ledger. If an out of balance situation occurs, the AR73 Diagnostic list prints the detail transactions for reconciling purposes. AR73 prints either a list of Cash Receipts or Invoice registers for a specific period of time.

    • Recommendation: Print this report only if AR70 is out of balance.

    AR71 Delinquency Days Diagnostic - is run on demand to preserve the integrity of each Customer's delinquency status. The program cycles through all active Customers (i.e. not flagged for deletion) and examines all DEBIT items looking for the one with the oldest due date. That date, which is stored by Customer, is compared to the system date to determine a Customer's delinquency status.

    • Recommendation: This program should be run after any changes are made to invoice terms and at month-end.

    AR72 Delinquency Days Diagnostic Report - reports any incorrect dates that are found and rectified in Delinquency Days Diagnostics (AR71).

    • Recommendation: Must be run once AR71 is complete.

General Ledger:

    GL70 GL Diagnostics - verifies that debits are equal to credits in the GL Transaction Collector File. This program accumulates debits and credits by system code and reports any balance errors by system at the end of the run.

    • Recommendation: You can run GL70 as frequently as required; we recommend that you run GL70 before month-end processing.

Inventory Masters:

    IM71 Master File Diagnostic - is designed to ensure that the inventory cross-reference files have a one-to-one relationship with the inventory master file. Missing records are created wherever necessary. The procedure for running the diagnostics is the program be run and printed (IM72) and then re-run and printed. Any items that appear on the second print should be reported to the Support Department for correction since this would indicate a problem exists that the diagnostic cannot resolve.

    • Recommendation: Weekly for the first month of a new implementation and then monthly.

    IM72 Print Master Files Diagnostics Report - will report any abnormal conditions detected by the Master File Diagnostic program.

    • Recommendation: Must be run after IM71 is complete.

Invoicing:

    IN71 Invoice History Diagnostic - validates and corrects system records in the Invoice Header and Detail History files. The run-time for IN71 depends on the size of the Invoice History master file (i.e., the more history kept on-line, the longer this program takes to complete). The procedure for running the diagnostics is the program be run and printed (IN72) and then re-run and printed. Any items that appear on the second print should be reported to the Support Department for correction since this would indicate a problem exists that the diagnostic cannot resolve.

    • Recommendation: Weekly for the first month of a new implementation and then monthly.

    IN72 Print Invoice History Diagnostics Report - prints the errors detected by Invoice History Diagnostics (IN71).

    • Recommendation: Must be run after IN71 is complete.

Order Processing:

    OE71 Order File Diagnostics - ensures that the data files used by the Order Entry module are free of errors and warns of existing errors so that they can be traced and corrected. The Order diagnostic reads the Open Order Header, Detail and Sort files. The procedure for running the diagnostics is the program be run and printed (OE72) and then re-run and printed. Any items that appear on the second print should be reported to the Support Department for correction since this would indicate a problem exists that the diagnostic cannot resolve.

    • Recommendation without Order Management: Daily for the first month of a new implementation and then bi-weekly.

    • Recommendation with Order Management: Daily for the first month of a new implementation and then weekly.

    OE72 Print Order File Diagnostics - prints the errors detected by Order File Diagnostic (OE71).

    • Recommendation: Must be run after OE71 is complete.

Purchasing:

    PO70 Purchasing Diagnostic – ensures the data files are being updated correctly and that figures in the purchasing system balance from file to file. The program warns of existing errors so they can be traced and corrected.

    • Recommendation: Monthly.

    PO71 Print Purchasing Diagnostics – prints the errors detected by Purchasing Diagnostic (PO71).

    • Recommendation: Must be run after PO70 is complete.

    PO75 PO Xref Diagnostic – To preserve the integrity of the Purchasing Master file and its associated cross-reference files. The primary function of this diagnostics program is to ensure that the purchasing master cross-reference files have a one-to-one relationship with the purchasing master file, correcting where necessary. These cross-reference files are used to review/print purchasing information records/reports in sequences other than supplier/product.

    • Recommendation: Monthly.

    PO76 Print PO Xref Diagnostic – reports any abnormal conditions detected by PO75.

    • Recommendation: Must be run after PO75 is complete.

Sales:

    SA70 YTD Sales Diagnostic - As a byproduct of processing Invoices and Credit Notes through the Invoicing cycle, Schedule Invoices/Credits (IN43) updates Sales statistics in a variety of files. The diagnostic program confirms that Sales statistics are updated equally in those files. For more information regarding the diagnostic and Sales files please see our on-line help text.

    • Recommendation: Monthly.

Support (Customer Maintenance):

    SU70 Master/Sort File Diagnostics – ensures that customer master data files are being updated correctly and aids in the tracing of data integrity problems that may occur and corrects them.

    • Recommendation: Weekly for the first month of a new implementation and then monthly.

    SU71 Print Master File Diagnostic– prints the errors detected by SU70.

    • Recommendation: Must be run after SU70 is complete.

 
Back