What is the difference to the previous version?
Peppol Exchange service for the Cloud Edition of SAP Document and Reporting Compliance | SAP Document and Reporting Compliance, Cloud Edition | |
Scope of the services | The names of the services indicate the different scopes already. The Peppol Exchange service is a standalone service that focuses only on the business scenarios related to the Peppol network - you can send and receive electronic documents through the Peppol network or validate documents for compliance. | In the new cloud edition, Peppol Exchange is not a standalone service but one of multiple processes that can be covered. You can even send invoices to countries other than those participating in the Peppol network. |
Technical differences | The Peppol Exchange service runs in subaccounts managed by SAP. With those subaccounts, you can't make your own configurations for the service. If you also use other SAP services in SAP BTP, you may even find that this is not the standard method for services in SAP BTP. | The new cloud edition, like most other services on SAP BTP, runs in subaccounts that you manage yourself in your SAP BTP global account. This means that you now have one entry point where you can access your SAP BTP services. In that entry point the set up of all the services works the same. So you only have to learn once how to set up a service on SAP BTP and then you know it for most of the other services as well. |
Applications | In the Peppol Exchange service, you have separate apps to manage users, set up connections with your business systems and to meter the application usage. | In the cloud edition, all those activities can be done in the SAP BTP Cockpit, like for most other services. |
Testing | For the Peppol Exchange service, both in the test subaccount and in the productive subaccount, your Peppol participants are registered with the registration service for productive participants (SML). To ensure that invoices used for testing are not unintentionally considered real invoices, the service uses a different ID for your Peppol participant in the test subaccount by adding "_test". | For the cloud edition, this is handled more clearly. In your test subaccount, you can no longer create Peppol participants using the productive participant registration service (SML). Therefore, you can also no longer send test invoices to customers who are active in production. Now, when you register a participant in your test subaccount, then the participant is automatically created using the registration service for test participants (SMK). It is no longer necessary to create participants with "_test". If you need more details about how it works now, you should check out this blog about Testing the Peppol Exchange Process with Your Business Partner! |
Why should I migrate sooner than later?
How do I migrate?
Where can I find more information about the new cloud edition?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
23 | |
11 | |
8 | |
7 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 |