3800583 - eDocument Mexico: No Inbound API Available in S/4HANA Cloud Public Edition for Asynchronous Status Callback from CPI

When implementing Mexico eDocument using an asynchronous integration pattern on CPI (iPaaS) with Edicom, the customer cannot find a SAP-provided inbound API or communication scenario that allows CPI to push the document processing status back into the eDocument Cockpit after receiving the PAC response asynchronously. The customer needs to know which interface on S/4HANA Cloud Public Edition CPI should call to update the eDocument status in this scenario.

• SAP S/4HANA Cloud Public Edition

1. Configure and run Mexico eDocument using SAP_COM_0255 so that S/4HANA calls CPI synchronously and updates eDocument Cockpit from the same HTTP response.
2. Change the integration to an asynchronous CPI (iPaaS) framework where CPI receives the PAC response later.
3. Attempt to identify or use an inbound API to push the asynchronous status back to S/4HANA and observe that none is available in the supported scope.

Mexico eDocument in S/4HANA Cloud Public Edition is designed as a synchronous integration only. The standard architecture is: S/4HANA Cloud Public Edition calls CPI outbound via communication arrangement SAP_COM_0255, CPI forwards the document to the PAC (Edicom), receives the PAC response, and returns it to S/4HANA within the same HTTP transaction. S/4HANA then updates the eDocument Cockpit status. SAP_COM_0255 defines only outbound services from S/4HANA Cloud to CPI. As confirmed by the SAP development team, no inbound communication scenario currently exists in S/4HANA Cloud Public Edition that would allow an external system (such as CPI) to push eDocument status back to the eDocument Cockpit asynchronously. This is a product scope boundary, not a missing configuration.

There is no SAP-provided inbound API for asynchronous status callbacks in Mexico eDocument. 

• Option 1: Retain the synchronous architecture (recommended). Use the standard MexicoeDocument_edicom iFlow provided by SAP via communication arrangement SAP_COM_0255. In this architecture, S/4HANA Cloud Public Edition calls CPI outbound, CPI forwards the document to the PAC, and the PAC returns the response within the same HTTP transaction. This is the only fully supported integration path for Mexico eDocument in S/4HANA Cloud Public Edition.
• Option 2: Submit an enhancement request. If an asynchronous architecture is a business requirement, submit an enhancement request to SAP Product Management via the SAP Customer Influence program for evaluation and potential roadmap inclusion.

• Refer to: Integrating With SAP Integration Suite | SAP Help Portal
• Refer to: Submitting Customer Invoices Using SAP Integration Suite | SAP Help Portal
• Refer to: 3254343 - Submission of eDocument in Mexico is not successful
• Refer to: 2523263 - eDocument Mexico Troubleshooting Guide

eDocument, Mexico, CPI, Edicom, SAP COM 0255, Asynchronous, CFDI, iPaaS, Inbound API, Status Update, eDocument Cockpit, Communication Arrangement , KBA , CA-GTF-CSC-EDO-MX , Document Compliance Mexico , Problem