Versions Compared

Old Version 7

changes.mady.by.user Mateusz Nowak

Saved on

compared with

New Version Current

changes.mady.by.user Izabela Bogorska (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

USE:

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

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

Alternatively, if the application interface is based on SAP Output Control, there is a single test case approach described here: Outbound test cases with triggering the Output Control.

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

Info

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

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

  • posting of 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 Document Number selectiontest case creation:

  1. Select Depending on the testing scope, select the "IDoc outbound" Interface  Interface Type field for messages processed only in SAP Backend or "PI E2E Outbound" for messages processed through SAP 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 a Document Number field)

    1. IFTT Object Definition used in the current test case. Confirm with with enter for  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. number, e.g., Purchase Order number. Message Selector will help you with what value you should be entered enter by passing the variable name and its description from the 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 a test base from the generated list. Transfer the message using using the Transfer selected button button.

  6. In the Parent ID field, enter the CaseID of the related triggering test case. 

After completing the above steps, press the the Save button  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.

Info

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

...