Symptom
The PATCH operation in the API_PROCESS_ORDER_2_SRV OData service returns an HTTP 204 (No Content) response, indicating success; however, only the quantity field is updated, while the scheduling fields are ignored.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Execute a PATCH request to the endpoint `/sap/opu/odata/sap/API_PROCESS_ORDER_2_SRV/A_ProcessOrder_2('PO number').
- Observe the response:
- HTTP Response: 204 No Content (success)
- Only the quantity field (`TotalQuantity`) is updated successfully.
- All scheduling fields remain unchanged without any error message.
Cause
The PATCH request includes both scheduling fields and a quantity field, but when using BasicSchedulingType, the API expects these to be updated in separate calls—one for scheduling fields and another for quantity.
Resolution
- Ensure that the payload for the PATCH operation includes only the fields relevant to the scheduling update.
- Perform the following steps:
- First, execute a PATCH request with the scheduling fields only.
- Then, execute a separate PATCH request to update the quantity field.
- Refer to: Update Process Order for details on dependent mandatory properties and example payloads.
Keywords
api_process_order_2_srv, patch operation, scheduling fields, basic scheduling type, mfgorderplannedstartdate, mfgorderplannedstarttime, mfgorderplannedenddate, mfgorderplannedendtime, sap s/4hana cloud, http 204 no content, odata service, process order update, sap api troubleshooting, scheduling update failure, dependent properties. , KBA , PP-PI-MD-2CL , Basic Data (Public Cloud) , PP-PI-MD , Basic Data , Problem
SAP Knowledge Base Article - Public