Symptom
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.
Read more...
Environment
- SAP S/4HANA Cloud Public Edition
Product
Keywords
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
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview