Symptom
- Service Entry Sheet (SES) created in Ariba and interfaced to SAP S/4HANA cannot be deleted after being rejected in SAP S/4HANA.
- SES quantity in SAP S/4HANA remains consumed even after rejection.
- Attempting to send a new SES from Ariba results in an error due to the consumed quantity in SAP S/4HANA.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a Service Entry Sheet (SES) in Ariba.
- Interface the SES to SAP S/4HANA.
- Reject the SES in SAP S/4HANA.
- Observe that the SES quantity remains consumed in SAP S/4HANA.
- Attempt to send a new SES from Ariba for the same service entry.
- Encounter an error indicating that the quantity is already consumed.
Cause
- The rejection of the SES in SAP S/4HANA does not release the consumed quantity, causing the quantity to remain blocked.
- In standard Ariba–S/4HANA integration, once a SES is created in S/4HANA, the quantity is considered consumed.
Resolution
Follow standard handling procedures based on the SES status:
- For Rejected SES:
- In Ariba, open the rejected SES.
- Edit and resubmit it to S/4HANA.
- This creates an updated SES version that replaces the previous one.
- Do not create a new SES for the same PO item, as quantity is already consumed.
- For Deletion:
- If the SES needs to be deleted, perform a Cancel action in Ariba.
- The cancellation triggers a delete flag in S/4HANA.
- Once replicated, the SES can then be deleted in S/4HANA.
Note:
Direct changes or deletions in S/4HANA are not supported for SES documents originating from Ariba.
Creating a new SES for the same PO while the previous SES quantity is consumed will always fail with “No quantity available for SES.”
See Also
3255842 - Unable to revoke Service Entry Sheet
Keywords
service entry sheet, SES rejection, quantity consumed, SAP S/4HANA, Ariba integration, SES deletion, SES update, SES change request, MM_PUR_SES_CHANGEREQUESTAPI, ServiceEntrySheetStsNotif_Out, SES follow-on documents, SES reversal, SES revoke, SES cancel , KBA , MM-PUR-SVC-SES-2CL , Service Entry Sheet for Service Procurement (Public Cloud) , SBN-AN-TX-SS , Service Procurement/Service Sheet (O&G) , Problem
SAP Knowledge Base Article - Public