SAP BDS_BUSINESSDOCUMENT_DEQUEUE Function Module for









BDS_BUSINESSDOCUMENT_DEQUEUE is a standard bds businessdocument dequeue 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 bds businessdocument dequeue FM, simply by entering the name BDS_BUSINESSDOCUMENT_DEQUEUE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDS_BAPI
Program Name: SAPLBDS_BAPI
Main Program: SAPLBDS_BAPI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BDS_BUSINESSDOCUMENT_DEQUEUE 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 'BDS_BUSINESSDOCUMENT_DEQUEUE'"
EXPORTING
* LOGICAL_SYSTEM = "
CLASSNAME = "
CLASSTYPE = "
* CLIENT = SY-MANDT "
* OBJECT_KEY = "
DOC_ID = "
DOC_VER_NO = "
DOC_VAR_ID = "

EXCEPTIONS
NOTHING_FOUND = 1 PARAMETER_ERROR = 2 NOT_ALLOWED = 3 ERROR_KPRO = 4 INTERNAL_ERROR = 5 NOT_AUTHORIZED = 6
.



IMPORTING Parameters details for BDS_BUSINESSDOCUMENT_DEQUEUE

LOGICAL_SYSTEM -

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

CLASSNAME -

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

CLASSTYPE -

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

CLIENT -

Data type: BAPIBDS01-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_KEY -

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

DOC_ID -

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

DOC_VER_NO -

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

DOC_VAR_ID -

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

EXCEPTIONS details

NOTHING_FOUND -

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

PARAMETER_ERROR -

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

NOT_ALLOWED -

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

ERROR_KPRO -

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

INTERNAL_ERROR -

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

NOT_AUTHORIZED -

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

Copy and paste ABAP code example for BDS_BUSINESSDOCUMENT_DEQUEUE 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_nothing_found  TYPE STRING, "   
lv_logical_system  TYPE BAPIBDS01-LOG_SYSTEM, "   
lv_classname  TYPE BAPIBDS01-CLASSNAME, "   
lv_parameter_error  TYPE BAPIBDS01, "   
lv_classtype  TYPE BAPIBDS01-CLASSTYPE, "   
lv_not_allowed  TYPE BAPIBDS01, "   
lv_client  TYPE BAPIBDS01-CLIENT, "   SY-MANDT
lv_error_kpro  TYPE BAPIBDS01, "   
lv_object_key  TYPE BAPIBDS01-OBJKEY, "   
lv_internal_error  TYPE BAPIBDS01, "   
lv_doc_id  TYPE BAPIBDS01-DOC_ID, "   
lv_not_authorized  TYPE BAPIBDS01, "   
lv_doc_ver_no  TYPE BAPIBDS01-DOC_VER_NO, "   
lv_doc_var_id  TYPE BAPIBDS01-DOC_VAR_ID. "   

  CALL FUNCTION 'BDS_BUSINESSDOCUMENT_DEQUEUE'  "
    EXPORTING
         LOGICAL_SYSTEM = lv_logical_system
         CLASSNAME = lv_classname
         CLASSTYPE = lv_classtype
         CLIENT = lv_client
         OBJECT_KEY = lv_object_key
         DOC_ID = lv_doc_id
         DOC_VER_NO = lv_doc_ver_no
         DOC_VAR_ID = lv_doc_var_id
    EXCEPTIONS
        NOTHING_FOUND = 1
        PARAMETER_ERROR = 2
        NOT_ALLOWED = 3
        ERROR_KPRO = 4
        INTERNAL_ERROR = 5
        NOT_AUTHORIZED = 6
. " BDS_BUSINESSDOCUMENT_DEQUEUE




ABAP code using 7.40 inline data declarations to call FM BDS_BUSINESSDOCUMENT_DEQUEUE

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 LOG_SYSTEM FROM BAPIBDS01 INTO @DATA(ld_logical_system).
 
"SELECT single CLASSNAME FROM BAPIBDS01 INTO @DATA(ld_classname).
 
 
"SELECT single CLASSTYPE FROM BAPIBDS01 INTO @DATA(ld_classtype).
 
 
"SELECT single CLIENT FROM BAPIBDS01 INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
"SELECT single OBJKEY FROM BAPIBDS01 INTO @DATA(ld_object_key).
 
 
"SELECT single DOC_ID FROM BAPIBDS01 INTO @DATA(ld_doc_id).
 
 
"SELECT single DOC_VER_NO FROM BAPIBDS01 INTO @DATA(ld_doc_ver_no).
 
"SELECT single DOC_VAR_ID FROM BAPIBDS01 INTO @DATA(ld_doc_var_id).
 


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!