Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

ABAPPARAMETERS_LDB - PARAMETERS LDB

ABAPPARAMETERS_LDB - PARAMETERS LDB

BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

PARAMETERS, ldb_options

Short Reference



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

Additions

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

2. ... HELP-REQUEST

3. ... VALUE-REQUEST

4. ... AS SEARCH PATTERN

Effect

These additions for the statement PARAMETERS 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 helps can be called and a special parameter can be defined for evaluating the search help linked with the logical database.

Note

If logical databases are no longer created, it is no longer necessary to use these additions of the statement PARAMETERS.

Addition 1

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

Effect

With this addition, the parameter must be assigned to a node of the structure of the logical database. If a node has type T, the addition TABLE can be used instead of NODE. For a description of the node types, see the statement NODES.

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

Addition 2

... HELP-REQUEST

Effect

This addition specifies that the subroutine para_hlp (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. If the subroutine is not available, the addition is ignored.

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

Note

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

Addition 3

... VALUE-REQUEST

Effect

This addition specifies that the subroutine para_val (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 ignored.

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

Note

In the called subroutine, 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 raised and there is no automatic pass by value between the selection screen and the program. Suitable function modules must be used for this, as with general dynpros. The parameter that is changed in the subroutine is transported to the selection screen.

Addition 4

... AS SEARCH PATTERN

Effect

This addition enables a search help to be evaluated in the database program. To do this, the logical database must be assigned a search help in transaction SE36. Except for the mandatory addition FOR TABLE$|NODE, the addition AS SEARCH PATTERN can only be combined with the addition MODIF ID. In particular, a type cannot be defined with the addition TYPE.

The data type of the parameter is the internal table syldb_sp from the type pool SYLDB. This table has three columns: hotkey (search help ID), string (search string), and trange ( deep data type for complex search helps). 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 helps.

After the selection screen has been processed, the list of values created by the search help is available in the internal table ldb_SP 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 subroutine PUT_root, where the event GET root is raised by the statement PUT root.

Note

See also Logical Databases - Links with Search Helps.






General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 8682 Date: 20230206 Time: 110129     sap01-206 ( 147 ms )