PARAMETERS - ldb_options

Syntax

... FOR {TABLE|NODE} node
    [HELP-REQUEST]
    [VALUE-REQUEST]
    [AS SEARCH PATTERN] ... .

Extras:

1. ... FOR {TABLE|NODE} node

2. ... HELP-REQUEST

3. ... VALUE-REQUEST

4. ... AS SEARCH PATTERN

Effect

These additions are only possible in the selection include of a logical database. They must be used to assign a node in the logical database to the parameter. Subroutines for self-defined help can be called and a special parameter can be defined for evaluating the search help linked with the logical database.

Addition 1

... FOR {TABLE|NODE} node

Effect

With this addition, the parameter has to be assigned to a node of the structure of the logical database. If a node is of type T, then instead of NODE, the table addition of equal status can be used. You can find a description of the node types with the NODES statement.

For the generation of the selection screen of an executable program, which is linked with the logical database, input fields are created for those parameters for which an interface work area for the assigned node or a node beneath it in the hierarchy is declared with NODES or TABLES in the executable program. When using the LDB_PROCESS function module, the assigned node node must be requested so that the parameter appears on the selection screen.

Addition 2

... HELP-REQUEST

Effect

This addition has the effect that the para_HLP subroutine (para is the name of the parameter) of the database program of the logical database is called if the user selects the F1 field help for a screen element of the parameter on the selection screen. The addition is ignored if the subroutine is not available.

If the parameter is defined in the ABAP Dictionary with a reference to a data type, the field help that is defined there is not displayed.

Note

In the subroutine that is called, the field help display can be programmed or called using suitable function modules, such as HELP_OBJECT_SHOW. If the input help is selected, no other selection screen events can be triggered and there is no automatic pass by value between the selection screen and the program.

Addition 3

... VALUE-REQUEST

Effect

This addition has the effect that the para_VAL subroutine (para is the name of the parameter) of the database program of the logical database is called if the user selects the F4 input help on a screen element of the parameter on the selection screen. The input help key is displayed for the input field of the parameter on the selection screen. If the subroutine is not available, the addition is ingored.

If the parameter is defined in the ABAP Dictionary with a reference to a data type, the input help that is defined there is not displayed.

Note

In the subroutine that is called, the input help display can be programmed or called using suitable function modules such as F4IF_INT_TABLE_VALUE_REQUEST. If the input help is selected, no other selection screen events are called and there is no automatic pass by value between the selection screen and the program. As for general screens, you have to use suitable function modules for this. The parameter that is changed in the subroutine is transported to the selection screen.

Addition 4

... AS SEARCH PATTERN

Effect

This addition enables the evaluation of a search help in the database program. For this, the logical database has to be assigned to a search help in TransactionSE36. Except for the mandatory addition FOR TABLE|NODE, the AS SEARCH PATTERN addition can only be combined with the MODIF ID addition. In particular, you cannot define a type with the TYPE addition.

The data type of the parameter is the SYLDB_SP internal table from the SYLDB type group. This table has three columns: HOTKEY (search help ID), STRING (search string) and TRANGE ( deep data type for complex search help). The selection screen displays an outlined block with the title "Selection using search help", which contains input fields for the search help ID and the search string as well as a pushbutton for complex search help.

After the selection screen processing, the list of values provided by the search help is available in the ldb_SP internal table in the database program. Instead of the PUT_root subroutine, the PUT_ldb_SP subroutine is called. Here, " ldb" is the name of the logical database and "root" is the name of the root node. This subroutine can read the actual data using the list of values in ldb_SP and can then call the PUT_root subroutine, where the GET root event is triggered with the PUT root statement.