SAP ISU_DB_DBERDR_DELETE Function Module for Internal: Delete Print Document Data in DBERDR
ISU_DB_DBERDR_DELETE is a standard isu db dberdr delete 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: Delete Print Document Data in DBERDR 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 dberdr delete FM, simply by entering the name ISU_DB_DBERDR_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: E26A
Program Name: SAPLE26A
Main Program: SAPLE26A
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_DBERDR_DELETE 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_DBERDR_DELETE'"Internal: Delete Print Document Data in DBERDR.
IMPORTING
Y_TRIES = "Number of Documents to Be Deleted
Y_SUCCESS = "
TABLES
* XT_ERDR_KEY = "
EXCEPTIONS
INPUT_ERROR = 1
EXPORTING Parameters details for ISU_DB_DBERDR_DELETE
Y_TRIES - Number of Documents to Be Deleted
Data type: SY-DBCNTOptional: No
Call by Reference: No ( called with pass by value option)
Y_SUCCESS -
Data type: SY-DBCNTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_DB_DBERDR_DELETE
XT_ERDR_KEY -
Data type: ISU_ARCHIVE_ERDR_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_ERROR - No parameters specified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_DBERDR_DELETE 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_y_tries | TYPE SY-DBCNT, " | |||
| lv_input_error | TYPE SY, " | |||
| lt_xt_erdr_key | TYPE STANDARD TABLE OF ISU_ARCHIVE_ERDR_KEY, " | |||
| lv_y_success | TYPE SY-DBCNT. " |
|   CALL FUNCTION 'ISU_DB_DBERDR_DELETE' "Internal: Delete Print Document Data in DBERDR |
| IMPORTING | ||
| Y_TRIES | = lv_y_tries | |
| Y_SUCCESS | = lv_y_success | |
| TABLES | ||
| XT_ERDR_KEY | = lt_xt_erdr_key | |
| EXCEPTIONS | ||
| INPUT_ERROR = 1 | ||
| . " ISU_DB_DBERDR_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_DBERDR_DELETE
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 DBCNT FROM SY INTO @DATA(ld_y_tries). | ||||
| "SELECT single DBCNT FROM SY INTO @DATA(ld_y_success). | ||||
Search for further information about these or an SAP related objects