...
PI GUID / IDOC Inbound interface types are very similar in a the matter of a test case creation. These types of testing allow testing allows to test a flow flow end-to-end in SAP, in which a . A message is processed through SAP PI/PO, enters SAP Backend, and triggers the creation of a business document like , Sales Order, Purchase Invoice, Material Movement, and others.
Info |
---|
PREREQUISITES:
|
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 . Then IFTT will compare the reference document and a document created based on a copy of the 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 for the Interface Type field. | 1. Select "PI IDOC E2E Inbound" for for the Interface Type field. |
2. Select Document Number field and enter message GUID of processed SAP PI/PO message or press (F4). int4 Int4 IFTT Message Selector screen will open (read int4 IFTT PI/PO Message Selector new ) | 2. In the Document Number field, type the number of the IDoc the IDoc that should be used as a test base |
After completing the 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
The test case is ready to be executed.
...