In this article you will learn:<\/h2>\n\n- The concept of EDI message splitting using SAP PI B2B EDISeparator,<\/li>\n
- How to test such cases using the Int4 IFTT.
\n<\/div><\/li>\n<\/ul>\n
\nReading time: 6 minutes<\/span><\/strong><\/p>\n<\/p>\n<\/div><\/span><\/strong><\/p>\nIntroduction<\/h3>\n
Int4 IFTT is a tool that allows testing of different types of SAP interfaces and business scenarios. Many of them use the EDI (Electronic Data Interchange) standard to communicate business objects like sales orders, invoices, etc. between business partners. EDI allows the interchange of data between many partners without modifications or developments of new interfaces for every partner because it provides a generic and standardized definition of business documents. And therefore this type of communication is often used in B2B (Business-to-Business) scenarios, where there is a need to exchange large amounts of data between trading companies. In order to optimize such processes, instead of sending multiple messages separately a more efficient solution may be to transfer one EDI file containing many transaction data which can be divided into individual messages. On the one hand, such a solution may provide benefits through the reduction of transmission costs (because of sending single instead of multiple files), but on the other hand, it may complicate the interface logic. But for this purpose, you can use the Int4 IFTT tool, thanks to which you will be able to test such scenarios. And in case of changes or developments in the interface logic, apply automatic regression testing<\/a> as well.<\/p>\n <\/p>\n
EDI Splitter test scenario<\/h3>\n
This article covers testing of a scenario where several purchase orders are created from one input EDI message after processing in SAP PI\/PO<\/a> (thus a process in relation: single input to multiple outputs). An example of such a B2B integration scenario in which the Splitter<\/em> adapter is used is presented in Figure 1.<\/em><\/p>\n![\"EDI](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/Figure-1.-EDI-Splitter-test-scenario-diagram.png\")
<\/a><\/p>\nFigure 1. EDI Splitter test scenario diagram.<\/em><\/p>\n
\nThe presented case consists of two ICOs (Integrated Configurations) in SAP PI<\/a>, whose basic technical information are as follows:<\/p>\n1. The first ICO receives a collective EDI message from the EDI partner and sends it to the EDISeparator<\/em> adapter (Outbound Processing<\/em> tab in Figure 2<\/em>):
\n![\"Input](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/pasted-image-0.png\")
<\/a><\/p>\nFigure 2. Input ICO’s Outbound Processing configuration.<\/em><\/p>\n
\n2. The second ICO receives the collective message via the EDISeparator<\/em> channel (Inbound Processing<\/em> tab in Figure 3<\/em>) and then the message is being separated and filtered by type to single IDOCs:<\/p>\n![\"OutputI](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/pasted-image-0-1.png\")
<\/a><\/p>\nFigure 3. Output ICO’s Inbound Processing configuration.<\/em><\/p>\nConfiguration in Int4 IFTT<\/h3>\n
In order to test SAP PI\/PO processing for a scenario using a B2B EDI Splitter we need to connect two types of the Int4 IFTT test cases (of type PI GUID E2E<\/em> Inbound<\/em> and PI E2E Outbound<\/em>). We cannot use the standard PI Unit Test<\/em> type, because the scenario consists of two separate ICOs.<\/p>\n\n- The “parent” test case is used to virtualize<\/a> the EDI Partner and validate the first part of the process, i.e. uploading a collective EDI message (example in the Listing 1<\/em>) to the Middleware Platform.<\/li>\n<\/ul>\n<\/div>\n
UNA:+.? '\r\n\r\nUNB+UNOA:3+0000000EDI_T:ZZ+0000000ECC:ZZ+20051107:1159+6002'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05847+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05848+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05849+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNZ+1+6002<\/pre>\nListing 1. Example input EDI message.<\/em><\/p>\n
\nAs you can see, the incoming EDI message consists of three same messages which in the next step will be divided into single messages. In order to identify each of these messages in the Int4 IFTT automation<\/a> object you should define a unique variable (in this case purchase order number) which will allow to connect the input and output the Int4 IFTT test cases:<\/p>\n![\"Configuration](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/Figure-4.-Configuration-of-the-IFTT-automation-object-for-input-test-case.png\")
<\/a><\/p>\nFigure 4. Configuration of the Int4 IFTT automation object for input test case.<\/em><\/p>\n
\n\n- The role of subsequent “child” test case(s) is to find the relevant single messages from collective messages processed in the first test case and then compare their values after mapping with a prepared pattern. For this purpose test cases are connected to each other. As already mentioned, automation object for “child” test case have defined variables that take the value from the previous test case, so that they can be linked together:
\n<\/div><\/li>\n<\/ul>\n![\"Configuration](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/Figure-5.-Configuration-of-the-IFTT-automation-object-for-output-test-case.png\")
<\/a><\/p>\nFigure 5. Configuration of the Int4 IFTT automation object for output test case.<\/em><\/p>\n
\nTesting in Int4 IFTT<\/h3>\n
After creating the appropriate automation objects configuration, you can go to the Int4 IFTT Cockpit and create test cases for interfaces. In tested scenario there is one input EDI message and three IDOC output messages, therefore you should create one test case of type PI GUID E2E Inbound<\/em> and three test cases of type PI E2E Outbound<\/em>:<\/p>\n![\"Created](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/Figure-6.-Created-IFTT-test-cases.png\")
<\/a><\/p>\nFigure 6. Created Int4 IFTT test cases.<\/em><\/p>\n
\nHowever, attention should be paid to defining the Parent ID for “child” test cases (marked with a yellow frame in the Figure 6<\/em>) to correctly link them together.<\/p>\nFinally, select all created Int4 IFTT test cases and execute them. As a result you will receive the Test Execution Report<\/em> visible in Figure 7<\/em>.<\/p>\n![\"Int4](\"https:\/\/int4.com\/wp-content\/uploads\/2020\/11\/Figure-7.-Int4-IFTT-Test-Execution-Report.png\")
<\/a><\/p>\nFigure 7. Int4 IFTT Test Execution Report.<\/em><\/p>\nSummary<\/h2>\n
The EDI splitting is a common approach in B2B integration and it is important to correctly test and prevent errors in such scenarios. Therefore, bear in mind that testing even complex SAP interfaces can be facilitated and automated with the use of Int4 IFTT tool. If you would like to learn more about the testing approach presented in this article, I encourage you to read the detailed documentation<\/a> available on Int4 IFTT Wiki Page.<\/p>\nAnd if you want to find out more about this (or other) Int4 IFTT features, just book a consultation<\/a>\u00a0with the product demo or contact us.<\/a><\/p>\n <\/p>\n
Read also:<\/h5>\n
1. Get advantage of the Int4 IFTT IDoc Message Selector during Test Case creation<\/a><\/p>\n
- \n
- The concept of EDI message splitting using SAP PI B2B EDISeparator,<\/li>\n
- How to test such cases using the Int4 IFTT.
\n<\/div><\/li>\n<\/ul>\n
\nReading time: 6 minutes<\/span><\/strong><\/p>\n
<\/p>\n<\/div><\/span><\/strong><\/p>\n
Introduction<\/h3>\n
Int4 IFTT is a tool that allows testing of different types of SAP interfaces and business scenarios. Many of them use the EDI (Electronic Data Interchange) standard to communicate business objects like sales orders, invoices, etc. between business partners. EDI allows the interchange of data between many partners without modifications or developments of new interfaces for every partner because it provides a generic and standardized definition of business documents. And therefore this type of communication is often used in B2B (Business-to-Business) scenarios, where there is a need to exchange large amounts of data between trading companies. In order to optimize such processes, instead of sending multiple messages separately a more efficient solution may be to transfer one EDI file containing many transaction data which can be divided into individual messages. On the one hand, such a solution may provide benefits through the reduction of transmission costs (because of sending single instead of multiple files), but on the other hand, it may complicate the interface logic. But for this purpose, you can use the Int4 IFTT tool, thanks to which you will be able to test such scenarios. And in case of changes or developments in the interface logic, apply automatic regression testing<\/a> as well.<\/p>\n
<\/p>\n
EDI Splitter test scenario<\/h3>\n
This article covers testing of a scenario where several purchase orders are created from one input EDI message after processing in SAP PI\/PO<\/a> (thus a process in relation: single input to multiple outputs). An example of such a B2B integration scenario in which the Splitter<\/em> adapter is used is presented in Figure 1.<\/em><\/p>\n
<\/a><\/p>\nFigure 1. EDI Splitter test scenario diagram.<\/em><\/p>\n
\nThe presented case consists of two ICOs (Integrated Configurations) in SAP PI<\/a>, whose basic technical information are as follows:<\/p>\n
1. The first ICO receives a collective EDI message from the EDI partner and sends it to the EDISeparator<\/em> adapter (Outbound Processing<\/em> tab in Figure 2<\/em>):
\n<\/a><\/p>\nFigure 2. Input ICO’s Outbound Processing configuration.<\/em><\/p>\n
\n2. The second ICO receives the collective message via the EDISeparator<\/em> channel (Inbound Processing<\/em> tab in Figure 3<\/em>) and then the message is being separated and filtered by type to single IDOCs:<\/p>\n
<\/a><\/p>\nFigure 3. Output ICO’s Inbound Processing configuration.<\/em><\/p>\n
Configuration in Int4 IFTT<\/h3>\n
In order to test SAP PI\/PO processing for a scenario using a B2B EDI Splitter we need to connect two types of the Int4 IFTT test cases (of type PI GUID E2E<\/em> Inbound<\/em> and PI E2E Outbound<\/em>). We cannot use the standard PI Unit Test<\/em> type, because the scenario consists of two separate ICOs.<\/p>\n
- \n
- The “parent” test case is used to virtualize<\/a> the EDI Partner and validate the first part of the process, i.e. uploading a collective EDI message (example in the Listing 1<\/em>) to the Middleware Platform.<\/li>\n<\/ul>\n<\/div>\n
UNA:+.? '\r\n\r\nUNB+UNOA:3+0000000EDI_T:ZZ+0000000ECC:ZZ+20051107:1159+6002'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05847+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05848+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNH+000000101+ORDERS:D:96A:UN:EAN008'\r\n\r\nBGM+220+DD05849+9'\r\n\r\nDTM+137:20051107:102'\r\n\r\nNAD+BY+00500100::9'\r\n\r\nNAD+SU+4012345000094::9'\r\n\r\nLIN+1+1+CE_EXC_100:IB'\r\n\r\nQTY+1:10'\r\n\r\nLIN+2+1+CE_EXC_300:IB'\r\n\r\nQTY+2:10'\r\n\r\nLIN+3+1+CE_EXC_CLAMP:IB'\r\n\r\nQTY+3:10'\r\n\r\nFTX+AFM+1++XPath 2.0 Programmer's Reference'\r\n\r\nUNS+S'\r\n\r\nCNT+2:4'\r\n\r\nUNT+22+SSDD1'\r\n\r\nUNZ+1+6002<\/pre>\n
Listing 1. Example input EDI message.<\/em><\/p>\n
\nAs you can see, the incoming EDI message consists of three same messages which in the next step will be divided into single messages. In order to identify each of these messages in the Int4 IFTT automation<\/a> object you should define a unique variable (in this case purchase order number) which will allow to connect the input and output the Int4 IFTT test cases:<\/p>\n
<\/a><\/p>\nFigure 4. Configuration of the Int4 IFTT automation object for input test case.<\/em><\/p>\n
\n- \n
- The role of subsequent “child” test case(s) is to find the relevant single messages from collective messages processed in the first test case and then compare their values after mapping with a prepared pattern. For this purpose test cases are connected to each other. As already mentioned, automation object for “child” test case have defined variables that take the value from the previous test case, so that they can be linked together:
\n<\/div><\/li>\n<\/ul>\n<\/a><\/p>\nFigure 5. Configuration of the Int4 IFTT automation object for output test case.<\/em><\/p>\n
\nTesting in Int4 IFTT<\/h3>\n
After creating the appropriate automation objects configuration, you can go to the Int4 IFTT Cockpit and create test cases for interfaces. In tested scenario there is one input EDI message and three IDOC output messages, therefore you should create one test case of type PI GUID E2E Inbound<\/em> and three test cases of type PI E2E Outbound<\/em>:<\/p>\n
<\/a><\/p>\nFigure 6. Created Int4 IFTT test cases.<\/em><\/p>\n
\nHowever, attention should be paid to defining the Parent ID for “child” test cases (marked with a yellow frame in the Figure 6<\/em>) to correctly link them together.<\/p>\n
Finally, select all created Int4 IFTT test cases and execute them. As a result you will receive the Test Execution Report<\/em> visible in Figure 7<\/em>.<\/p>\n
<\/a><\/p>\nFigure 7. Int4 IFTT Test Execution Report.<\/em><\/p>\n
Summary<\/h2>\n
The EDI splitting is a common approach in B2B integration and it is important to correctly test and prevent errors in such scenarios. Therefore, bear in mind that testing even complex SAP interfaces can be facilitated and automated with the use of Int4 IFTT tool. If you would like to learn more about the testing approach presented in this article, I encourage you to read the detailed documentation<\/a> available on Int4 IFTT Wiki Page.<\/p>\n
And if you want to find out more about this (or other) Int4 IFTT features, just book a consultation<\/a>\u00a0with the product demo or contact us.<\/a><\/p>\n
<\/p>\n
Read also:<\/h5>\n
1. Get advantage of the Int4 IFTT IDoc Message Selector during Test Case creation<\/a><\/p>\n
- The role of subsequent “child” test case(s) is to find the relevant single messages from collective messages processed in the first test case and then compare their values after mapping with a prepared pattern. For this purpose test cases are connected to each other. As already mentioned, automation object for “child” test case have defined variables that take the value from the previous test case, so that they can be linked together:
- The “parent” test case is used to virtualize<\/a> the EDI Partner and validate the first part of the process, i.e. uploading a collective EDI message (example in the Listing 1<\/em>) to the Middleware Platform.<\/li>\n<\/ul>\n<\/div>\n