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; when created manually, error "PSM_S4C_FM_AVC013 - Not enough budget available" is raised.

SAP S/4HANA Cloud Public Edition

1. Create a purchase requisition manually with a WBS element that has no available budget and a corresponding G/L account. Observe the error "PSM_S4C_FM_AVC013 - Not enough budget available."
2. Create a purchase requisition via the API (API_PURCHASEREQUISITION_2, OData) using a payload that includes WBSElementExternalID and populates the OrderedQuantity field.
3. Observe that the purchase requisition is created successfully without the WBS budget check.

The request payload included the <OrderedQuantity> field during purchase requisition creation, which prevented the budget check from running.

Ensure that the "OrderedQuantity" field is not populated when creating the Purchase Requisition via API_PURCHASEREQUISITION_2, as this field is typically updated automatically based on the quantity consumed in follow-on processes such as Purchase Orders. 

purchase requisition api, api_purchaserequisition_2, odata v4, wbs budget check, psm avc, orderedquantity, wbselementexternalid, insufficient budget, psm_s4c_fm_avc013, cpi integration, pr creation, budget control, public sector management, avc check, bapi purchase requisition , KBA , MM-PUR-REQ-BAPI-2CL , BAPIs - Purchase requisition (Public Cloud) , Problem