Start Options

You can specify start options on the relevant tab. The visible tabs depend on the context.

Parameter Tab

This is for test scripts.

The import parameters of the test script are visible. You can enter values to be used for execution.

Variants Tab

This is for test configurations.

You can select to execute the test configuration using either external variants or internal variants.

External Variants

The checkbox External Variants must be selected to use external variants. The default folder for the file containing the external variants is specified in the user-specific settings. The default file is specified in the test configuration.

Internal Variants

The checkbox External Variants must be unselected to see and use internal variants.

The variants to be executed are marked in the Execute Variant field. The default setting for each variant in set in the test configuration editor. Here, you can override the defaults. You can do this individually for each variant.

In the Special, Generic field, you can restrict the variants to be executed:

·        By entering an asterisk (*), all variants except ECATTDEFAULT are executed.

·        By entering a string followed by an asterisk, all variants whose names start with the entered string are executed. For example, TEST*.

·        By entering a string, only that variant is executed.

You can also overwrite the values for the ECATTDEFAULT in the ECATTDEFAULTRUN row.

Shared Tab


Error Behavior

You can specify how eCATT reacts to an error in a test.

You can choose from the following:

·        Termination. Execution continues with the next variant.

·        Termination. Execution continues with the next test configuration.

·        Termination of the start process. Execution does not continue.

·        No termination. Execution continues with the next script command.

Debug Mode

You can specify if and when eCATT executes in the eCATT debugger.

You can choose from the following:

·                Normal Breakpoint Handling, Stop at BREAK

·                Execution with Immediate Debugging

·                Stop When an Error Occurs

·                Ignore Breakpoints (Default for Collective Execution)

Execution Control

When you select Execution Control, a dialog is available during replay in which you can pause or  stop the script, or jump into the debugger. Any such user interaction will be recorded in the log.

System Data

When starting a test, you can choose to use a system data container other than the one specified in the test configuration or test script.

You can also choose a different target system instead of the default target system. The default target system is:

·        The maintenance target system when executing a test script alone from within the eCATT development environment.

·        The target system of the test configuration when executing a test configuration. The maintenance system of the test script is not relevant.

Commands having a specific target system will be executed in that system. If the system is neither physically available nor in the system data container, an error will result.


If you want the log to be displayed automatically at the end of a test, select Display Log.

If you want the archive flag to be set for the generated log, select Archive.


You can specify that RFC connections be closed after a script or variant has been executed. See RESCON for more information about closing RFC connections.

You can specify whether synchronous or asynchronous RFC should be used for remote access.

UI Control Tab

Start Modes for TCD

You can override the TCD mode of test scripts.

You can choose from the following start modes for TCD commands:

·        Display all (process in foreground), synchronous local

·        Error (display errors only), synchronous local.

·        Display nothing (process in background), synchronous local.

·        No display (process in the background), asynchronous update

·        (Empty) Use the default

·        Display nothing (process in background), synchronous not local

For information about database updates, see Programming Database Updates.

Start Options for SAPGUI

Execute all SAPGUI commands in a single session. Select this to override the SessionId and ConnectionId in each command interface so that they all have the same values. An example use is when you have rerecorded sections of a script and you suspect that an error in the replay is due to a wrong SessionId or ConnectionId.

Highlight GUI elements. This marks the GUI elements that are currently being controlled during replay. It makes it easier to see what is happening on the screen. You can specify the time delay under Utilities ® Settings ®eCATT ® Execution.

Minimize eCATT GUI. Minimizes the eCATT GUI when SAPGUI commands are being replayed.

The playback modes are:

·        Optimized performance. Automation calls are placed in the automation queue.

·        Synchronous GUI control. Automation calls are not queued.

You can choose from the following error modes:

·        Terminates on any error.

·        Continue Value. Terminates for most errors but continues if a field value could not be delivered.

·        Continues after every error.

In the Stop Whenfield, you can select points where playback should pause – for example, at each SAPGUI command. This is for debugging purposes although by default it does not open the debugger. If you want to spring to the debugger when the playback stops, select Stop in Debugger.

You can choose to close generated sessions. In the GUIs Close field, you can choose:

·        Close Generated Session After Script. All GUIs will be closed at the end of the execution of the test script.

·        Close Generated Session After REF. At the end of each REF command, all sessions opened by the REF will be closed.

·        Do Not Close Generated Sessions. This is for when you are interested in the final state of a GUI after the execution of a test script.


Save Screenshots. Select this to automatically take screenshots during replay. You can select the following positions for the screenshots:

·        In case of error (mode 1)

·        Before user input (mode 2)

·        After user input (mode 3)

·        After each property/method call (mode 4)

The screenshot name contains the mode so you can tell where it was taken in relation to a command..

The screenshots are saved to the path specified in the field Screenshot Path. You can temporarily over-ride the default path by choosing Change. The default path for the file containing the external variants is specified in the user-specific settings. 

Separate Directory for this Activity. If you select this, all the screenshots taken during a replay will be stored in a new folder. The folder name consists of the system name and the eCATT log number.

Web Dynpro

You can specify foreground or background execution. In addition, you can start in background mode and automatically change to foreground when an error occurs. You can select from the following options:

·        Background Processing

·        Foreground Processing

·        Foreground Processing (Parallel Display of Recorded Screens)

For foreground processing and foreground processing with the parallel display, you can specify how long screens should be displayed.

Start Options for an External Tool

You can select from the following start modes:

·        Normal mode. Runs without debugging or the user interface of the external tool.

·        Debug mode. Runs with the user interface of the external tool.

·        Runs with the user interface of the external tool. No debugging.

You can enter the user name and password for the external tool. If you do not enter these here, you will need to enter them the first time a REFEXT or SENDEXT command is called.

Breakpoints Tab

Here you specify break points for the eCATT debugger.

The entries on this tab do not disappear after each execution. You can deactivate a breakpoint by selecting Inactive, or you can permanently delete a breakpoint.

Script Line

You can set script-specific breakpoints. For each breakpoint that you want to set, you specify the  test script name, the version, and the line number. You can set several breakpoints in the same or different test scripts. If you view a script in the test script editor, you will see the lines with breakpoints highlighted in color.

Command and Object

You can set breakpoints at eCATT commands. Breakpoints that you specify here are valid for all test scripts. You can further restrict the breakpoints by specifying an object for the command. For example, if you only specify LOG, the debugger will stop at all LOG commands, but if you further specify A for the object, the debugger will only stop at LOG ( A ).