My Oracle Support Banner

Unable to set expiry date for batch and apply lock codes Error: Exception updating batch number R1: descriptor 'date' requires a 'datetime.datetime' object but received a 'datetime.date (Doc ID 2597036.1)

Last updated on OCTOBER 08, 2019

Applies to:

Oracle Warehouse Management Enterprise Edition Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

Core Product Functionality

Unable to set expiry date for batch in Oracle WMS Cloud  

In the "Batch Management" screen of the Oracle WMS Cloud when attempting to set the expiry date for a certain batch, the systems throws the error message: "Exception updating batch number R1: descriptor 'date' requires a 'datetime.datetime' object but received a 'datetime.date'".

When selecting a date from the calendar, It is not allowed any other date format , so it is effectively not possible to set any expiry date. Hence it is not possible to use any FEFO/FIFO functionality.

ERROR
-----------------------
Exception updating batch number R1: descriptor 'date' requires a 'datetime.datetime' object but received a 'datetime.date'



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

1. Responsibility: Oracle Warehouse on Cloud
2. Navigation Path: Users Interface (UI)
3. Go to Batch Management form and try to update the expiry date.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.