SAP ISU_DB_DELETE_PRINT_DOCUMENT Function Module for Internal: Delete Entire Print Document









ISU_DB_DELETE_PRINT_DOCUMENT is a standard isu db delete print document 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 Entire Print Document 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 delete print document FM, simply by entering the name ISU_DB_DELETE_PRINT_DOCUMENT 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_DELETE_PRINT_DOCUMENT 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_DELETE_PRINT_DOCUMENT'"Internal: Delete Entire Print Document
  EXPORTING
*  X_DELETE_ERCHC = '' "

CHANGING
*  Y_ERDK_COUNT =  "
*  Y_ERDB_COUNT =  "
*  Y_ERDO_COUNT =  "
*  Y_ERDZ_COUNT =  "
*  Y_ERDR_COUNT =  "
*  Y_ERDU_COUNT =  "
*  Y_ERDL_COUNT =  "
*  Y_ERDLB_COUNT =  "

TABLES
   X_ERDK_KEY =  "

EXCEPTIONS
   INPUT_ERROR = 1    READ_ERROR = 2    UPDATE_ERROR = 3
.



IMPORTING Parameters details for ISU_DB_DELETE_PRINT_DOCUMENT

X_DELETE_ERCHC -

Data type: KENNZX
Default: ''
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ISU_DB_DELETE_PRINT_DOCUMENT

Y_ERDK_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDB_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDO_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDZ_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDR_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDU_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDL_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

Y_ERDLB_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISU_DB_DELETE_PRINT_DOCUMENT

X_ERDK_KEY -

Data type: ISU_ARCHIVE_ERDK_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

UPDATE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_DB_DELETE_PRINT_DOCUMENT 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_x_erdk_key  TYPE STANDARD TABLE OF ISU_ARCHIVE_ERDK_KEY, "   
lv_input_error  TYPE ISU_ARCHIVE_ERDK_KEY, "   
lv_y_erdk_count  TYPE I, "   
lv_x_delete_erchc  TYPE KENNZX, "   ''
lv_read_error  TYPE KENNZX, "   
lv_y_erdb_count  TYPE I, "   
lv_update_error  TYPE I, "   
lv_y_erdo_count  TYPE I, "   
lv_y_erdz_count  TYPE I, "   
lv_y_erdr_count  TYPE I, "   
lv_y_erdu_count  TYPE I, "   
lv_y_erdl_count  TYPE I, "   
lv_y_erdlb_count  TYPE I. "   

  CALL FUNCTION 'ISU_DB_DELETE_PRINT_DOCUMENT'  "Internal: Delete Entire Print Document
    EXPORTING
         X_DELETE_ERCHC = lv_x_delete_erchc
    CHANGING
         Y_ERDK_COUNT = lv_y_erdk_count
         Y_ERDB_COUNT = lv_y_erdb_count
         Y_ERDO_COUNT = lv_y_erdo_count
         Y_ERDZ_COUNT = lv_y_erdz_count
         Y_ERDR_COUNT = lv_y_erdr_count
         Y_ERDU_COUNT = lv_y_erdu_count
         Y_ERDL_COUNT = lv_y_erdl_count
         Y_ERDLB_COUNT = lv_y_erdlb_count
    TABLES
         X_ERDK_KEY = lt_x_erdk_key
    EXCEPTIONS
        INPUT_ERROR = 1
        READ_ERROR = 2
        UPDATE_ERROR = 3
. " ISU_DB_DELETE_PRINT_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM ISU_DB_DELETE_PRINT_DOCUMENT

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.

 
 
 
DATA(ld_x_delete_erchc) = ''.
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!