E1: 41: Date - Lot Expiration is Invalid (019U) With DME Date Format on Non Lot Controlled Item

(Doc ID 2342504.1)

Last updated on DECEMBER 22, 2017

Applies to:

JD Edwards EnterpriseOne Inventory Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Inventory Adjustments (P4114)

When an Australian user who has date format set as DME (Day / Month / 4 Digit Year) attempts to perform an Inventory Adjustment (P4114) on a non-lot controlled item, with NO lot number the following error occurs.

ERROR
Date - Lot Expiration is Invalid (019U)
CAUSE: The Date - Lot Expiration is invalid for one of the following conditions: - Month not valid (must be between 1 and 12), - Day not valid (must be between 1 and 31, and valid for month), - Year not valid (must be between 00 and 99), - Date has not been entered.
RESOLUTION: Enter a valid Date - Lot Expiration.

The item being used in the inventory adjustment transaction is NOT a lot controlled item and there is no lot number populated in the grid. Also the error does not occur when the line is edited, but only appears after clicking OK to complete the transaction.

If the user enters a lot expiration date in the field, the error goes away even though there is no lot number used in teh transaction.

The issue can be reproduced at will with the following steps:

  1. Enter E1 and change your User Profile (P0092) Date Format from MDE to DME
  2. Exit E1 and reenter E1 under your user id.
  3. Find an item with Lot Process Type = Blank, where lots are optional
  4. Perform an Inventory Adjustment (P4114) to add a quantity to a location but do not enter a lot.
  5. When the line is edited, no error appears.
  6. When the user clicks OK, the "Date - Lot Expiration is Invalid (019U)" Error is displayed.
  7. Change your User Profile (P0092) Date Format back from DME to MDE
  8. Exit E1 and reenter E1 under your user id.
  9. Perform an Inventory Adjustment (P4114) to add a quantity to the same item location with no lot information populated
  10. Transaction succeeds with no error.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms