USE:
PI GUID / IDOC Inbound interface types are very similar in a matter of a test case creation. These types of testing allows to test a flow end-to-end in SAP, in which a message is processed through SAP PI/PO, enters SAP Backend and triggers creation of a business document like, Sales Order, Purchase Invoice, Material Movement and others.
PREREQUISITES:
You have completed the steps described in General rules for a test case creation
The automation object for end-to-end test is already prepared. See the Configuration section for details
In both cases, the test cases are created based on SAP PI/PO input message. Thanks to the Automation Object chosen for the test case, Int4 IFTT will be able to identify the document created in SAP Backend and perform the comparison of a reference and a document created based on copy of input message.
Steps for Document Number selection:
PI GUID Inbound - Creates a test case based on SAP PI/PO message GUID number | PI IDOC Inbound - Creates a test case based on SAP Backend IDOC (only for IDoc interfaces, the message SAPI PI/PO message GUID is fetched from IDOC control record) |
|---|---|
1. Select "PI GUID E2E Inbound" for Interface Type field. | 1. Select "PI IDOC E2E Inbound" for Interface Type field. |
2. Select Document Number field and enter message GUID of processed SAP PI/PO message or press (F4). int4 IFTT Message Selector screen will open (read int4 IFTT Message Selector new ) | 2. In Document Number field type the number of the IDoc that should be used as test base |
After completing above steps hit on Save button to save a test case. After saving the Object Def. ID field should be updated automatically with relevant Object Definition ID.
Test case is ready to be executed.