USE:
PI Outbound interface type allows you to test a flow in which a business document triggers the interface and continues until the final version of an XML message 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 you need to define a trigger of an outbound message.
Trigger of an outbound message:
manual test case - for further reference see eCATT Recording - Replication of manual steps
orinbound message - for further reference see: PI GUID Inbound interface and PI IDOC Inbound interface
| Info |
|---|
OPTIONAL: |
Steps for Document Number selection:
| Info |
|---|
PREREQUISITES: |
Select "IDoc outbound" Interface Type field for IDOC messages processed directly to ERP or "PI E2E Outbound" for messages processed through middleware.
Select Document Number field and press (F4).
In IFTT PI/PO Message Selector type in:
IFTT Object Definition used in current test case. Confirm with enter for changes to take place.
Date range within which IFTT should search for the messages on PI
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.
Process it (F8)
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.
In the Parent ID field enter the CaseID of the related inbound message or manual 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.