Versions Compared

Old Version 7

changes.mady.by.user Mateusz Adamus

Saved on

compared with

New Version 8

changes.mady.by.user Izabela Bogorska

Saved on

Key

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

...

Parameter name

Description

Example

PI: Landscape where interface exists on the ABAP stack

Name of the PI ABAP Landscape. It is required to access the ABAP stack PI messages.

PI: ABAP stack: Read input message from Java persistence

This flag needs to be checked in the case when the ABAP stack PI read a message from the JAVA adapter  

PI: ABAP stack: Read output message from Java persistence

This flag needs to be checked in the case when the ABAP stack PI sends a message to the JAVA adapter

Test Case Execution

Parameter name

Description

Example

PI: Validate message status

SAP PI/PO message processing status will be

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).
It should be provided without PI endpoint & port. 

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/
create/1/{PONUMBER}/1

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

Do not fail TC if reference not found

This flag determines if in the situation when DB validation for reference messages have not been found whether it should be treated as Error or Successful message.

Checked or 'X' - if reference document is not found test case will not be failed

Unchecked or '' - if reference document is not found test case will be failed (default setting)

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.

Show XML in the correct order (unsorted)

This flag determines if the file lines in the XML Comparison Report should be displayed unsorted or should be sorted alphabetically for a specific nodes.

Checked or 'X' - payload will not be sorted on the report

Unchecked or '' - payload will be sorted alphabetically (default value)

Message Selector

Parameter name

Description

Example

PI: Message Search - Interface Name

Used to specify the Interface Name within which the Message Selector should search for the version of the message. This parameter is only to be entered if Interface Name visible in the Message Monitor main screen differs from the Interface Name used to create the object definition. 

If we only have receiver interfaces visible in the message monitor, then use the receiver name specified in the ICO of the sender interface specified in the automation object used.

PI: Message Search - Namespace

Used to specify the Interface Namespace within which the Message Selector should search for the version of the message. This parameter is only to be entered if Interface Namespace visible in the Message Monitor main screen differs from the Interface Namespace we have used to create the object definition.

The same condition as the previous parameter but then for the namespace of the receiver interface

...