SAP NEWS-30-LDB



Get Example source ABAP code based on a different SAP table
  



Logical Databases and Selection Screens in ABAP Release 3.0
ITOC

ABAP_MODIFICATION_NN Checkbox Parameters

PARAMETERS now has an addition called AS CHECKBOX which can be used to display a parameter on the selection screen as a checkbox.

ABAP_MODIFICATION_NN Matchcode Selection with Logical Databases

The addition AS MATCHCODE STRUCTURE of PARAMETERS makes it possible to use matchcode selection for a logical database. The standard selection screen contains a box with input fields for matchcode ID and search string. In the database program, selected records can be processed in the subroutine PUT_xxx_MATCHCODE. Matchcode selections are a particularly good way of improving performance, since they can be used to restrict the amount of data selected significantly.

ABAP_MODIFICATION_NN SUBMIT rep WITH SELECTION-TABLE rspar.

The addition WITH SELECTION-TABLE rspar makes it possible to specify values passed by WITH clause to the parameters or selection criteria of a report in an internal table. Here, the table rspar has the structure of RSPARAMS. The function module RS_REFRESH_FROM_SELECT_OPTIONS can be used to fill the table with the content of the current parameters or selection criteria (this FM replaces the keyword REFRESH respar FROM SELECT-OPTIONS). For further information, see the documentation on SUBMIT.

ABAP_MODIFICATION_NN Self-Programmed F1 and F4 on Selection Screens

Self-programmed input help (F4) and field help (F1) is now available for both database-specific and report-specific parameters and selection criteria. For database-specific objects, this is done using an addition (VALUE-REQUEST ... or HELP-REQUEST ...) with PARAMETERS and SELECT-OPTIONS. For report-specific objects, the event to be processed is specified directly at F1 or F4 ( AT SELECTION-SCREEN ON VALUE-REQUEST FOR ... or AT SELECTION-SCREEN ON HELP-REQUEST FOR ...).

ABAP_MODIFICATION_NN Date Calculations in Variants

In addition to the variables available in table TVARV for parameters or selection criteria in variants (for retrieving values from table TVARV at runtime), it is now possible to calculate dates or periods for parameters/selection criteria of the type date at runtime. Examples include current date, last day of previous month, and first quarter of current year.

ABAP_MODIFICATION_NN SUBMIT: Runtime Information from Function Module

The function module RS_SUBMIT_INFO returns information about the current report execution process in the structure RSSUBINFO. It is specifically intended for use during the processing of selection screens. It indicates, for example, whether the selection screen is processed when the report is executed, when variants are defined, or when scheduling a background job. This is important, for example, if the user uses his or her own GUI status on the selection screen.

ABAP_MODIFICATION_NN No More Blank Selection Screens

Previously, selection screens were generated and processed even if no parameters or selection criteria were defined. To reduce the number of selection screens, this is no longer the case. Events previously triggered by the selection screen (AT SELECTION-SCREEN, AT SELECTION-SCREEN OUTPUT) are not processed.

ABAP_MODIFICATION_NN New OK Code Field SSCRFIELDS-UCOMM on Selection Screens

The previous OK code field SY-UCOMM had the drawback of being destroyed by every CALL SCREEN. For this reason, it has been replaced by the field SSCRFIELDS-UCOMM from ABAP Dictionary. Unlike SY-UCOMM, the structure SSCRFIELDS must be declared using TABLES when reading or manipulating SSCRFIELDS-UCOMM.
Only the procedure for setting SY-UCOMM in the program has changed; SY-UCOMM must now be set instead. Setting SY-UCOMM in the program, however, no longer meets the intended purpose, and SSCRFIELDS-UCOMM now needs to be set instead.

ABAP_MODIFICATION_NN Integration of the Data Model

In transaction SE36 (Logical Databases), the set of views that refer to a logical database table can be displayed by selecting Edit -> Data Model -> Views and Entities. The relevant entities are displayed from the Enterprise Data Model ( <(>EDM<)>). After choosing the views, Data Model -> Graphics can be selected to display the convex wrapper of the relevant entities in the <(>EDM<)>.

ABAP_MODIFICATION_NN Function Modules: User's Own GUI Status on Selection Screen

Function modules RS_SET_SELSCREEN_STATUS and RS_EXTERNAL_SELSCREEN_STATUS.
These function modules make it possible to set a separate status for the selection screen or to deactivate function codes from the standard status (for example, if the 'Print' function for the report is not required).
While the function module RS_SET_SELSCREEN_STATUS requires the status in question to belong to the user interface for the report, the function module RS_EXTERNAL_SELSCREEN_STATUS makes it possible to set a status that has been defined externally in a function pool.
When a separate status is set, it is best to first get information about the current situation using the function module RS_SUBMIT_INFO (see point 6). In this way, the 'Execute' key is not provided instead of the 'Save' key when defining variants.

ABAP_MODIFICATION_NN PARAMETERS as Radio Buttons

Addition RADIOBUTTON GROUP group with PARAMETERS.
By using this addition, PARAMETERS can be combined together in radio button groups on the selection screen. For further information, see PARAMETERS.

ABAP_MODIFICATION_NN Size of Selection Screens Increased to 200 Lines

Selection screens can now be up to 200 lines long. Since the scroll bar can be used to scroll within a screen, the continuation screens 1001, 1002 ... are no longer necessary.
Benefits: Since all SELECT-OPTIONS and PARAMETERS are on one screen, it is no longer necessary to check carefully that the incorrect field is actually on the current screen when handling errors. Also, the addition 'OBLIGATORY' now applies to all SELECT-OPTIONS or PARAMETERS that were previously on a subsequent screen. This reduces the total number of generated selection screens
Necessary actions: In theory, none. However, new pages previously forced by the SELECTION-SCREEN NEW-PAGE statement may have to be replaced by something else, such as a block (see also points 13 and 14).

ABAP_MODIFICATION_NN SELECTION-SCREEN NEW-PAGE is No Longer Used.

Since continuation screens are no longer used (see point 12), the keyword SELECTION-SCREEN NEW-PAGE is no longer required, but is retained for syntax reasons. However, it now starts a new line instead of a new page.

ABAP_MODIFICATION_NN Selection Screen Versions Instead of Template Screens

The option to define non-standard selection screens by specifying the number of a model screen (belonging to the database access program SAPDBxyz) in the report properties no longer exists. This has been replaced by selection screen versions. Like model screens, these have a three-character name that is specified on the report properties screen. By pressing F4 here, it is possible to get a list of all the selection screen versions for the underlying logical database.