PRC:PO Create Purchase Order Using REST WebService Match Approval Level is Derived as 4- Way instead of 2-Way
(Doc ID 2789618.1)
Last updated on JULY 19, 2021
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.13.21.01.0 and laterOracle Fusion Purchasing - Version 11.13.21.10.0 and later
Information in this document applies to any platform.
Symptoms
Actual Behavior:
When Creating Purchase Order using REST webservice - Payload has Match Approval Level as 2-Way
But after creating the Purchase Order if you check the Schedules it is showing Match Approval Level as 4-Way
If the same PO is created from UI the defailt is defaulting to 2-Way
Expected Behavior:
Expect PO is created with Match Approval Level as 2-Way as it is given in Payload or if defaulting logic is followed it should default to 2-way
Steps:
The issue can be reproduced at will with the following steps:
1. Create Payload with Match approval Level - 2-way
2. Run the Payload for creating the PO
3. PO is Created , check schedules it shows Match approval level as 4-way
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 |