2025 Oct 06 5:29 PM - edited 2025 Oct 06 5:34 PM
This is my first time implementing the integration between SAP ERP and SAP Document and Reporting Compliance (DRC) for Peppol Exchange, following SAP’s official documentation:
https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/integrat...
However, I find the documentation quite high-level — it doesn’t go deep enough into the technical aspects, and I’m a bit confused about certain configuration points.
I’m currently implementing the integration between SAP ERP ECC 6.0 (SAP RISE) and SAP Document and Reporting Compliance (DRC) – Peppol Exchange for Belgium (BE).
So far, all the main configuration tasks have been completed:
The eDocument Cockpit is fully configured and working correctly in SAP ECC.
SAP DRC Peppol Exchange is deployed on SAP BTP (region: Frankfurt).
The ERP system is hosted on SAP RISE (region: Virginia).
The Cloud Connector is configured and connected to the corresponding BTP subaccount.
The Service Binding and Destination (DRC_PEPPOL) were successfully created in BTP.
A communication user with all necessary authorizations (SAP_BC_WEBSERVICE_SERVICE_USER, EDO_*, etc.) has been created.
The service endpoint in SOAMANAGER has been correctly configured and exposed according to SAP’s documentation at the following path:/sap/bc/srt/rfc/sap/dcppushservice/<xxx>/dcppushservice/pushrequest.
Despite all this, the connection between the ERP and the DRC Cloud Peppol service still cannot be established.
Ping tests return errors such as NIEHOST_UNKNOWN, NIECONN_REFUSED, or “Service Unreachable.”
At this point, I’m not sure whether the issue is related to:
Certificate or trust configuration between ERP and BTP,
A network limitation due to the cross-region setup (RISE Virginia ↔ BTP Frankfurt),
Or something missing in the Peppol participant configuration within the DRC instance.
Additionally, I’m unsure whether I should ask the client to explicitly allow outbound communication from the DRC Cloud service binding (created in BTP) through SAP’s internal firewall so that the ERP system can reach the endpoint.
If so, I would appreciate guidance on how this should be done — whether it should be managed directly in BTP Cockpit, via a SAP support ticket, or if it is enabled automatically once the binding is created.
Finally, the client assumes that XML ↔ UBL transformations must be handled via SAP Integration Suite (CPI), but based on my understanding, the standard SAP DRC solution should already manage these conversions internally.
Given that the ERP (RISE) and BTP environments are hosted in different regions, do I need to configure an additional SAP Cloud Connector or any special setup to enable secure communication between the two?
Or is the standard connection through the Service Binding and Destination configuration sufficient for DRC Cloud to reach the on-premise ERP?
According to SAP’s documentation, Peppol requires UBL BIS 3.0-compliant documents.
My main questions are:
Does the standard DRC solution automatically handle the XML → UBL BIS 3.0 transformation when sending eDocuments from SAP ERP to Peppol?
Conversely, when receiving documents from Peppol, does DRC automatically convert UBL BIS → XML so that it can be consumed by SAP ERP?
If these transformations are not handled natively, what’s the recommended approach to implement them?
Specifically, how can I connect SAP DRC Cloud with SAP Integration Suite (iFlow) to intercept and transform the payload (UBL/XML) before it reaches the ERP?
(I would really appreciate if anyone has implemented a similar setup or could share a best-practice example.)
I would also appreciate any insights on special settings that should be considered in the eDocument Cockpit for sending and/or receiving documents.
The client refers to their system as SAP RISE, but technically the backend is SAP ECC 6.0.
Are there any official SAP guidelines or technical notes describing the recommended configuration for this hybrid scenario (RISE + DRC Cloud) — especially regarding trust setup, certificates, or communication channels?
The existing SAP documentation seems too generic, so any deeper or experience-based guidance would be very helpful.
Thank you in advance for your help and insights!
Any detailed documentation, SAP Notes, or examples from similar Belgium Peppol implementations would be highly appreciated.
Request clarification before answering.
| User | Count |
|---|---|
| 14 | |
| 8 | |
| 6 | |
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.