When setting up your system, you create a service instance for the SAP Document and Reporting Compliance, cloud edition to connect with your business system. For that, you have followed the steps described in the Creating a Service Instance for the Cloud Edition.
All service instances created before April 26, 2023, were delivered with a direct communication with the component part of SAP Document and Reporting Compliance, cloud edition. However, starting from April 2023, as part of our product evolution, we introduced an API layer aimed at unifying and simplifying the process of exchanging electronic documents and submitting reports across different scenarios.
What does this mean? If you have onboarded SAP Document and Reporting Compliance, cloud edition prior to April 26, 2023, you need to recreate the service instance to be able to leverage the latest API layer. This is a prerequisite to use any scenario published and supported by SAP Document and Reporting Compliance, cloud edition after April 26, 2023.
Creating two process instances within the same subaccount is not possible. Hence, you are presented with two alternatives:
- Establishing a new subaccount along with a new service instance.
- Deleting the current service instance and re-creating it.
Create new subaccount and new service instance
For creating a new subaccount and service instance, you follow the steps described in the Initial Setup page on the SAP Help Portal. Additionally, follow the integration steps specific to your scenario.
Delete current service instance and recreate it
For deleting the current service instance, follow the steps described in Deleting Service Instances. For recreating it, the steps vary depending on the authentication type you use. Consider the following:
- When using OAuth 2.0 Client Authentication or SSL Client Certificate Authentication, perform all steps as described under Integration for your scenario.
- When using User Provided SSL Client Certificate Authentication, perform all steps described under Integration for your scenario, except the PSE configuration in the STRUST as you will use the same certificate.
If you use the same subaccount for Peppol, you don’t need to set it up again as long as you create a new service binding using the same certificate you were using before. That is because, for the Peppol Exchange process, the host has not been changed with the addition of the new API.
It’s just a few steps and you’ll be setup for the future - if you need to connect multiple back-end systems to SAP Document and Reporting Compliance, cloud edition, or exchange documents and reports with different countries/regions, you can use the same process instance to incorporate both OAuth (EHP8 for SAP ERP 6.0 – SP 23 and higher) and certificate-based (EHP8 for SAP ERP 6.0 – SP 22 and lower) authentications. In that case, you can create three service bindings to accommodate all configurations:
- Peppol
- Others - oAuth
- Others - Certificate
Remember that the combination of OAuth and certificate-based authentication is only necessary if the backend systems are running on multiple versions of the back-end systems. Otherwise, you can reuse the oAuth authentication between your backend systems.
We hope you find this information useful. You can leave a comment on this blog or follow us for more information about SAP Document and Reporting Compliance here in SAP Community.
