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

Function BUP_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 'BUP_DEQUEUE'".
EXPORTING
I_PARTNER = "
I_AKTYP = "
I_AKTDB = "
I_XSAVE = "
IMPORTING Parameters details for BUP_DEQUEUE
I_PARTNER -
Data type: BUT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
I_AKTYP -
Data type: TBZ0K-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_AKTDB -
Data type: TBZ0K-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_XSAVE -
Data type: BUS000FLDS-XSAVEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUP_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_i_partner | TYPE BUT000-PARTNER, " | |||
| lv_i_aktyp | TYPE TBZ0K-AKTYP, " | |||
| lv_i_aktdb | TYPE TBZ0K-AKTYP, " | |||
| lv_i_xsave | TYPE BUS000FLDS-XSAVE. " |
|   CALL FUNCTION 'BUP_DEQUEUE' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_AKTYP | = lv_i_aktyp | |
| I_AKTDB | = lv_i_aktdb | |
| I_XSAVE | = lv_i_xsave | |
| . " BUP_DEQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM BUP_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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner). | ||||
| "SELECT single AKTYP FROM TBZ0K INTO @DATA(ld_i_aktyp). | ||||
| "SELECT single AKTYP FROM TBZ0K INTO @DATA(ld_i_aktdb). | ||||
| "SELECT single XSAVE FROM BUS000FLDS INTO @DATA(ld_i_xsave). | ||||
Search for further information about these or an SAP related objects