Dynamic Selections on Selection Screens

In reports that use a logical database, "dynamic selections" allow you to select by database fields which do not exist in the logical database and are not defined in the report. These selections are passed to the database in the same manner as the static selections defined in the logical database.

Procedure from selection screen:

You can define dynamic selections if the Dynamic selections pushbutton appears on the selection screen.

In the most simple case, you press this pushbutton and then go to another selection screen. After entering your selections and pressing the pushbutton Copy, you return to the first selection screen; you can then see from the text of the key for how many dynamic selections you made entries for.

However, you may also have to choose selection criteria for the dynamic selections, i.e. one or two intermediate screens may appear before the selection screen.

You can also change the field selection from the second selection screen.

Note

Which tables support dynamic selections?

This depends on the logical database. You can use the editor command "SHOW DATABASE ldb" to get more information about this.

Note

Technical implementation in the logical database:

To activate dynamic selections for a table db_tab of the logical database ldb, the INCLUDE DBldbSEL must contain a

SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE db_tab.

statement. In the maintenance transaction for logical databases, you can create a selection view which contains the field list defined for the dynamic selections, including the field preselection. Standard SAP logical database selection views can be overwritten by the customer.

For an explanation of the logical database selections entered by the user, see SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE db_tab.

If the logical database reads via views for performance reasons, it can call the function module FREE_SELECTIONS_LDB_JOINS_INIT to ensure that the dynamic selections are also used for these read accesses (see function module documentation).