SAP QADB_DOCU_DELETE Function Module for
QADB_DOCU_DELETE is a standard qadb docu delete 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 qadb docu delete FM, simply by entering the name QADB_DOCU_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SQADB00
Program Name: SAPLSQADB00
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QADB_DOCU_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 'QADB_DOCU_DELETE'".
EXPORTING
DOCNAME = "Documentation Object
IMPORTING
ERROR_OCCURED = "General Flag
PROCESSING_STATUS = "Processing degree of a function
TABLES
ERRORS = "Error structure of repository interface
IMPORTING Parameters details for QADB_DOCU_DELETE
DOCNAME - Documentation Object
Data type: DOKHL-OBJECTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for QADB_DOCU_DELETE
ERROR_OCCURED - General Flag
Data type: RPYGSGF-ERR_EXISTOptional: No
Call by Reference: Yes
PROCESSING_STATUS - Processing degree of a function
Data type: RPYGSGF-PROC_STATOptional: No
Call by Reference: Yes
TABLES Parameters details for QADB_DOCU_DELETE
ERRORS - Error structure of repository interface
Data type: RPYGSEROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QADB_DOCU_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: | ||||
| lt_errors | TYPE STANDARD TABLE OF RPYGSER, " | |||
| lv_docname | TYPE DOKHL-OBJECT, " | |||
| lv_error_occured | TYPE RPYGSGF-ERR_EXIST, " | |||
| lv_processing_status | TYPE RPYGSGF-PROC_STAT. " |
|   CALL FUNCTION 'QADB_DOCU_DELETE' " |
| EXPORTING | ||
| DOCNAME | = lv_docname | |
| IMPORTING | ||
| ERROR_OCCURED | = lv_error_occured | |
| PROCESSING_STATUS | = lv_processing_status | |
| TABLES | ||
| ERRORS | = lt_errors | |
| . " QADB_DOCU_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM QADB_DOCU_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 OBJECT FROM DOKHL INTO @DATA(ld_docname). | ||||
| "SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured). | ||||
| "SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status). | ||||
Search for further information about these or an SAP related objects