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
  • VL.19.00
  • Warehouse Management
  • WMS Core Applications
  • CR - Client Related

CR.55: Date Code Conversion Methods

Written by Anthony Hodge

Updated at August 12th, 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

The ability to translate Manufacturer's Date code dates may be required in order to allow the Warehouse to rotate stock according to a release or expiry date. This program allows you to set up a variety of code date formats and attach them to Products.

The purpose of this functionality is to:

  • enforce the data entry of only valid date code formats during receiving, and
  • automatically calculate the Expiry (Release) date from the Manufacturer's Date code for Products that are released by this date.

Note: For related documentation and workflows, see CR - Client Related.

Usage

Use this job to set up Lot code date formats as follows:

Define a "Method Code". This is a 2-character code that will determine how this particular code date format is to be referred to (e.g., "J1" could mean Julian Date code format #1, which might be in the form 5032, where

  • the first digit denotes the year (e.g., 5 = 1995)
  • the next three digits denote the Julian date (e.g., day 032 of the year); the system will then be set up to recognize this code and translate it to an actual date of February 1, 1995.

This functionality is used during Receiving in programs RE.11 [In-Transit Receipts], RE.21 [Receipts], or RE.31 [Receipt Invoices] and it can be applied to either the Lot code field, the Lot Identity field, or the Extra field.

For instance, the operator may enter a different number in the Lot Code field, then enter the Manufacturer's Lot code in the Lot Identity field. Alternatively, they may enter the Manufacturer's code date in the Lot Code field. The setup in this program allows for either situation.

If the "Extra field" option is used, the operator may use both Lot Code and Lot Identify for other purposes, and instead enter the code date in the Extra field that will appear in receiving. The purpose of the Extra field is only to allow entry of the code date and the original date is not stored on the system.

During the receiving process, the system will do the following:

  • When the Product code is entered, it will display the Method Code description. This is meant to guide the operator when he enters the Julian date code (e.g., if the system requires YYMMDD, this should be part of the Method Code description so that the operator will see this).
  • If the Julian Date Code is entered in a different format, the system will warn the operator of this. Invalid Date Code formats will not be allowed.
  • The system calculated date is automatically updated to the "Expiry Date" of the Lot.

Note that a Method Code may be attached to Products that are NOT defined as Release-Dated. The purpose of this is to still enforce the format of the Lot Code or Lot Identity even though no actual Release Date calculation takes place.

Preconditions

This program applies only if Component *LRD* (Lot Release Date) has been set up in program WP.43 [Global Lot Components].

Lot Set codes need to be set up in programs WP.44 [Lotting Data Sets] and assigned in program WP.46 [Lotting Assignments].

Subsequent Actions

The date code conversion occurs in various programs, including:

OE.01 [Enter Orders (Shipping)]

OE.06 [Pick Confirmation]

OE.20 [Confirm or Modify Shipments]

OE.21 [Enter Shipped Orders]

RE.21 [Receipts]

RE.31 [Receipt Invoices]

OR.20 [Lots - Maintain / Adjust]

and OR.43 [Stock - Inquiry].

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.

unnamed piece no title

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • 5. General Ledger Month End
  • CR.02: Invoice Terms of Payment
  • CR.10: Measuring Units
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