3703626 - PO API conditions when Partner Function 'WL' is included.

Using the Odata API 'api_purchaseorder_2' to create purchase orders, it is observed that the price in the payload not always taken when the partner type WL is included in the payload. 

SAP S/4Hana Public Cloud Edition 

Create a Purchase Order with api_purchaseorder_2 (sample payload attached) 

When you use the API WITH the WL partner type defined. The system will always assign the value of the condition record as the price.
In this case the condition record is considered the most precise source and it takes precedence over the manual value provided in the payload.    

To clarify the system behaviour in this regard: 

If there is no valid condition record for the combination used. 
You can use the API with or without the WL partner type defined and the 
system will always assign the manual amount from the payload as the price. 

If there IS a valid condition record for the combination used, either a condition (maintained directly in MEK2 or in an info record).
- When you use the API without the WL partner type defined. 
The system will always assign the manual amount from the payload as the price.   

- When you use the API WITH the WL partner type defined. 
The system will always assign the value of the condition record as the price.
In this case the condition record is considered the most precise source and it takes precedence over the manual value provided in the payload.   

api_purchaseorder_2, _PurchaseOrderPartner,  Goods Supplier  , KBA , MM-PUR-PO-2CL , Purchase Orders (Public Cloud) , Problem