Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Versions
  • Legacy Ezlearn
  • PI - Physical Inventory

PI.40: A/B Ticket Discrepancy Reports

Written by Anthony Hodge

Updated at August 13th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Versions
    VL.19.010 VL.19.00 Legacy Ezlearn
  • What's New!
  • FAQ
  • Whitepaper & Case Studies
+ More

Table of Contents

Business Benefits Usage Preconditions Subsequent Actions Program Fields and Functions

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

In the course of taking a Physical Count, there are numerous Tags/Tickets in the hands of the Stock-Takers. Some of these might be lost, while others may have inadvertently been duplicated.

To make the Physical Count meaningful and accurate, it is important to account for all the Tags/Tickets that were issued, so that no Inventory is overlooked and is reconciled to the computer records. Similarly, any duplicates must be found and corrected so that the Count is not distorted. This program produces a report that highlights any such omissions or duplications, so that you can take corrective or followup action.

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 view the different types of discrepancies:

  • A vs Book
  • B vs Book
  • A vs B
  • A or B reference discrepancies, which indicate that the quantities are right but the Lot, Product, etc. do not match.

Preconditions

The Count code must have been set up in program PI.20 [Count - Maintain/Generate] and Ticket numbers generated in program PI.20 [Count - Maintain/Generate] or PI.22 [Tags - Generate Blank/External].

The information from Tickets must have been entered in program PI.30 [Count - Enter].

Subsequent Actions

Based on the discrepancies identified in this report, you may proceed to reconcile the discrepancies.

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.

discrepancy ticket

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • PI.32: B Tickets for A Discrepancy
  • PI.24: Tickets - Assign to Operators
  • PI.28: Tickets - Print
MAVES Logo

For more than fifty years, we have been exclusively focused on the development of multi-client third-party logistics software and supporting services.

Address

MAVES International Software Corp

140 Allstate Parkway

Suite #302

Markham, ON L3R 5Y8

905-882-8300

Email: info@maves.com

Links

  • Home
  • Contact Us
  • Careers
  • News and Events
  • Blog
  • Support Desk

Associations and Memberships

WERC CSCMP Global Cold Chain IARW IWLA

©Copyright 2025 MAVES International Software. Privacy Policy. Terms of Use. Site Map

Expand