SAP SDOK_QUE_CLASSES_GET Function Module for









SDOK_QUE_CLASSES_GET is a standard sdok que classes get 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 sdok que classes get FM, simply by entering the name SDOK_QUE_CLASSES_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function SDOK_QUE_CLASSES_GET 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 'SDOK_QUE_CLASSES_GET'"
EXPORTING
* IV_LANGUAGE = SY-LANGU "

TABLES
* TT_CLASSES = "
* TT_CLASSES_T = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for SDOK_QUE_CLASSES_GET

IV_LANGUAGE -

Data type: SY-BATCH
Default: SY-LANGU
Optional: No
Call by Reference: Yes

TABLES Parameters details for SDOK_QUE_CLASSES_GET

TT_CLASSES -

Data type: SDOK_Q_CLASSES
Optional: Yes
Call by Reference: Yes

TT_CLASSES_T -

Data type: SDOK_Q_CLASSES_T
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SDOK_QUE_CLASSES_GET 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_not_found  TYPE STRING, "   
lt_tt_classes  TYPE STANDARD TABLE OF SDOK_Q_CLASSES, "   
lv_iv_language  TYPE SY-BATCH, "   SY-LANGU
lt_tt_classes_t  TYPE STANDARD TABLE OF SDOK_Q_CLASSES_T. "   

  CALL FUNCTION 'SDOK_QUE_CLASSES_GET'  "
    EXPORTING
         IV_LANGUAGE = lv_iv_language
    TABLES
         TT_CLASSES = lt_tt_classes
         TT_CLASSES_T = lt_tt_classes_t
    EXCEPTIONS
        NOT_FOUND = 1
. " SDOK_QUE_CLASSES_GET




ABAP code using 7.40 inline data declarations to call FM SDOK_QUE_CLASSES_GET

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 BATCH FROM SY INTO @DATA(ld_iv_language).
DATA(ld_iv_language) = SY-LANGU.
 
 


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!