PI Outbound

USE:

The test type PI Outbound allows testing a flow in which an SAP Backend (or another system) business document triggers the interface message. This message is processed in SAP PI/PO until the final version of an XML or flat file is ready to be sent to the 3rd party receiver.

That’s why, to execute this type of testing, you need to define an associated test case that will trigger the message from a business document.

Alternatively, if the application interface is based on SAP Output Control, there is a single test case approach described here: https://int4support.atlassian.net/wiki/spaces/IUM/pages/1407877121.

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

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

recording of user manual steps that caused triggering of interface message - for further reference, see eCATT Recording - Replication of manual steps
or
posting the 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
UI scripting in external software and calling Int4 IFTT by API

Steps for test case creation:

Depending on the testing scope, select the "IDoc outbound" Interface Type field for messages processed only in SAP Backend or "PI E2E Outbound" for messages processed through SAP PI/PO.
Select Document Number field and press (F4).
In IFTT PI/PO Message Selector type in: (Message Selector is available only for SAP PI/PO. Otherwise provide IDOC number in a Document Number field)
1. IFTT Object Definition used in the 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, e.g., Purchase Order number. Message Selector will help you with what value you should enter by passing the variable name and its description from the object definition (optionally if Automation Object contain a searching variable)
Process it (F8)
Check the content of the found messages to select an appropriate GUID that should be used as a test base from the generated list. Transfer the message using the Transfer selected button.
In the Parent ID field, enter the CaseID of the related triggering test case.

After completing the above steps, press the Save button to save a test case. After saving the Object Def. ID field should be updated automatically with relevant Object Definition ID.
The test case is ready to be executed.

OPTIONAL:
Suppose you don't want the test message to be delivered to the third-party system. In that case, you can configure canceling of the outbound message. As a result, the final XML message will be stored in the middleware without being sent. It doesn't affect the test results.