Incorrect Defaulting Of OTB_EOW_DATE When Otb_System_Ind = 'N'
(Doc ID 2919603.1)
Last updated on JANUARY 06, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 22.1 to 22.1 [Release 22.1]Information in this document applies to any platform.
Symptoms
While creating purchase orders from UI screen, the OTB_EOW_DATE populates incorrectly.
OTB_EOW_DATE should be based on the NOT_AFTER_DATE selected and can not be less than NOT_AFTER_DATE
Steps to recreate:
- Go to Create Order Screen in RMS
- Select supplier, dept and not before date and not after date, give future dates which are greater than vdate+10 days
- Go to calculate date
- Popup asks to override existing selected dates- select No
- Notice that OTB_EOW_DATE is populated as current EOW date
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 |
Cause |
Solution |
References |