When I force-reject a Service Entry Sheet (SES) and my company's ERP sends a push error, the SES is stuck in Rejecting status.

When I cancel an SES and my company's ERP sends a push error, the SES is stuck in Canceling status.

The self-service parameter Application.ServiceSheet.FixSESStatusIntegrationForCIG is set to No, and your site uses SAP Managed Gateway for Spend&Network to send SES for external processing.

To prevent new SES getting stuck in these statuses, enable the self-service parameter Application.ServiceSheet.FixSESStatusIntegrationForCIG, which will instruct the system to move the SES back to its prior status when there is an ERP push error.
For example, if you force-reject a Processed SES, with this parameter on, the system will move the SES back to Processed in the case of a push error.

Then, if there are any SES stuck in Canceling or Rejecting, open a ticket with SAP Support.

KB0401355: How do I view/edit a parameter value in Intelligent Configuration Manager?

It may happen that after a user Force Rejects the SES, the SES Rejecting Status update fails to send to the ERP

• In case of Managed Gateway for Spend&Network Integration, ServiceSheetStatusAsyncExportRequest task shows Failed
• in case of Web Service Integration, logs can show this Status Export failed

SES History will indicate Failed in External System and no Push Error will appear. SES will remain in Rejecting Status as per expected behavior.
The same applies for the Canceling scenario.

Purchasing