The screen is displayed in a simulation mode in the screen flow logic detail view (for both the TCD function and the function module test). This mode replaces the screen list display from up to release 4.0B. It has the following additional functions:

• possible entries help (F4) and field help (F1) as in the original screen.
• TabStrips, table controls and nested subscreens.
• input field entry format checks.
• all radio buttons in a group are parameterized at once. Only one radio button can be selected at a time.
• The entire radio button group is always presented in radio button detail maintenance.
• when a pushbutton or tab title is selected, its OK code can become the new OK code.

All fields set to input-enabled in the Menu Painter are ready for input in the screen simulation, even if the transaction dynamically set them to input-disabled.

1. Enter values in the required fields. You can either enter a value directly, or call the individual field processing.

2. Enter the required OK code, e.g. (/11), with the OK code function.
3. Return to the function maintenance screen and save your entries.

If you choose a screen field and choose Field contents, an individual field processing dialog box, which contains information about any field parameters and its current value, appears.

Mark a screen field and choose Insert import parameter:

You define an export parameter to contain the value of the field that is to be read, with the Read field value function in test case screen detail maintenance.

Proceed as follows:

1. Position the cursor on the field whose value is to be read.
2. Choose .
3. Specify a parameter name. The contents of the field are passed in this parameter. If this parameter does not exist, it is automatically created as an export parameter.

The check function checks whether the runtime value of a field is the expected value, at the end of the transaction.

The check value can be a constant or a parameter. If the check value is a parameter, the test case creator must ensure that it contains the correct check value at runtime. If a non-existent parameter is specified, an import parameter is automatically created.

You define a check with the screen detail maintenance function Check field, as follows:

1. Position the cursor on the field to be checked.
2. Choose .
3. Define the check in the following dialog box:

• If you enter a value in the Field contents field, it is checked.
• If you enter a parameter name in the Parameter name field, it is checked. If this parameter does not exist, it is automatically created as an import parameter.

• if you enter a partial value in the Field contents field and add wildcard characters, a check is made against this constant.
• If you enter an incomplete parameter name containing wildcard characters in the Parameter name field, it is checked. If this parameter does not exist, it is automatically created as an import parameter.

You can change the cursor position during the test with the Cursor position function. Enter the name of the field on which the cursor is to be positioned in the test, in the dialog box. The current cursor position is proposed (field name or line/column).

Subscreens are recorded with a transaction/function module. To specify subscreen areas:

1. Display the screen simulation.
2. Choose Subscreens.

The subscreen areas are displayed by boxes.

3. Position the cursor on the top left-hand corner of the subscreen (on the period).
4. Choose Detail.
5. Enter the module pool name and the subscreen number on the next dialog screen. Confirm your entries.

The input fields are now visible in the subscreen area.

6. Go back to the screen simulation and maintain the subscreen fields, if necessary.

Alternatively to entering field values on the screen, you can maintain them in the field list. It lists the fields of the selected screen, with the option of entering new field contents. You can use variables or parameters here too.