Explain the detailed end-to-end flow of SES update scenario / the behavior of SES updates from SAP ECC to Ariba Network?

Please find below the detailed flow of the SES update scenario explaining the behavior of SES updates and how SES Acceptance, Revoke Acceptance and Rejection Processes are designed in Ariba: 

SES - Acceptance & Revoke Acceptance:

1. When an SES (service entry sheet) is created for a Service PO (purchase order) from AN and sent to SAP Enterprise Central Component, the Status of the SES in AN would be Sent / Sent, and when it reaches SAP Enterprise Central Component, an SUR (status update request) would be sent back to AN.
2. Upon receiving an SUR, the SES Status would be Sent / Acknowledged.
3. When the SES is blocked (kept on hold) in SAP Enterprise Central Component, no status update would be sent back to AN, and the AN Status would remain the same as Sent / Acknowledged.
4. When the SES is accepted and approved in SAP Enterprise Central Component, a SES update would be sent back and the Status in AN would be Approved / Acknowledged.
5. When the approval is revoked in SAP Enterprise Central Component, the Status of SES in AN would be flipped back to the previous state (as it was before accepting the SES), that is, Sent / Acknowledged.

SES - Rejection:

1. When the SES is deleted, an SES update would be sent back and the Status in AN would be Rejected / Obsoleted.
2. After revoking the acceptance, customers have the following possible options:
   o     Accept it again after review
   o     Hold it for further review
   o     Delete the SES
3. In case the quantity on AN wants to be released, the SES has to be revoked and rejected in the SAP Enterprise Central Component. This would enable you to create a new SES on AN.

There are other integration with P2P, AN and ECC as well as only P2P and AN

SAP Business Network for Procurement & Supply Chain