SAP Knowledge Base Article - Public

3713188 - SES Status Update Not Triggered to Ariba (Scope Item 42K)

Symptom

  • A Service Entry Sheet (SES) is created in Ariba and successfully interfaced to S/4HANA Cloud.

  • The SES is approved in S/4HANA, but no status update (Approved/Rejected) is sent back to Ariba.

  • No outbound messages or errors are visible in Message Monitoring or SRT_MONI for the status update.

  • The customer is unable to proceed with invoicing in Ariba because the SES remains in "Sent" or "Awaiting Approval" status.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a Service Purchase Order in SAP S/4HANA Public Cloud.
  2. Generate a Service Entry Sheet (SES) for the Service Purchase Order in Ariba.
  3. Approve the SES in SAP S/4HANA Public Cloud.
  4. Verify that the receipt request generated from SAP S/4HANA Public Cloud reflects correctly in Ariba.
  5. Observe that the SES status in Ariba does not update to "Approved."

Cause

The S/4HANA outbound framework uses the SenderBusinessSystemID from the inbound SES request to determine the target for the status update. If the Business System ID maintained in the Communication System does not exactly match the ID sent by Ariba/CIG, the system cannot identify a valid recipient, and the outbound trigger fails silently.

Resolution

  1. Check the inbound payload for the SES in Message Monitoring app of S/4HANA (Communication Arrangement SAP_COM_0237, Inbound Service ServiceEntrySheetRequest_In).

  2. Identify the value in the tag <SenderBusinessSystemID>.

  3. Go to the Communication Systems app and open the system associated with SAP_COM_0237

  4. Compare the Business System ID field with the value from the payload.

Ensure consistency between the Ariba Network/CIG configuration and the S/4HANA Communication System:

  1. Option A (Recommended): Update the Business System ID in the S/4HANA Communication Systems app to match the ID being sent in the XML payload.

  2. Option B: Adjust the Sender/Receiver transformation in SAP Integration Suite, managed gateway (CIG) to ensure the Business System ID sent to S/4HANA matches the existing configuration in the S/4HANA system.

Keywords

ses status synchronization, sap s/4hana public cloud, ariba, service po, ses approval status, sy/530 error, cx_sy_no_handler, cx_sy_ref_is_initial, ses not updated, sap ariba integration, service entry sheet , KBA , MM-PUR-SVC-SES-2CL , Service Entry Sheet for Service Procurement (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions