SAP DB02_DB4_GET_INFO Function Module for iSeries: Get info for DB02 Main Screen (Dynpro 0110)
DB02_DB4_GET_INFO is a standard db02 db4 get info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for iSeries: Get info for DB02 Main Screen (Dynpro 0110) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for db02 db4 get info FM, simply by entering the name DB02_DB4_GET_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU4_TCC
Program Name: SAPLSTU4_TCC
Main Program: SAPLSTU4_TCC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DB02_DB4_GET_INFO pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'DB02_DB4_GET_INFO'"iSeries: Get info for DB02 Main Screen (Dynpro 0110).
EXPORTING
* IM_SYSDATA = "DB6: Global Control Data for Navigation Frame
IMPORTING
DB02_DISPLAYED_INFO = "Info that is displayed on DB02 main screen
API_QWCRSSTS_RC = "Error code from API call
TABLES
* MISS_TABLES = "Tables missing in DB but expected in DD
* ADDTL_TABLES = "Tables missing in DD but existing in DB
* MISS_INDEX = "Indexes missing in DB but expected in DD
* ADDTL_INDEX = "Indexes missing in DD but existing in DB
* MISS_VIEWS = "Views missing in DB but expected in DD
* ADDTL_VIEWS = "Views missing in DD but existing in DB
EXCEPTIONS
WRONG_DBSYS = 1 API_ERROR = 10 DBSTATTDB4_EMPTY = 2 API_QWCRSSTS_ERROR = 3 DBSTAT_EMPTY_API_ERROR = 4 IMPORT_FROM_MONI_ERROR = 5 DBSTAT_EMPTY_MONI_ERROR = 6 API_ERROR_MONI_ERROR = 7 DBSTAT_EMPTY_API_ERR_MONI_ERR = 8 CONSISTENCY_CHECK_ERROR = 9
IMPORTING Parameters details for DB02_DB4_GET_INFO
IM_SYSDATA - DB6: Global Control Data for Navigation Frame
Data type: DB6NAVSYSTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DB02_DB4_GET_INFO
DB02_DISPLAYED_INFO - Info that is displayed on DB02 main screen
Data type: DB02INFDB4Optional: No
Call by Reference: No ( called with pass by value option)
API_QWCRSSTS_RC - Error code from API call
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DB02_DB4_GET_INFO
MISS_TABLES - Tables missing in DB but expected in DD
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDTL_TABLES - Tables missing in DD but existing in DB
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
MISS_INDEX - Indexes missing in DB but expected in DD
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDTL_INDEX - Indexes missing in DD but existing in DB
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
MISS_VIEWS - Views missing in DB but expected in DD
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDTL_VIEWS - Views missing in DD but existing in DB
Data type: MISSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_DBSYS - Function only supports DB2/400
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
API_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DBSTATTDB4_EMPTY - No file statistics available in DBSTATTDB4
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
API_QWCRSSTS_ERROR - Error in API call to get ASP info
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DBSTAT_EMPTY_API_ERROR - DBSTATTDB4 is empty & error in API call
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IMPORT_FROM_MONI_ERROR - Miss./addtl. tables not imported from MONI
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DBSTAT_EMPTY_MONI_ERROR - DBSTATTDB4 is empty & error in import from MONI
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
API_ERROR_MONI_ERROR - Error in API call & error in import from MONI
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DBSTAT_EMPTY_API_ERR_MONI_ERR - DBSTATTDB4 empty & API error & MONI import error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONSISTENCY_CHECK_ERROR - Error in call function 'DD_DB_CONSISTENCY_CHECK'
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DB02_DB4_GET_INFO Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_im_sysdata | TYPE DB6NAVSYST, " | |||
| lt_miss_tables | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_wrong_dbsys | TYPE MISSOBJ, " | |||
| lv_db02_displayed_info | TYPE DB02INFDB4, " | |||
| lv_api_error | TYPE DB02INFDB4, " | |||
| lt_addtl_tables | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_api_qwcrssts_rc | TYPE SY-SUBRC, " | |||
| lv_dbstattdb4_empty | TYPE SY, " | |||
| lt_miss_index | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_api_qwcrssts_error | TYPE MISSOBJ, " | |||
| lt_addtl_index | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_dbstat_empty_api_error | TYPE MISSOBJ, " | |||
| lt_miss_views | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_import_from_moni_error | TYPE MISSOBJ, " | |||
| lt_addtl_views | TYPE STANDARD TABLE OF MISSOBJ, " | |||
| lv_dbstat_empty_moni_error | TYPE MISSOBJ, " | |||
| lv_api_error_moni_error | TYPE MISSOBJ, " | |||
| lv_dbstat_empty_api_err_moni_err | TYPE MISSOBJ, " | |||
| lv_consistency_check_error | TYPE MISSOBJ. " |
|   CALL FUNCTION 'DB02_DB4_GET_INFO' "iSeries: Get info for DB02 Main Screen (Dynpro 0110) |
| EXPORTING | ||
| IM_SYSDATA | = lv_im_sysdata | |
| IMPORTING | ||
| DB02_DISPLAYED_INFO | = lv_db02_displayed_info | |
| API_QWCRSSTS_RC | = lv_api_qwcrssts_rc | |
| TABLES | ||
| MISS_TABLES | = lt_miss_tables | |
| ADDTL_TABLES | = lt_addtl_tables | |
| MISS_INDEX | = lt_miss_index | |
| ADDTL_INDEX | = lt_addtl_index | |
| MISS_VIEWS | = lt_miss_views | |
| ADDTL_VIEWS | = lt_addtl_views | |
| EXCEPTIONS | ||
| WRONG_DBSYS = 1 | ||
| API_ERROR = 10 | ||
| DBSTATTDB4_EMPTY = 2 | ||
| API_QWCRSSTS_ERROR = 3 | ||
| DBSTAT_EMPTY_API_ERROR = 4 | ||
| IMPORT_FROM_MONI_ERROR = 5 | ||
| DBSTAT_EMPTY_MONI_ERROR = 6 | ||
| API_ERROR_MONI_ERROR = 7 | ||
| DBSTAT_EMPTY_API_ERR_MONI_ERR = 8 | ||
| CONSISTENCY_CHECK_ERROR = 9 | ||
| . " DB02_DB4_GET_INFO | ||
ABAP code using 7.40 inline data declarations to call FM DB02_DB4_GET_INFO
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single SUBRC FROM SY INTO @DATA(ld_api_qwcrssts_rc). | ||||
Search for further information about these or an SAP related objects