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.30: Count - Enter

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

After Tickets have been generated and distributed to the Counters, you will receive the Tickets as the Count is completed by each person. This program allows you to enter the Ticket Count, so that later you can determine if there are any discrepancies between the physical count and the computer records.

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 enter the Count from Tickets that have been produced.

Preconditions

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

Client codes must have been defined in program CR.06 [Client Names and Addresses], and Product codes in program
CR.62 [Client's Inventory Products].

Location codes are defined in program SL.90 [Locations].

Subsequent Actions

Once all the Ticket Counts have been entered, you may compare the results by running program PI.40 [A/B Ticket Discrepancy Reports] or PI.53 [A vs B Variances - Report].

Note regarding A and B tickets:All A vs B ticket discrepancies must be resolved before you can update a count. This requires either the A ticket or the B ticket to be updated so they are the same.

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.

tally input

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • PI - Physical Inventory
  • PI.20: Count - Maintain/Generate
  • PI.20: Count - Maintain/Generate
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