Attaching to Check Tables 

If a field has a check table, the set of all possible entries to the field is defined by the contents of this check table (see Foreign Keys).

The contents of the key fields of the check table are therefore offered automatically in the input help. If a text table is defined for the check table, the contents of the first text field of this text table is also displayed in the user’s logon language (see Text Tables). This input help coming from the check table can be further edited by assigning a search help to the check table.

If a search help is attached to a table, it should display the data contained in this check table. In this case, the check table itself or a view on this check table should be defined as the selection method of the search help.

When a search help is allocated to a table, there must be an allocation between the key fields of the table and the parameters of the interface of the search help.

The field CONNID (number of the flight connection) of table SFLIGHT (flights) is checked against table SPFLI (flight schedule). The elementary search help H_SPFLI (search for flights by cities of departure and arrival) is allocated to table SPFLI. This search help is available for the field CONNID when data is entered in table SFLIGHT.

Search help H_SPFLI does not contain a client field since for the input help the selection is always made in the logon client of the user.

There is a value transport (see Value Transport for Input Helps) between the field contents of the input template and the parameters of the search help both when the input help is called in an input template and when an entry of the hit list is selected.

The search help attachment is part of the definition of the table/structure to which the search help is attached. You can find out how to attach a search help to a table in Creating Fields of Tables.