SAP Knowledge Base Article - Public

3756193 - Order Confirmation Tolerance (0%) not passed from SAP S/4HANA Cloud to SAP Business Network via CIG (Zero Values Ignored)

Symptom

  • An error occurs when suppliers submit an order confirmation with a lower unit price than the original; SAP S/4HANA Cloud does not allow price modifications, and the confirmation is rejected.
  • Control keys for lower unit-price tolerance are configured in SAP S/4HANA Cloud but are not passed to SAP Business Network.
  • Tolerance attributes are not mapped by the standard configuration in Cloud Integration Gateway (CIG).
  • In the integration flow, the SAP S/4HANA Cloud payload shows tolerance data, but the CIG preprocess payload omits fields when their values are 0.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a purchase order in SAP S/4HANA Cloud.
  2. In SAP Business Network, submit an order confirmation with a lower unit price than the original purchase order.
  3. Observe that the confirmation is rejected because the 0% tolerance configuration is not passed to the network.

Cause

During backend processing for the OrderRequest_Out message, zero-valued tolerance fields are excluded by design; only non-zero tolerance values are passed forward. Furthermore, standard CIG mapping leverages SAP Business Network transaction rules and does not include tolerance fields when their value is exactly 0.

Resolution

By standard system behavior, zero-valued tolerance fields are not sent by OrderRequest_Out and are ignored by standard CIG mapping. While the Message Monitoring download may display the full schema with empty fields, the effective outbound data is the backend payload.

To enforce a 0% tolerance downstream, utilize one of the following approaches:

Option 1: Implement Custom Logic in SAP S/4HANA Cloud Use the Custom Logic app enhancement Enrich Standard Mapping for OrderRequest_Out to map the values explicitly:

  1. Populate the required tolerance fields with "0.0" (e.g., permitted price overrun/shortfall).

  2. Set the corresponding controller flags so that initial values are successfully output in the payload.

Option 2: Utilize the CIG Mapping Tool Alternatively, use the CIG Mapping Tool or XSLT to set the target cXML control keys (e.g., price tolerance percentage 0.00) so that SAP Business Network applies a 0% tolerance.

Keywords

Order confirmation tolerance, zero tolerance, SAP S/4HANA Cloud, CIG, SAP Business Network, OrderRequest_Out, permitted_price_overrun_in_pct, permitted_price_short_fall_in, upper_conf_date_tolerance_in_d, lower_conf_date_tolerance_in_d, preprocess payload, SRT_MONI, message monitoring, price decrease, control keys , KBA , MM-PUR-PO-ES-2CL , Enterprise Services in Purchase Order (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions