Proxy Outbound

SAP Outbound Proxy interface name.

The correct interface can be found in the sxi_monitor in the Sender Interface column.

This parameter points out the system where the outbound proxy message is injected. The value should be a system line described in the landscape configuration.

Note:

If Backend system line for the current doc. has the same value as the Backend system line for the reference doc. (for instance, both are S4/HANA) then the RFC connection between the systems will be maintained both in:

a) the original environment of the reference document (for instance, production system)

b) the environment where the current test case execution takes place (for instance, development system) 

If Backend system line for the current doc. is different than the Backend system line for the reference doc. then, the RFC connection will be maintained only in the environment of the current execution (for instance, development system), but for both system lines (like ECC and S4HANA) 

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
Database Validations documentation can be read here.

Variable technical name

Free text for variable description

Type of variable processing

Scope determines the processing of procedures that generate unique values like, e.g., GUID or NUM_RANGE.

• Test Case Scope - variable is replaced with new values considering values from the currently processed test case. The variable value, which occurs multiple times in the test case payload, is replaced with the same new value. The variable value in different test cases from the currently processed test run is replaced with a new value for each test case.

• Test Run - variable is replaced with new values considering values from the currently processed test run. The variable value in different test cases from the currently processed test run is replaced with the same new value.

Int4 Suite will provide additional, more technical information in Test Execution Report during the running of the test cases if this parameter is set. Therefore, it is recommended to set this option initially and deactivate it when object definition is confirmed after executing the first test cases

Wait Flag indicating if Int4 Suite should stop test case execution after sending test case message to middleware. Int4 Suite will show the confirmation box, and the user will decide to continue. This setting can execute manual follow-up actions before running the next test case or checking the validations.

This setup works only with Execute via SAP GUI option of execution

Delay (in seconds) between test case execution ( sending message) and checking the results.

Delay (in seconds) between test run execution ( sending messages) and checking the results.

Provide a name for the number range. This name would be passed as a parameter in variable processing for actions that will generate values from it.

The alphanumeric characters to be appended at the beginning of the document number to separate original documents from source systems and the one created during Int4 Suite testing (optional).

The first number of our range.

The last number of our range.

When the number range is used during testing, it would increment per each use.

The alphanumeric characters to be appended at the end of the document number to separate original documents from source systems and the one created during Int4 Suite testing (optional).

If this box is checked, zeros will be automatically appended to the beginning of the document number, such as 000500.

If this indicator is selected, the number range is incrementing once per test run. If multiple test cases with the same Automation Object exist in the test run, they will receive the same value.

Rule type. Available options:

• Test Case Creation - in case you want to scramble data during the creation of a test case

• Runtime - in case you want to scramble data during runtime - when the interface is executed, and additional data is loaded to test case data.

Specify scrambling rule name for identification.

Choose a scrambling method from a list. Available methods:

• CONSTANT Replace value with constant
  The current value will contain the constant passed in the parameter. The constant should be provided as is without any brackets.

• GUID Generate GUID

  Generate random value in a GUID format. 

• RANDOM Generate a random value

  Generates a random value. The value of the parameter defines the upper limit of the range. It is also possible to generate negative numbers. For example, passing -100 in parameter will generate random numbers from -1 to -100

• HASH create a hash based on value
  Calculates a hash based on the given value using algorithm passed in parameter (default 'SHA1').

• MASK - replace each character with constant
  Replace each character with a constant passed in parameter. For example, passing X in the parameter will replace scrambled data with X signs.

• CUSTOM - create custom method
  create a CUSTOM method (implementing an interface /INT4/_IF_DATA_SCRMBL_METH).

Expression type. Available options:

• unspecified

• XPath

• Flat expression

This field is optional for all interfaces where there is a single type of output. However, for interfaces that output might be both XML and flat file, it is mandatory to specify the expression type.

Path pointing to the field/node where the exception should be applied.

Specify Processing Parameter suitable for a chosen scrambling method.

Proxy Message Version that is used by Int4 Suite to save the right messages from the XI Integration Engine Message Queue

Default value is ‘000’.

Tells the Int4 Suite to inject a message to the XI Integration Engine Message Queue.

Default value is ' ' (false).