3802489 - Sales order BOM API PATCH clears header custom fields when BAdI BOM_BEFORE_UPDATE is active (SAP S/4HANA Cloud Public Edition)

• When using API_ORDER_BILL_OF_MATERIAL_SRV to PATCH SalesOrderBOM header extension fields, the custom fields are saved as empty values afterward.
• No error message is returned.
• Observed for sales order BOM; not reproducible for material BOM via the corresponding API in the same scenario.

• Product: SAP S/4HANA Cloud Public Edition
• Bills of Material (Public Cloud)
• API_ORDER_BILL_OF_MATERIAL_SRV (PATCH operation)

1. Ensure an implementation of BAdI BOM_BEFORE_UPDATE exists for Order BOM processing.
2. Use an HTTP client (for example, Postman) to send a PATCH request to the OData service API_ORDER_BILL_OF_MATERIAL_SRV entity SalesOrderBOM with a valid key of a sales order BOM.
3. In the request body, provide values for header-level custom extension fields (for example, YY1_* fields).
4. Check the sales order BOM header custom fields: the values appear cleared (empty) after the update.

A defect in the Sales Order BOM OData processing causes the mapping after BAdI BOM_BEFORE_UPDATE execution to clear header extension field values.

1. Use the Manage Order Bill of Material (Version 2) application to maintain the required sales order BOM header information until the fix is delivered.
2. Plan to retest the PATCH operation after the fix delivery planned with the 2702 main release (targeted for end of February).

refer to: 3072643

sales order BOM, API_ORDER_BILL_OF_MATERIAL_SRV, PATCH, custom fields, extension fields, header, cleared, empty, BAdI BOM_BEFORE_UPDATE, OData, Manage Order Bill of Material(Version 2), SalesOrderBOM, Bill of Material API,  PATCH , KBA , LO-MD-BOM-2CL , Bills of Material (Public Cloud) , Problem