Note that you can click the button (or press F5) to invoke field help at any time from within the job panel itself.

Business Benefits

Frequently events occur which will halt the update of an inventory count from taking place. This job identifies areas that may exist in the data of a count that could cause the update to fail in job PI.72 [Count - Update]. Running this job prior to running PI72 will allow you to identify these issues and take action to remedy them.

Note: For related documentation and workflows, see PI - Physical Inventory. For further information on how inventory is handled under ViewPoint Logistics, see Physical Inventory Overview.

Usage

Use this job to list issues within a generated PI or Cycle Count that could impact the update of that count in PI.72 [Count - Update].

Preconditions

The Count must have been generated in PI.20 [Count - Maintain/Generate] prior to using the diagnostics. Any external and/or blank tickets must must also have been generated in PI.22 [Tags - Generate Blank/External].

Subsequent Actions

The report can identify the following areas of concern:

Uncounted Book Records

In this situation, a record exists in the Count file which has book quantity for a Client/Product/Lot/Location but which does not have a ticket attached to it. PI.72 [Count - Update] will not update a count that has records with no ticket numbers attached.

Un-Entered Tickets

Records exist in the count file that have not had a count quantity entered against them in PI.30 [Count - Enter]. If no count is entered, the system will not have discrepancies calculated, so PI.72 [Count - Update] will not update.

Incomplete Lotting Data

Occasionally, a Lot-Location record may not be removed cleanly from the Inventory system during normal activity. If this occurs, the PI system will generate a count record for this Lot-Location in job PI.20 [Count - Maintain/Generate] when the Generate routine is performed. This will leave an erroneous book record in the Count file that cannot be updated. This diagnostic will identify these records. Maves Support Services will have to remove these records.

Missing Client/Product Data

Occasionally, a Client-Product record will become obsolete and be removed from the inventory system. If this action does not complete correctly, then a Lot Quantity record may still remain, which will generate a count record that cannot be updated in PI.72 [Count - Update].

These records will have to be removed by Maves Support programmers.

Order Discrepancies

If a count is entered in PI.30 [Count - Enter] against a product which has quantity on order, and the quantity entered is less than the quantity on order, then an Order Discrepancy will occur. These can be resolved using job PI.70 [Order Discrepancy - Reconcile].

If PI.70 indicates no current Orders exist for the Count record, then Maves Support Services will have to investigate the issue.

Program Fields and Functions

To review a text version of the field help, click here. Click the button (or press F5) to invoke field help at any time from within the job panel itself.