Expiration Date Change During Completion Of Work Order
(Doc ID 2474633.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Fusion Manufacturing Cloud Service - Version 11.13.18.02.0 to 126.96.36.199.0 [Release 1.0]
Information in this document applies to any platform.
On : 11.13.18.02.0 version, Work Execution
Lot Expiration Date gets changed automatically to a date later than what user input.
At the time of WIP Completion, user enters the lot expiration date as '18-OCT-2018' and clicks save and close. Error pops up as the Locator value is incorrect. At this time in the back ground Lot Expiration Date
automatically gets changed to '17-OCT-2018'.
User corrects the date and proceeds to Issue #2.
At WIP Completion, user provided Lot Expiration Date as '18-OCT-2018 and completes the work order.
However, when you view the lot in Manage Lots UI, the Lot Expiration Date shows '19-OCT-2018'. This is incorrect.
Item Attribute for Shelf Life Control is 'User Defined Expiration Date'.
STEPS TO REPRODUCE
1.User enters lot 'SR123'
2.Clicks save and close and error pops up.
3.Now Lot Expiration Field becomes enabled.
4.User now enters 18-OCT-2018 as Lot expiration Date.
5.Clicks save and close. Error pops up saying Locator is invalid.
6.Notice in the background now Expiration Date automatically changed to 17-OCT-2018.
7.User now enters correct value for the locator.
8.User inputs the Lot Expiration Date as 18-OCT-2018 and clicks save and close.
9.Not Work Order gets successfully completed.
10.User now navigates to Inventory Management and goes to task Manage Lots.
11.User views the lot and the Expiration Date now shows as '19-OCT-2018'.
Lot Expirtation Dates should remain what customer entered and not what system is defaulting to.
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