Hi Experts,
I am facing an issue while updating pricing conditions for NBIC Purchase Orders using API_PURCHASEORDER_2 in SAP S/4HANA Public Cloud.
Scenario:
* PO Type: NBIC
* API: API_PURCHASEORDER_2
* Entity: PurOrderItemPricingElement
* Condition Type: PMP0
I am able to successfully PATCH the pricing condition using Postman and receive HTTP 200 OK response, but the value is not actually updated in the database. After re-reading the pricing element, the old value is restored automatically.
PATCH URL:
/sap/opu/odata4/sap/api_purchaseorder_2/srvd_a2x/sap/purchaseorder/0001/PurOrderItemPricingElement(
PurchaseOrder='4500000450',
PurchaseOrderItem='00010',
PricingDocument='1000000667',
PricingDocumentItem='000010',
PricingProcedureStep='060',
PricingProcedureCounter='001'
)
Payload:
{
"ConditionRateAmount": 159.000000000,
"ConditionCurrency": "AED",
"ConditionIsManuallyChanged": true
}
Response:
* HTTP 200 OK
* No API error
However, after GET:
* ConditionRateAmount still shows old value
* Pricing seems to be redetermined automatically
Observed fields from GET response:
{
"ConditionControl": "C",
"ConditionOrigin": "C",
"ConditionIsDeletable": false,
"ConditionType": "PMP0"
}
Additional findings:
1. POST on PurOrderItemPricingElement is not supported
Error:
"Creating operations are disabled for entity"
2. PATCH on PurchaseOrderItem with NetPriceAmount also returns:
"Operation is not enabled"
3. Same API update works correctly for NB Purchase Orders, but not for NBIC.
My questions:
1. Is pricing condition update intentionally restricted for NBIC Purchase Orders in Public Cloud?
2. Are PMP0/intercompany conditions protected from API persistence?
3. Is there any supported approach to update pricing for NBIC POs through API?
4. Should pricing only be updated indirectly through condition records/info records?
Any guidance or SAP documentation reference would be appreciated.
Thanks.
Request clarification before answering.
Answers to Your Questions
1) Is pricing condition update restricted for NBIC?
Yes. For intercompany POs, pricing is protected — manual changes via API are not persisted.
2) Are PMP0/intercompany conditions protected?
Correct. PMP0 and similar intercompany condition types are system‑driven and cannot be overridden directly.
3) Supported approach to update NBIC pricing via API?
Not supported. The only way to influence NBIC pricing is indirectly, via condition records, info records, or intercompany pricing setup — not by PATCHing the PO condition.
4) Should pricing be updated indirectly?
Yes. Best practice is to maintain the correct intercompany condition records (via pricing procedure configuration or master data). The PO then picks up the right values automatically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Pricing update is restricted for NBIC POs
Yes – PMP0/intercompany conditions are protected
No direct API update supported for these conditions
Maintain pricing via condition records / intercompany pricing config
Or update source objects.
Thanks,
Sravan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.