Parameters

Visibility

The visibility determines whether a parameter is an import parameter, an export parameter, or a local variable. You set the visibility in the parameter list.

Local variables can be used inside inline ABAP blocks. Import and export parameters cannot be used inside inline ABAP blocks.

Import Parameters

Import parameters are transferred when a test script is called. They are available locally in the test script. They can have default values which are used if no other value is passed in the call.

Import parameters are version-independent, that is, if you create a parameter in one version, it exists in all versions. This is important because it ensures a consistent interface for the test script.

Export Parameters

You can assign the test script result to an export parameter, which can be passed to a variable in the calling test procedure when you return from a test module.

Export parameters are version-independent, that is, if you create a parameter in one version, it exists in all versions. This is important because it ensures a consistent interface for the test script.

Local Variables

Local variables are used in test cases for calculations, or to receive export parameters from referred test cases or called function modules. They are also used for passing values to and from inline ABAP blocks.

Local variables are version-dependent, that is, a local variable defined in one version is not automatically defined in another version. For example, a parameter with a given name might be defined as type C in one version, type I in a second version, and not exist at all in a third version.

You can use an alias parameter as a work area within LOOP blocks. For more information, see LOOP .

Runtime Data Container

A runtime data container (RDC) is an instance of a test data container (TDC), or rather of one data set (variant) of a TDC. At runtime, an RDC contains parameters defined and named exactly as in the underlying TDC.

The RDC itself is a parameter with visibility C. The parameter reference is the name of the underlying TDC.

For more information, see Runtime Data Container .

Naming Convention

Names are alphanumeric strings with a maximum of 30 characters. The first character must be a letter or an underscore.

Copying Parameters from Other eCATT Objects

See Importing Parameters into Test Data Containers or Test Scripts .