SAP DEQUEUE_E_CRMC_BL_QUERY Function Module for Release lock on object E_CRMC_BL_QUERY









DEQUEUE_E_CRMC_BL_QUERY is a standard dequeue e crmc bl query 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_CRMC_BL_QUERY 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 crmc bl query FM, simply by entering the name DEQUEUE_E_CRMC_BL_QUERY into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_CRMC_BL_QUERY 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_CRMC_BL_QUERY'"Release lock on object E_CRMC_BL_QUERY
EXPORTING
* MODE_CRMC_BL_QUERY = 'E' "Lock mode for table CRMC_BL_QUERY
* _COLLECT = ' ' "Initially only collect lock
* APPLICATION = "01th enqueue argument
* USERROLE = "02th enqueue argument
* SEARCHNAME = "03th enqueue argument
* X_APPLICATION = ' ' "Fill argument 01 with initial value?
* X_USERROLE = ' ' "Fill argument 02 with initial value?
* X_SEARCHNAME = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_E_CRMC_BL_QUERY

MODE_CRMC_BL_QUERY - Lock mode for table CRMC_BL_QUERY

Data type: ENQMODE
Default: 'E'
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)

APPLICATION - 01th enqueue argument

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

USERROLE - 02th enqueue argument

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

SEARCHNAME - 03th enqueue argument

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

X_APPLICATION - Fill argument 01 with initial value?

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

X_USERROLE - Fill argument 02 with initial value?

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

X_SEARCHNAME - Fill argument 03 with initial value?

Data type:
Default: SPACE
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)

Copy and paste ABAP code example for DEQUEUE_E_CRMC_BL_QUERY 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_crmc_bl_query  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_application  TYPE CRMC_BL_QUERY-APPLICATION, "   
lv_userrole  TYPE CRMC_BL_QUERY-USERROLE, "   
lv_searchname  TYPE CRMC_BL_QUERY-SEARCHNAME, "   
lv_x_application  TYPE CRMC_BL_QUERY, "   SPACE
lv_x_userrole  TYPE CRMC_BL_QUERY, "   SPACE
lv_x_searchname  TYPE CRMC_BL_QUERY, "   SPACE
lv__scope  TYPE CRMC_BL_QUERY, "   '3'
lv__synchron  TYPE CRMC_BL_QUERY. "   SPACE

  CALL FUNCTION 'DEQUEUE_E_CRMC_BL_QUERY'  "Release lock on object E_CRMC_BL_QUERY
    EXPORTING
         MODE_CRMC_BL_QUERY = lv_mode_crmc_bl_query
         _COLLECT = lv__collect
         APPLICATION = lv_application
         USERROLE = lv_userrole
         SEARCHNAME = lv_searchname
         X_APPLICATION = lv_x_application
         X_USERROLE = lv_x_userrole
         X_SEARCHNAME = lv_x_searchname
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_E_CRMC_BL_QUERY




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_CRMC_BL_QUERY

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_crmc_bl_query) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single APPLICATION FROM CRMC_BL_QUERY INTO @DATA(ld_application).
 
"SELECT single USERROLE FROM CRMC_BL_QUERY INTO @DATA(ld_userrole).
 
"SELECT single SEARCHNAME FROM CRMC_BL_QUERY INTO @DATA(ld_searchname).
 
DATA(ld_x_application) = ' '.
 
DATA(ld_x_userrole) = ' '.
 
DATA(ld_x_searchname) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 


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!