API Not Restricting Inventory Adjustments With The Future INV_ADJ Dates
(Doc ID 3059741.1)
Last updated on NOVEMBER 21, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 24.0 and laterInformation in this document applies to any platform.
Symptoms
Validation needs to be put in place to restrict users from inputting a future date for Inventory Adjustments. This is also impacting the TC 23 transactions to be stagnant in the TRAN_DATA tables and not moved to TRAN_DATA_HISTORY. Ideally, the API should not allow inventory adjustments having dates in the future in INV_ADJ.ADJ_DATE.
STEPS
-----------------------
1) Prepare an Inventory Adjustment Payload (similar to the attachment) with the dates in the future
2) Let the API consume the payload
3) Note that there is no error message thrown by the API and still allowing the Inv. Adj. to be created in MFCS
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 |