...
Testing of PI processing for a scenario using SAP B2B Splitter relies on PI message references. Such a scenario consists of separate ICOs used for receiving a collective message from the EDI partner and ICOs processing individual messages.
Since version 2.7.0, Int4 IFTT can be used to test these scenarios using a single test case. Instructions for configuring this scenario on older versions using , utilizing a combination of inbound and outbound test cases, can be found found here.
Example case
Example An example scenario in which we want to test the EDI Splitter is presented in the diagram below:
...
This article describes the part of the flow presented above flow related to the EDI Splitter, ie. . As an example, how to verify the operation both operations
before the Separator (the part between
...
"EDI Customer" and "Splitter")
after the Separator (the part between
...
"Splitter" and ECC system).
Testing the rest of the flow is described in the article Outbound Flat File scenario with 'PI Outbound' interface testing.
...
Testing the scenario described above requires the virtualization of an EDI Partner and uploading a collective message to the SAP PO.
...
and Outbound Processing Adapter Type: “EDI Separator”Separator.”
...
Automation Object creation.
Go to transaction transaction /INT4/IFTT_CONF and create a new object definition, e.g., providing the following data:
...
IFTT Automation Object and Description Object and Description can have any name. However, but in the Name and Namespace fields, we should provide the interface name and namespace used in the ICO of the tested interface.
For more info on how to fill this section, check Automation Object Definition.
2. Go to Variables and define Variable name and Variable description. Unlimited You can create an unlimited number of variables can be declared.
...
For more info on how to fill this section check Variables.
3. After selecting a single variable, move to to the Variable Processing Processing tab. Here you define actions for every variable declared in the previous step. For more specific information, check the Variable processing section. Be aware that for constructing XPath Expressions for flat files files, Expression language for flat files should be used.
...
4. Due to the fact, that the Since the tested interface uses a flat-file, in in the Additional Parameters tab tab, you should set parameters for flat-file interfaces and line separator as follows:
...
For more info on how to fill this section, please check Additional Parameters.
5. [Optionally create ] Create a number range that can be assigned to a specific variable or multiple variables in variable the variable processing section (in this example, the name of the defined number range is is $1). Thanks to this, so that we can overwrite the original numbers with the new test values. Please note that this is only needed if we do not want to send duplicates from original documents (e.g., sales orders to the final customer).
...
For more info on how to fill this section, check Number ranges.
Test Case creation
After creating and defining Automation Object, create and save the IFTT test case (provide . Provide Test case description, Interface Typeas as PI GUID E2E Inbound, Automation Object created above and choose reference message for tested interface):
...
Optionally, we can define define Payload Validation Ignore List, i.e., fields that should not be compared during verification between reference and current message. As an example, a difference in the generated document number or the date can be used here. For more info on how to use this section check , check the Payload Validation Ignore List.
...
Select created test case and click the “Execute Selected” button:
After processing the test cases, you will receive a Test Case Execution Result Report:
...