SAP DB_READ_DYNPRO Function Module for
DB_READ_DYNPRO is a standard db read dynpro SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 db read dynpro FM, simply by entering the name DB_READ_DYNPRO into the relevant SAP transaction such as SE37 or SE38.
Function Group: SYDB
Program Name: SAPLSYDB
Main Program: SAPLSYDB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB_READ_DYNPRO 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 'DB_READ_DYNPRO'".
EXPORTING
PROG_NAME = "
DYNPRO_NR = "
EXCEPTIONS
DYNPRO_NOT_EXISTS = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for DB_READ_DYNPRO
PROG_NAME -
Data type: D020S-PROGOptional: No
Call by Reference: Yes
DYNPRO_NR -
Data type: D020S-DNUMOptional: No
Call by Reference: Yes
EXCEPTIONS details
DYNPRO_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DB_READ_DYNPRO 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_prog_name | TYPE D020S-PROG, " | |||
| lv_dynpro_not_exists | TYPE D020S, " | |||
| lv_dynpro_nr | TYPE D020S-DNUM, " | |||
| lv_internal_error | TYPE D020S. " |
|   CALL FUNCTION 'DB_READ_DYNPRO' " |
| EXPORTING | ||
| PROG_NAME | = lv_prog_name | |
| DYNPRO_NR | = lv_dynpro_nr | |
| EXCEPTIONS | ||
| DYNPRO_NOT_EXISTS = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " DB_READ_DYNPRO | ||
ABAP code using 7.40 inline data declarations to call FM DB_READ_DYNPRO
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 PROG FROM D020S INTO @DATA(ld_prog_name). | ||||
| "SELECT single DNUM FROM D020S INTO @DATA(ld_dynpro_nr). | ||||
Search for further information about these or an SAP related objects