Maintain screens 

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:

Field value assignment via screens

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.

To ensure that you only enter values in the input fields, you should put values in all fields when recording the transaction/function module.
  1. Enter values in the required fields. You can either enter a value directly, or call the individual field processing.

Space characters (to delete field default values) can be passed by entering two apostrophes (' ' or '', i.e. with or without space characters between the apostrophes).
  1. Enter the required OK code, e.g. (/11), with the OK code function.
  2. Return to the function maintenance screen and save your entries.

Individual field processing

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.

Parameterization

Mark a screen field and choose Insert import parameter:

Read field values

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 parameter is filled at the end of the transaction, so you cannot use it in the same transaction as an import value for a subsequent screen.

Define field check

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:

You can similarly define a check on the last system message: See „ Extended system message checks ".

Field checks with patterns

Screen field checks are defined in the CATT function TCD. The check value can be a constant or the current contents of a parameter.
From 4.6C generic checks are also possible. If a check value or the current check parameter contains an ' * ' at the end of the strings, a longer field would still give a positive check result.

The check is made according to the ABAP condition CP (contains pattern) rules, so it is not case-sensitive.

All wildcard characters, e.g. ' * ', ' + ', ' # ' can be used with the same meaning as in ABAP conditions with the comparison operator CP between strings. See CP (Contains Pattern) in Comparing strings

To define a check with ’Contains Pattern‘ similarly to a field check:

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

You check against the Message text field of the message screen SAPMSCEM 0001: The entry USER* in transaction FD01 Create user has a positive check result for both the messages " User created" and "User already exists".

Cursor position

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).

Function codes

Use the function keys or the transaction Menu Painter function codes. Get system data tells you how to find these.

Subscreen

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

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

    3. 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.

    6. The input fields are now visible in the subscreen area.

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

You can get the name and screen number of the subscreen by calling the transaction, positioning the cursor on a subscreen field, and choosing System ® Status.

Field value input via field list

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.

In exceptional cases, you can also use internal variables as field names (see ). Process dynamic screens and field names).

Before you can edit the fields of a subscreen in the field list, you must define the subscreen. Proceed as described in Subscreen (above).

You can find the assignment of field names to the screen fields by positioning the cursor on the associated screen field in the transaction, and pressing the help key. A field help window appears. You can display the table name and the field name as well as the program name and the screen number, with the Technical Info function.