PI E2E Synchronous test type is responsible for testing synchronous scenarios. In such cases, test validation is based on a receiver system response message and optionally on the documents created in SAP Backend.
The receiver system will not be virtualized. The connection must be working. The test validation will be performed based on the response from the receiver (after mapping in SAP PI/PO).
...
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 |
Inject using PIT | This flag will use SAP PIT WS as a message injector (SAP PO > 7.5 SP14) for this automation object. This flag can be set up also globally for whole environment. | |
|---|---|---|
HTTP RFC Destination | Alternative RFC Connection where the REST message should be sent. If this parameter is populated, then the message will be sent there alternative RFC. | SAPSYS1_RFC |
Direct HTTP URL | Direct endpoint to tested interface (synchronous). Additionally, if the URL is dynamic (like JSON queries), it is possible to enter the variable name in {} brackets. The value will be substituted before calling the final URL | /RESTAdapter/webshop/salesOrder/ |
Direct HTTP operation | If the direct endpoint is provided, here you can specify the HTTP operation (for synchronous REST testing) | PUT, GET, POST |
PI: Reference Sender Channel Name | Name of the sender channel to be used as a reference. | CC_SOAP_SENDER |
PI: Reference Sender Channel BC | Business Component of the sender channel to be used as a reference. | BC_SENDER |
PI: Reference Sender Channel Party | Party of the sender channel to be used as a reference. | SENDER_PARTY |
Flag for Flat File interfaces | Used to mark interface input as Flat File | |
Flat File Line Separator | The character used for end-of-line determination in Flat File messages: for example, CLRF - Unix. The parameter is used to display the comparison report better and display the reference and new message line by line. "Carriage Return and New line" character should be stored as CRLF "Line Feed" should be stored as LF (Unix based files) There is no default value, so the parameter is obligatory for CSV files | CLRF |
Test Case Validation
Parameter name | Description | Example |
PI: Validate message status | SAP PI/PO message processing status will be taken as a part of the test case result. By default, the processing status is not part of the test as such, for example, the communication channel may be deactivated not to send test messages. This option is helpful when performing validation of receiver communication channels. It would not validate the results of processing in the channel but at least collect SAP PO status. | |
PI: Validate message attachments | This flag allow to check SAP PI/PO message attachments as a part of the test. |
...