Create_id,last_update_id Updation On Purchase Orders Via ReST API
(Doc ID 2975935.1)
Last updated on SEPTEMBER 22, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When approvedBy field is passed in the input JSON via purchase order rest Service, orig_approval_id is updated with generic user.
EXPECTED BEHAVIOR
-----------------------
When approvedBy field is passed in the input JSON via purchase order rest Service, orig_approval_id should be updated by the passed value in this field.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Create a PO in Approved Status via rest API webservice.
2. Pass approvedBy field with a value in the input JSON.
3. Notice that the orig_approval_id is not considering the approvedBy value,
instead defaulting to the generic user.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Orig_approval_id should hold the approval ID from an external system.
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 |