OTB Validation When Interfacing POS With Approved Status
(Doc ID 3074660.1)
Last updated on FEBRUARY 28, 2025
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Goal
Customer intends to validate OTB, so the system option PROCUREMENT_UNIT_OPTIONS will be set to ‘Y'es.
Using PO screens, the PO approval process checks if the OTB is exceeded. If it is, the system prompts the user to either proceed with the PO approval or abort. If the user chooses to proceed, the PO is approved; otherwise, it remains in Worksheet status.
Using PO induction, the upload process refers to the system option SVC_ORDER_PARAMETER_CONFIG.OTB_OVERRIDE to decide the action:
- If the option is set to ‘No’ and the OTB is exceeded, the PO will be created but not approved.
- If the option is set to ‘Yes’ and the OTB is exceeded, the PO will be created and approved.
Using integration from external systems, what is the expected outcome when attempting to upload a PO in approved status if the OTB is exceeded? Is there an attribute in the payload that integration uses to determine the action? Do the same system option used by induction apply to integration?
Solution
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
Goal |
Solution |
References |