3799843 - Target Value not sent in RequestForQuotationS4Request_Out (4BL Integration, S/4HANA Cloud Public Edition to Ariba Sourcing)

• In the 4BL integration scenario (S/4HANA Cloud Public Edition to Ariba Sourcing), the header field "Target Value" is not included in the RequestForQuotationS4Request SOAP/XML sent from S/4HANA Cloud.
• In traditional S/4 and Ariba integrations (via CIG add-on), this value was sent and mapped to the Baseline Spend extrinsic in Ariba Sourcing.
• The value is visible in the S/4HANA Cloud “Manage Requests for Quotation” app but absent in the source payload received by Managed Gateway/CIG and thus not present in the downstream QuoteRequest cXML.

SAP S/4HANA Cloud Public Edition 

1. Create an RFQ in S/4HANA Cloud Public Edition (Manage Requests for Quotation app) with "Target Value" populated.
2. Initiate the 4BL integration to send RequestForQuotationS4Request SOAP/XML to the Managed Gateway endpoint (/cxf/receiveS4SOAP).
3. Observe Managed Gateway transforms the message to QuoteRequest cXML and sends it to the S4HanaRequestForQuotation service in Ariba Sourcing.
4. Check CIG Transaction Tracker and verify "Target Value" is missing in source/preprocess/outbound payloads; in Ariba Sourcing, the Sourcing Request lacks Baseline Spend.

• The "Target Value" is not supported by the RequestForQuotationS4Request_Out SOAP API (per WSDL), therefore it is not included in the standard 4BL outbound payload.
• Examples of fields not supported by this API include: PaymentTerms, CashDiscount1Days, CashDiscount2Days, CashDiscount1Percent, CashDiscount2Percent, TargetValue.

1. Review the RequestForQuotationS4Request_Out SOAP API documentation to confirm the field is not part of the standard payload.
2. Create a custom field in S/4HANA Cloud to hold the "Target Value" and enable exposure of this custom field for the RequestForQuotationS4Request_Out SOAP API.
3. In Managed Gateway/CIG, map the custom field to the Baseline Spend extrinsic in the QuoteRequest cXML for Ariba Sourcing.
4. Test end-to-end by sending a new RFQ and verify in CIG Transaction Tracker that the custom field is present and that the Sourcing Request in Ariba reflects Baseline Spend.

4BL, requestforquotations4request_out, Target value, baseline spend, ariba sourcing, managed gateway, CIG, QuoteRequest cXML, rfq outbound, s/4hana cloud public edition, missing field, wsdl, api limitation, targetvalue, sourcing request , KBA , MM-PUR-RFQ-2CL , RFQ/Quotation (Public Cloud) , Problem