SAP SQADB02_READ_QUESTION Function Module for









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

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



Function SQADB02_READ_QUESTION 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 'SQADB02_READ_QUESTION'"
EXPORTING
I_OK_CODE = "
* I_ADDONID = ' ' "Industry version

IMPORTING
E_MODE = "
E_SQADB01 = "

CHANGING
P_QUEID = "

TABLES
E_T_DOCU = "
P_T_INV_CHOICE = "

EXCEPTIONS
NOTFOUND = 1 EXISTS = 2 CANCLED = 3 ERROR = 4 DELETED = 5 ENQUEUE = 6 NO_QUEID = 7
.



IMPORTING Parameters details for SQADB02_READ_QUESTION

I_OK_CODE -

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

I_ADDONID - Industry version

Data type: SQADB01T-ADDON
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SQADB02_READ_QUESTION

E_MODE -

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

E_SQADB01 -

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

CHANGING Parameters details for SQADB02_READ_QUESTION

P_QUEID -

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

TABLES Parameters details for SQADB02_READ_QUESTION

E_T_DOCU -

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

P_T_INV_CHOICE -

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

EXCEPTIONS details

NOTFOUND -

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

EXISTS -

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

CANCLED -

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

ERROR -

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

DELETED -

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

ENQUEUE -

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

NO_QUEID -

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

Copy and paste ABAP code example for SQADB02_READ_QUESTION 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_e_mode  TYPE STRING, "   
lv_p_queid  TYPE SQADB01-QUEID, "   
lt_e_t_docu  TYPE STANDARD TABLE OF TLINE, "   
lv_notfound  TYPE TLINE, "   
lv_i_ok_code  TYPE SY-UCOMM, "   
lv_exists  TYPE SY, "   
lv_e_sqadb01  TYPE SQADB01_S, "   
lv_i_addonid  TYPE SQADB01T-ADDON, "   SPACE
lt_p_t_inv_choice  TYPE STANDARD TABLE OF SQA02CH_T, "   
lv_cancled  TYPE SQA02CH_T, "   
lv_error  TYPE SQA02CH_T, "   
lv_deleted  TYPE SQA02CH_T, "   
lv_enqueue  TYPE SQA02CH_T, "   
lv_no_queid  TYPE SQA02CH_T. "   

  CALL FUNCTION 'SQADB02_READ_QUESTION'  "
    EXPORTING
         I_OK_CODE = lv_i_ok_code
         I_ADDONID = lv_i_addonid
    IMPORTING
         E_MODE = lv_e_mode
         E_SQADB01 = lv_e_sqadb01
    CHANGING
         P_QUEID = lv_p_queid
    TABLES
         E_T_DOCU = lt_e_t_docu
         P_T_INV_CHOICE = lt_p_t_inv_choice
    EXCEPTIONS
        NOTFOUND = 1
        EXISTS = 2
        CANCLED = 3
        ERROR = 4
        DELETED = 5
        ENQUEUE = 6
        NO_QUEID = 7
. " SQADB02_READ_QUESTION




ABAP code using 7.40 inline data declarations to call FM SQADB02_READ_QUESTION

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_p_queid).
 
 
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_i_ok_code).
 
 
 
"SELECT single ADDON FROM SQADB01T INTO @DATA(ld_i_addonid).
DATA(ld_i_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!