PI GUID E2E Inbound is a test that will inject the message to the SAP PI or SAP PO middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
...
Parameter name | Description | Example |
Database validation ruleset | Reference database validation ruleset object name. Database validation ruleset specify how related backend validation should be performed. Specify tables, fields and join conditions for the backend validation. Buttons allow navigation to the chosen database validation ruleset and creation of a new database validation ruleset | GENERIC_SO |
|---|
Variables
...
Variables are the container for values that can be used during testing. Each variable contains two values, the one that is calculated based on the reference message/document and the one that is calculated ad-hoc during test case execution.
Link to be added
Create button allows variable creation.
...
Parameter name | Description | Example |
PI: Ignore parent message during TC creation | This flag is used for scenarios with multiple receivers. If you create a test case based on the message that is part of the bigger scenario, then engine will search for the initial message that SAP PI/PO received. | |
|---|---|---|
Message version before processing | A version of the message to be fetched from the SAP PI/PO persistence. Here we specify the version which contains the original message - before being processed by SAP PI/PO. If empty, Global Parameter is used. | Depending on the SAP PI version can be either: numeric: 0 |
Message version after processing | A version of the message to be fetched from the SAP PI/PO persistence. Here we specify the version which contains after mapping version of the message - already processed by SAP PI/PO. If empty, Global Parameter is used. | Depending on the SAP PI version can be either: numeric: -1 |
PI: Allows Receiver interface be same as Sender interface | For pass-through interfaces In particular scenarios, sender and receiver interfaces may be the same, for instance, in the EDIFACT scenario. If this parameter is not provided and the sender is the same as the receiver interface, no test case would be created for such messages, or during execution, an error may occur. | X |
ABAP Stack SAP PI Integration
...