RFC Call

RFC Call test type allows calling and verifying of results of remote enabled function modules (including BAPIs) on system under test.

With the use of delivered function modules it is also possible to submit report (/INT4/IFTT_F_SUBMIT_REPORT) and call transaction with BDC data (/INT4/IFTT_F_CALL_TCODE) on target system.

Basic Information

Parameter name	Description	Example
Execution system line	System line where the RFC Call will be performed. Used during execution to determine system based on system line / landscape combination.	S42CLNT100

Parameters

Parameter name	Description	Example
Close RFC Connection	Used to execute each call in new session on target syste.	Yes/No
Call BAPI_TRANSACTION_COMMIT	Used to automatically add BAPI_TRANSACTION_COMMIT after execution.	Yes/No
Validate response	Used to indicate that the RFC response should be validated against reference XML	Yes/No

Execution Settings

Parameter name

Description

Example

Debug Log

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

Display wait popup before validation

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 between execution and validation

Parameter name	Description	Example
For each test case	Delay (in seconds) between test case execution ( sending message) and checking the results.	10
Once per test run	Delay (in seconds) between test run execution ( sending messages) and checking the results.	60

Database Validations

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
DB Validation Rulesets

GENERIC_SO

Persist reference DB Data

When switched on, DB reference data will be fetched from backend system during test case creation. Otherwise, it will be fetched during test case execution.

Automation Objects | Database Validations

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.

Variables & Variable processing

Create button allows variable creation.

Parameter name	Description	Example
Name	Variable technical name	VARIABLE_1
Description	Free text for variable description	Variable One
Type	Type of variable processing	Read & Replace Find message Custom
Scope	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.	Test Case Test Run