Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
If you want to test a country solution for one of the Peppol countries and you don't know where to start from, then you are in the right place.

As prerequisites, you must ensure that you have:

Peppol - Four corner model architecture

Testing with "yourself"

The easiest way to run an end-to-end test is to use for both Sender and Receiver an own Peppol participant ID. You should execute this type of test also if you don't plan to use both sending and receiving capabilities of the service in production.

Following Peppol's four corner model, the document is sent from your backend system (Corner 1 in the picture above), it will then reach the Sender Access Point (Corner 2), which will forward the document to the Receiver Access Point (Corner 3). Receiver Access Point will send the document to the final Receiver (Corner 4).

When testing with "yourself", the exchange is happening within the SAP Access Point (corner 2 & 3)

In your Peppol Exchange Service dashboard

  1. Register the participant in Master Data Management application of Peppol Exchange Service. Enable it for both sending and receiving documents.


In your backend system

  1. In the sender Company Code master data maintain the same identifier (VAT, GLN, Leitweg-ID, etc.) that you registered in the service, as described in the Master Data section of the country documentation relevant to your system release.

  2. Add an entry to EDOEUCOMPV view, corresponding to the Company Code and participant type used at point 1.

  3. Enable the Company Code for source type SRC_FILE in EDOCOMPANYACTIV view, to be able to receive incoming documents.

  4. Create a test Customer/Business Partner and maintain the same identifier you used for the company code at point 1. Follow the steps described in the Master Data section of the country documentation relevant to your system release.

  5. Add an entry to EDOEUBUPAV view, corresponding to the Customer/Business Partner and the participant type you used.

  6. Create a source document (FI or SD) and submit the generated electronic document from the eDocument Cockpit.

Remark: Always maintain your own participants in the Master Data Management and not participants of your customers.

If you set up your system as described above, you will be able to see both the outgoing and incoming documents in the eDocument Cockpit in your backend system. When you achieve that, it means that both your backend and service part of the solution are correctly configured and you are ready to test with customers or move the implementation to your productive system.

For more information about testing check the Testing Best Practices section of the documentation or the Attention points for testing blog post.

Please share your feedback and thoughts in a comment. If you have questions about SAP Document Compliance, you can post your question here.