...
ICO 1: Asynchronous outbound request interface [SI 1] → Synchronous inbound interface [SI 2] (testing of this part is described in Part A. PI Inbound Testing below),
ICO 2: Asynchronous outbound response interface of the receiver [SI 3] → Asynchronous inbound response interface [SI 4] (testing of this part is described in Part B. PI Outbound Testing below).
Procedure
Part A. PI Inbound Testing
...
IFTT Automation Object and Description can have any name. However, in the Name and Namespace fields, we should provide the interface name and namespace used in our ICO. For more info on how to fill this section, check Automation Object Definition.
| Info |
|---|
Please note that you can use the SAP PI/PO Wizard instead of creating an automation object manually. |
...
In the second part, we will create a test case of type PI E2E Outbound connected with the test case from part A. For this purpose, test cases will be connected using the test case property: “Parent ID.” The automation object for the second ICO will also have defined a variable that will take the value from the previous case. Thanks to that, they can be linked together (in this example, it is variable “MATNR” corresponding to the material number included in the request SOAP message).
...
| Info |
|---|
Please note that similar to part A above, you can use the SAP PI/PO Wizard instead of creating automation objects manually. |
...
The procedure is the same for the variable MATDESC, as shown in Part A (for variable MATNR). That means we need to define a path in the response message based on which we will take the value for the MATDESC variable:variable:
...