Inventory Counts Overview
Written by Anthony Hodge
Updated at August 13th, 2025
Table of Contents
The inventory handling applications under ViewPoint Logistics are used to count each Client’s Inventory with
- Ticket generation and count recording,
- Count entry and reports of outstanding Tickets,
- Reconciliation of physical vs computer/book records.
For a list of the core applications associated with inventory counts in VL, see PI - Physical Inventory.
Usage and Operations
PI.20 [Count - Maintain/Generate]
This is where you define the parameters that will apply to each Count. Numerous Counts can be set up with different parameters for each one. There are options for types of Tickets, blank or external, and to show Lot information etc. Also the count options and how to handle discrepancies are defined here. Note that option #2 in Field 8 will only generate Tickets for Locations that have stock in them as recognized by the system. Option #1 will let you tell the system what the ranges of the external and blank Tickets to generate (see program PI.22). The Pending or In-Process status is if the Tickets have been generated or not. After the Count has been updated, this status will change to Updated status.
PI.22 [Tags - Generate Blank/External]
This is where the types of Tickets that were defined in Field 8 of PI.20 are printed. Note that each range of Tickets must have a different numbered range. NO overlapping of ranges is allowed to ensure an accurate Count and avoid possible mix-ups later on.
PI.24 [Tickets - Assign to Operators]
If, for some reason, you want to assign a specific Operator or Operators to do a specific Count for a specific Client, this is where you assign these Operators. Or if a certain Operator is needed to do a re-count, or if you want certain Operators to count specific Locations, this is where the tickets are assigned to these Operators. Once the ranges are defined, they must be generated first before viewing and printing in PI.26 and PI.28.
This is where you preview the Tickets that were generated in PI.20 and PI.22 for accuracy before actually printing. Depending on the set-up in Field 9 of PI.20, Field 2 will be bypassed or the option will be given to view different Ticket types. Also, if specific Tickets were assigned to Operators in PI.24, the Operator can be viewed here for accuracy and distribution of Tickets.
This is where you print the Tickets that were defined in the previous programs. Options are given to print A- and B-type Tickets. Also, Tickets can be printed by Operator and by Ticket ranges, if needed. The printed Tickets are then given to the counters and the Inventory is taken.
Note: After entering the Count number and accepting it, the next screen shows the option of printing a Count sheet, which will print in alphanumeric sequence an Inventory sheet that can be used instead of Tags.
The printout will show information as defined in PI.20.
The odd/even option will let you print sheets or Tickets by odd/even Location sequence, so that both sides of an Aisle can be counted at the same time.
This is where the Inventory Counts that were taken are entered into the system. Caution must be used when entering the Counts, to make sure they are applied to the correct Tag sheet so that discrepancies do not occur. Depending on what you have defined in Field 8 of PI.20, Fields 3-6 will be populated with the appropriate information according to the set-ups.
Count entry must be done using the sequence 1) Quantity, 2) F1 key, 3) F4 key ... after which the program will show the next Ticket number. Failure to follow this sequence will result in no count being updated. In Field 3, a look-up will bring up a browse that will show you counts entered against Tickets, for review purposes. Depending on the type of Count, programs PI.40 [A/B Ticket Discrepancy Reports] or PI.53 [A vs B Variances - Report] should be run, to view and correct discrepancies. Any discrepancies MUST be corrected on the A-type Tickets.
PI.32 [B Tickets for A Discrepancy]
This is where you would generate Tickets for an A vs. book discrepancy Count. It will only generate the discrepancies under B Tickets. These Tickets are then printed in PI.28 and the re-count is taken. This program is not applicable if a full B Count is intended.
PI.40 [A/B Ticket Discrepancy Reports]
This program is used to view the different types of discrepancies:
A Count vs. book,
B Count vs. book,
A Count vs. B Count,
A or B reference discrepancies which tell us the quantities are okay but the Lot, Product, etc. do not match.
PI.51 [Missing Tickets-Report]
If any Tickets that were generated and printed are missing or lost or not entered, this report will print the missing numbers so they can be traced, and action taken.
PI.53 [A vs B Variances - Report]
This report will show a more detailed discrepancy report, showing actual A/B Counts and the variance between them.
PI.55 [Physical Tag Balances - Report]
This program is used to print the information that was entered in PI.30, by Client, Product, etc. You can compare the physical to the book Inventory by running PI.56.
PI.56 [Physical vs Book - Report]
This program produces the report that compares the results of the physical Count and the computer records, to view discrepancies, if any, and take corrective action. You should review this report thoroughly before accepting it, as the next step would be to update the Inventory and transfer the physical Count to book.
PI.60 [PI Diagnostics]
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.
PI.68 [Count - Abort Physical]
This program is used to (mark to) abort a Count that has not been updated yet in PI.72. Once the Count has been marked, the status will change to Aborted. The actual aborting process is carried out in PI.78. Once the Count is aborted, all the data attached to the Count will be purged so that no activity will show in the PI system. This is used in the case of a Test Count or if a mistake was made in the parameters in PI.20.
PI.71 [Item Reconciliation Report]
This report indicates quantities on-order and in-transit, which may account for discrepancies in the Cycle Count quantities. Modifications may be made to the Count quantities in program PI.30 [Count - Enter] to resolve the discrepancies.
PI.72 [Count - Update]
This program is used to transfer the physical Count to book and update and record the new Counts in the system. All future activity will take the physical Count quantities as the new book value. If you try to update a Count and there are still unresolved discrepancies or missing Tickets from program PI.20 [Count - Maintain/Generate], a message will pop up and tell you where the problem is, and will not let you update until they are fixed. This is only when there is an A/B discrepancy, not a physical/ book variance.
PI.78 [Purge Completed/Aborted Counts]
This program will purge completed/updated Counts or Counts with an Aborted status as assigned in program PI.68. All activity against this Count will be purged in the PI system, but if the Count has been updated in program PI.72, the book value will be what the actual physical Count was.
PI.90 [Hold / Adjustment Codes]
The Hold codes that you want to assign to overages, shortages, and adjustments are set up here. The Hold code for a shortage should be a non-shippable type, so that no activity can be applied to it until the differences are corrected. Also, Location position for odd/even Tickets is assigned here.
PI.91 [Cycle Count Class]
This job is used to define Classes for Cycle Counts. Examples: Daily, Weekly, Monthly, Quarterly, Yearly, etc.
PI.92 [Assign Cycle Count Class]
This program is used to Assign Cycle Count Class to the Client and Product.