Once we deliver the first one or first two interfaces the testing starts to get more tricky ad we cannot just repost a single message in SAP Process Orchestration to test the whole flow as the integration scenario depends on the previously created business objects (like Purchase Order). As you can see we have three interfaces from Ariba:Ī) interface 1 - creating a Purchase order ( SAP Process Orchestration and ABAP enhancements/SAP customizing)ī) interface 2 - creating a Goods Receipt to the Purchase order ( SAP Process Orchestration and ABAP enhancements/SAP customizing)Ĭ) interface 3 - creating an Invoice to the previous documents ( SAP Process Orchestration and ABAP enhancements/SAP customizing) Let’s imagine a typical flow where Ariba is creating a Purchase Order in S/4HANA then posts a Goods Receipt and at the end sends an Invoice. While working with many SAP cloud applications and trying to connect them to the SAP ECC or S/4HANA system we quite often tend to struggle with one thing - lack of test data.

Ariba edi integration