SAP DEQUEUE_E_BGRFC_O_DEST_R Function Module for Release lock on object E_BGRFC_O_DEST_R









DEQUEUE_E_BGRFC_O_DEST_R is a standard dequeue e bgrfc o dest r SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release lock on object E_BGRFC_O_DEST_R processing and below is the pattern details for this FM, 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 dequeue e bgrfc o dest r FM, simply by entering the name DEQUEUE_E_BGRFC_O_DEST_R into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/SEN0012
Program Name: /1BCDWBEN/SAPLSEN0012
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DEQUEUE_E_BGRFC_O_DEST_R 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 'DEQUEUE_E_BGRFC_O_DEST_R'"Release lock on object E_BGRFC_O_DEST_R
EXPORTING
* MODE_BGRFC_O_DEST_REGISTRATION = 'E' "Lock mode for table BGRFC_O_DEST_REGISTRATION
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* DESTINATION_NAME = "01th enqueue argument
* SCHEDULER_NR = "02th enqueue argument
* CONTEXT_ID = "03th enqueue argument
* DP_SERVER_NAME = "04th enqueue argument
* X_DESTINATION_NAME = ' ' "Fill argument 01 with initial value?
* X_SCHEDULER_NR = ' ' "Fill argument 02 with initial value?
* X_CONTEXT_ID = ' ' "Fill argument 03 with initial value?
* X_DP_SERVER_NAME = ' ' "Fill argument 04 with initial value?
.



IMPORTING Parameters details for DEQUEUE_E_BGRFC_O_DEST_R

MODE_BGRFC_O_DEST_REGISTRATION - Lock mode for table BGRFC_O_DEST_REGISTRATION

Data type: ENQMODE
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SCOPE -

Data type:
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SYNCHRON - Synchonous unlock

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

_COLLECT - Initially only collect lock

Data type: DDENQCOLL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

DESTINATION_NAME - 01th enqueue argument

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

SCHEDULER_NR - 02th enqueue argument

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

CONTEXT_ID - 03th enqueue argument

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

DP_SERVER_NAME - 04th enqueue argument

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

X_DESTINATION_NAME - Fill argument 01 with initial value?

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

X_SCHEDULER_NR - Fill argument 02 with initial value?

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

X_CONTEXT_ID - Fill argument 03 with initial value?

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

X_DP_SERVER_NAME - Fill argument 04 with initial value?

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

Copy and paste ABAP code example for DEQUEUE_E_BGRFC_O_DEST_R 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_mode_bgrfc_o_dest_registration  TYPE ENQMODE, "   'E'
lv__scope  TYPE ENQMODE, "   '3'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_destination_name  TYPE BGRFC_O_DEST_REGISTRATION-DESTINATION_NAME, "   
lv_scheduler_nr  TYPE BGRFC_O_DEST_REGISTRATION-SCHEDULER_NR, "   
lv_context_id  TYPE BGRFC_O_DEST_REGISTRATION-CONTEXT_ID, "   
lv_dp_server_name  TYPE BGRFC_O_DEST_REGISTRATION-DP_SERVER_NAME, "   
lv_x_destination_name  TYPE BGRFC_O_DEST_REGISTRATION, "   SPACE
lv_x_scheduler_nr  TYPE BGRFC_O_DEST_REGISTRATION, "   SPACE
lv_x_context_id  TYPE BGRFC_O_DEST_REGISTRATION, "   SPACE
lv_x_dp_server_name  TYPE BGRFC_O_DEST_REGISTRATION. "   SPACE

  CALL FUNCTION 'DEQUEUE_E_BGRFC_O_DEST_R'  "Release lock on object E_BGRFC_O_DEST_R
    EXPORTING
         MODE_BGRFC_O_DEST_REGISTRATION = lv_mode_bgrfc_o_dest_registration
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         DESTINATION_NAME = lv_destination_name
         SCHEDULER_NR = lv_scheduler_nr
         CONTEXT_ID = lv_context_id
         DP_SERVER_NAME = lv_dp_server_name
         X_DESTINATION_NAME = lv_x_destination_name
         X_SCHEDULER_NR = lv_x_scheduler_nr
         X_CONTEXT_ID = lv_x_context_id
         X_DP_SERVER_NAME = lv_x_dp_server_name
. " DEQUEUE_E_BGRFC_O_DEST_R




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_BGRFC_O_DEST_R

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.

DATA(ld_mode_bgrfc_o_dest_registration) = 'E'.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single DESTINATION_NAME FROM BGRFC_O_DEST_REGISTRATION INTO @DATA(ld_destination_name).
 
"SELECT single SCHEDULER_NR FROM BGRFC_O_DEST_REGISTRATION INTO @DATA(ld_scheduler_nr).
 
"SELECT single CONTEXT_ID FROM BGRFC_O_DEST_REGISTRATION INTO @DATA(ld_context_id).
 
"SELECT single DP_SERVER_NAME FROM BGRFC_O_DEST_REGISTRATION INTO @DATA(ld_dp_server_name).
 
DATA(ld_x_destination_name) = ' '.
 
DATA(ld_x_scheduler_nr) = ' '.
 
DATA(ld_x_context_id) = ' '.
 
DATA(ld_x_dp_server_name) = ' '.
 


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!