3771357 - Purchase requisitions created via API do not perform WBS budget check - SAP s/4hana cloud public edition

• PRs created via the API cannot perform a validity check on the WBS budget.
• During manual creation, the system raises “Not enough budget available. Message no. PSM_S4C_FM_AVC013”, while via API the purchase requisition is created without this validation.

SAP S/4HANA Cloud Public Edition

1. In the UI, create a purchase requisition with account assignment to a WBS element that has no available budget and observe message PSM_S4C_FM_AVC013.
2. Using API_PURCHASEREQUISITION_2 (OData V4), create a purchase requisition with the same account assignment (WBSElementExternalID) and include the field OrderedQuantity in the item payload.
3. Observe that the purchase requisition is created successfully without the WBS budget check.

The OrderedQuantity field was populated in the API payload during purchase requisition creation, which prevented the system from performing the WBS budget check (PSM AVC).

1. Remove the OrderedQuantity field from the purchase requisition item in the API payload.
2. Send the create request again via API_PURCHASEREQUISITION_2.
3. Verify that when the WBS element has insufficient budget, the system raises message PSM_S4C_FM_AVC013 and blocks creation.
4. Keep OrderedQuantity unmanaged in API requests; it is updated automatically by follow-on processes such as purchase orders.

purchase requisition api, api_purchaserequisition_2, odata v4, wbs, wbs element, psm avc, budget check, orderedquantity, wbselementexternalid, pr creation, public cloud, procurement, budget validation, error psm_s4c_fm_avc013 , KBA , MM-PUR-REQ-BAPI-2CL , BAPIs - Purchase requisition (Public Cloud) , Problem