SAP QADB_QUESTION_DOCU_ERASE Function Module for









QADB_QUESTION_DOCU_ERASE is a standard qadb question docu erase 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 question docu erase FM, simply by entering the name QADB_QUESTION_DOCU_ERASE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SQADB01
Program Name: SAPLSQADB01
Main Program: SAPLSQADB01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function QADB_QUESTION_DOCU_ERASE 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_QUESTION_DOCU_ERASE'"
EXPORTING
QUE_ID = "Unique question ID
* ADDONID = ' ' "Industry

IMPORTING
PROCESSING_STATUS = "Processing degree of a function

TABLES
ERRORS = "Error structure of repository interface

EXCEPTIONS
ERROR_OCCURED = 1
.



IMPORTING Parameters details for QADB_QUESTION_DOCU_ERASE

QUE_ID - Unique question ID

Data type: SQADB01-QUEID
Optional: No
Call by Reference: Yes

ADDONID - Industry

Data type: SQABRANCH-BRANCH
Default: SPACE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for QADB_QUESTION_DOCU_ERASE

PROCESSING_STATUS - Processing degree of a function

Data type: RPYGSGF-PROC_STAT
Optional: No
Call by Reference: Yes

TABLES Parameters details for QADB_QUESTION_DOCU_ERASE

ERRORS - Error structure of repository interface

Data type: RPYGSER
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for QADB_QUESTION_DOCU_ERASE 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_que_id  TYPE SQADB01-QUEID, "   
lv_error_occured  TYPE SQADB01, "   
lv_processing_status  TYPE RPYGSGF-PROC_STAT, "   
lv_addonid  TYPE SQABRANCH-BRANCH. "   SPACE

  CALL FUNCTION 'QADB_QUESTION_DOCU_ERASE'  "
    EXPORTING
         QUE_ID = lv_que_id
         ADDONID = lv_addonid
    IMPORTING
         PROCESSING_STATUS = lv_processing_status
    TABLES
         ERRORS = lt_errors
    EXCEPTIONS
        ERROR_OCCURED = 1
. " QADB_QUESTION_DOCU_ERASE




ABAP code using 7.40 inline data declarations to call FM QADB_QUESTION_DOCU_ERASE

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 QUEID FROM SQADB01 INTO @DATA(ld_que_id).
 
 
"SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status).
 
"SELECT single BRANCH FROM SQABRANCH INTO @DATA(ld_addonid).
DATA(ld_addonid) = ' '.
 


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!