3788446 - SES failure in SAP S/4HANA not communicated back to SAP Business Network after supplier submission

• A supplier submits a Service Entry Sheet (SES) in the business network; the SES shows as successfully submitted in the supplier portal.
• The SES fails during inbound processing in s/4hana and no failure status or error details are returned to the business network.
• The SES remains in a submitted/successful state in the business network with no error message displayed.
• The supplier cannot edit the submitted SES.
• The supplier cannot create a replacement SES for the same service lines.
• Example inbound error in S/4HANA: "Measurement Unit EA has no ISO code".

 SAP S/4HANA Cloud Public Edition

1. Create a Limit Purchase Order (PO) with multiple limit line items in SAP S/4HANA Cloud Public Edition and transmit it to SAP Business Network.
2. Log in to SAP Business Network as the supplier and choose Create Service Entry Sheet for the purchase order.
3. Enter an invalid or unsupported Unit of Measure (UoM) (for example, a UoM that does not have a valid ISO code mapping).
4. Submit the Service Entry Sheet (SES) from SAP Business Network. The submission is displayed as successful.
5. Monitor the inbound SES processing in SAP S/4HANA and observe that the SES fails validation (for example, "Measurement Unit EA has no ISO code.").
6. Return to SAP Business Network and verify that the SES still appears in a Submitted/Successful state, with no error displayed to the supplier. Also verify that the supplier cannot edit the submitted SES or create a replacement SES for the same service lines.

• The inbound SES fails in s/4hana due to validation errors (for example, invalid UoM or missing ISO code mapping: "Measurement Unit EA has no ISO code").
• By design, the outbound SES status notification (ServiceEntrySheetStsNotif_Out) is sent only when the SES is successfully created in s/4hana; no notification is sent for failed SES creations, so no failure status is updated back to the business network.

Note this is standard behavior: SES status notifications to the business network are sent only upon successful SES creation in S/4HANA.

When SES creation fails in S/4HANA, no failure status or error details are returned to the business network, and suppliers cannot edit the submitted SES or create a replacement SES for the same service lines via the business network.

service entry sheet, ses, business network, ariba, s/4hana cloud public edition, integration, status notification, ServiceEntrySheetStsNotif_Out, failure not communicated, invalid uom, iso code mapping, lean services, limit purchase order, inbound processing, supplier cannot edit ses , KBA , MM-PUR-SVC-SES-2CL , Service Entry Sheet for Service Procurement (Public Cloud) , Problem