SAP ISU_DB_ERDU_UPDATE Function Module for INTERNAL: Update ERDR
ISU_DB_ERDU_UPDATE is a standard isu db erdu update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Update ERDR 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 isu db erdu update FM, simply by entering the name ISU_DB_ERDU_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ERDK
Program Name: SAPLERDK
Main Program: SAPLERDK
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_ERDU_UPDATE 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 'ISU_DB_ERDU_UPDATE'"INTERNAL: Update ERDR.
EXPORTING
X_UPD_MODE = "Update Mode
TABLES
T_ERDU = "
IMPORTING Parameters details for ISU_DB_ERDU_UPDATE
X_UPD_MODE - Update Mode
Data type: REGEN-UPD_MODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_DB_ERDU_UPDATE
T_ERDU -
Data type: ERDUOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_ERDU_UPDATE 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: | ||||
| lt_t_erdu | TYPE STANDARD TABLE OF ERDU, " | |||
| lv_x_upd_mode | TYPE REGEN-UPD_MODE. " |
|   CALL FUNCTION 'ISU_DB_ERDU_UPDATE' "INTERNAL: Update ERDR |
| EXPORTING | ||
| X_UPD_MODE | = lv_x_upd_mode | |
| TABLES | ||
| T_ERDU | = lt_t_erdu | |
| . " ISU_DB_ERDU_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_ERDU_UPDATE
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 UPD_MODE FROM REGEN INTO @DATA(ld_x_upd_mode). | ||||
Search for further information about these or an SAP related objects