About running the Data Verification Toolset

You run the Data Verification Toolset programs in four phases. To ensure accurate reports, you need to run all four phases when verifying your data. These paragraphs describe what these phases are and list the order in which the programs are to be run. For the most accurate reporting results, the phases should be run in sequential order.

You should run the Data Verification Toolset programs any time that you suspect an error exists in the Warehouse application database.

The four phases are:

Note: The Phase One programs can be run concurrently.
  • Phase One (Orphan Record Check). In this phase, the programs check for orphan records. Orphan records are missing some required components, such as a header record missing some of its detail lines, or detail lines that are missing a closed header. For example, the WH Orphan Record Check - Report Only (WH420) program checks that every shipment line detail record belongs to an existing shipment line record, and that each shipment line belongs to an existing shipment record.

    Note: You can run Phase One programs alone, if you suspect orphan records exist. However, if you proceed to run Phase Two, you must also run Phase Three and Phase Four.
  • Phase Two (Document Integrity Check). This phase makes sure that all records for each source document are in sync. The Document Integrity programs check closed headers and detail lines in the external systems to ensure that the detail lines of each record correspond to its header information. For example, if a customer order record is closed, then none of the customer order line records can be in an Open status.

  • Phase Three (Warehouse and Inventory Control Integrity Check). You can run Phase Three after successfully completing Phase One and Phase Two. Phase Three ensures that the Inventory Control and Warehouse application database files are in sync with the external documents that created them. For example, this phase checks that the demand record for a requisition line is in the same status and for the same quantity.

  • Phase Four (Warehouse and Inventory Control Detail Integrity Check). This phase makes sure that the records within the Inventory Control and Warehouse applications are in sync. For example, this phase checks that the stock-on-hand quantity for a serial-number tracked item is backed up by the same number of serial numbers. This phase also checks the sum of the quantities in all of the bins for a specific item to ensure that the sum matches the stock-on-hand quantity for that item.

Report programs

This table describes which report programs belong to each of the four phases, and what each program does. These programs are report only; the actual correcting of data does not occur until you run the update programs. These report programs must be run first, and in the order listed.

Phase Associated programs
Phase One (Orphan Record Check)
  • RQ Orphan Check - Report Only (RQ420). This program purges orphan records within the Requisitions application.

  • OE Orphan Check - Report Only (OE420). This program purges orphan records within the Order Entry application.

  • WO Orphan Check - Report Only (WO420). This program purges orphan records within the Production Order application.

  • PO Orphan Check - Report Only (PO420). This program purges orphan records within the Purchase Order application.

  • WH Orphan Check - Report Only (WH420). This program purges orphan records within the Warehouse application.

Phase Two (Document Integrity Check)
  • RQ Document Integrity Check - Report Only (RQ421). This program ensures that any open lines have an open header and a corresponding demand record within the Requisitions application.

  • OE Document Integrity Check - Report Only (OE421). This program ensures that any open lines have an open header and a corresponding demand record within the Order Entry application.

  • WO Document Integrity Check - Report Only (WO421). This program ensures that any open lines have an open header and a corresponding demand record within the Production Order application.

  • PO Document Integrity Check - Report Only (PO421). This program ensures that any open lines have an open header and a corresponding demand record within the Purchase Order application.

  • IT Document Integrity Check - Report Only (WH421). This program ensures that any open lines have an open header and a corresponding demand record within the Warehouse application.

    WH421 also ensures that a demand record exists for the pre-released document header record when the transaction type is IT (Issue Transfer).

Phase Three (Warehouse and Inventory Control Integrity Check)
  • WH-IC Integrity Check - Report Only (WH422). This program ensures that the inventory and warehouse files are in sync with the open documents.

Phase Four (Warehouse and Inventory Control Detail Integrity Check)
  • WH-IC Detail Integrity Check (WH423). For UNIX and Windows, this program ensures consistencies within the ITEMLOC, ITSERIAL, and SOHDETAIL files based on data within the WODETAIL, WHSHLDTL, and WHDEMNDDTL files.

  • WH-IC Detail Integrity Check - Report and Update (WH433). For IBM i, this program ensures consistencies within the DBICITL, DBICSER, and DBICSDT files based on data within the DBWOWOD, DBWHWHD, and DBWHWDD files.

Update programs

This table describes which update programs belong to each of the four phases, and what each program does. Update programs correct your data when run in Update mode, and should not be run until you have reviewed the report results. These update programs must be run in the order listed.

Phase Associated programs
Phase One (Orphan Record Check)
  • RQ Orphan Record Check (RQ430). This program purges orphan records within the Requisitions application.

  • OE Orphan Check - Report and Update (OE430). This program purges orphan records within the Order Entry application.

  • WO Orphan Check - Report and Update (WO430). This program purges orphan records within the Production Order application.

  • PO Orphan Record Check (PO430). This program purges orphan records within the Purchase Order application.

  • WH Orphan Check - Report and Update (WH430). This program purges orphan records within the Warehouse application.

    You must run WH Orphan Check - Report and Update (WH430) after the other orphan check programs have completed.

Phase Two (Document Integrity Check)
  • RQ Document Integrity Check (RQ431). This program ensures that any open lines have an open header and a corresponding demand record within the Requisitions application.

  • OE Document Integrity Check - Report Only (OE431). This program ensures that any open lines have an open header and a corresponding demand record within the Order Entry application.

  • WO Document Integrity Check - Report and Update (WO431). This program ensures that any open lines have an open header and a corresponding demand record within the Production Order application.

  • PO Document Integrity Check (PO431). This program ensures that any open lines have an open header and a corresponding demand record within the Purchase Order application.

  • IT Document Integrity Check - Report and Update (WH431). This program ensures that any open lines have an open header and a corresponding demand record within the Warehouse application.

    WH421 also ensures that a demand record exists for the pre-released document header record when the transaction type is IT (Issue Transfer).

Phase Three (Warehouse and Inventory Control Integrity Check)
  • WH-IC Integrity Check - Report and Update (WH432). This program ensures that the Warehouse and Inventory Control application database files are in sync with the open documents.

Phase Four (Warehouse and Inventory Control Detail Integrity Check)
  • WH-IC Detail Integrity Check - Report and Update (WH433). For UNIX and Windows, this program ensures consistencies within the ITEMLOC, ITSERIAL, and SOHDETAIL files based on data within the WODETAIL, WHSHLDTL, and WHDEMNDDTL files.

  • WH-IC Detail Integrity Check - Report and Update (WH433). For IBM i, this program ensures consistencies within the DBICITL, DBICSER, and DBICSDT files based on data within the DBWOWOD, DBWHWHD, and DBWHWDD files.