Page Comparison

USE:

The test type PI Outbound interface type allows you to test a flow in which a SAP Backend’s business document triggers the interface and continues message and this message is processed in SAP PI/PO until the final version of an XML message or flat file is ready to be sent out to the 3rd party receiver by middleware.
That’s why, in order to execute this type of a test case testing you need to define a trigger of an outbound message.Trigger associated test case, that will trigger the message from SAP Backend.

During the test case execution, the PI outbound type will listen if particular message was processed in SAP PI/PO. If so, it would fetch the content and compare it with the reference.

Associated test case to trigger of an outbound message from SAP Backend:

• manual test case recording of user manual steps that caused triggering of interface message - for further reference see eCATT Recording - Replication of manual steps
  or

• posting of inbound message can trigger the response. For example, the typical case is posting a sales order IDOC will trigger another IDOC with sales order response - for further reference see: PI GUID Inbound interface and PI IDOC Inbound interface

...

1. Select "IDoc outbound" Interface  or “PROXY outbound” Interface Type field for IDOC messages processed directly to ERP only in SAP Backend or "PI E2E Outbound" for messages processed through middlewareSAP PI/PO.

2. Select Document Number field and press (F4).

3. In IFTT PI/PO Message Selector type in:  (Message Selector is available only for SAP PI/PO. Otherwise provide IDOC number or proxy GUID in Document Number field)

   1. IFTT Object Definition used in current test case. Confirm with enter for changes to take place. 

   2. Date range within which IFTT should search for the messages on SAP PI/PO

   3. Message number i.e. Purchase Order number. Message Selector will help you with what value should be entered by passing the variable name and its description from object definition . (optionally if Automation Object contain a searching variable)

4. Process it (F8)

5. Check the content of the found messages to select an appropriate GUID that should be used as test base from the generated list. Transfer the message using Transfer selected button.

6. In the Parent ID field enter the CaseID of the related inbound message or manual triggering test case recording. 

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.