SAP DEQUEUE_ECMX_XS Function Module for Release lock on object ECMX_XS









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

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



Function DEQUEUE_ECMX_XS 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_ECMX_XS'"Release lock on object ECMX_XS
EXPORTING
* MODE_CMX_XS_W_ENQUEUE = 'E' "Lock mode for table CMX_XS_W_ENQUEUE
* _COLLECT = ' ' "Initially only collect lock
* NID = "01th enqueue argument
* OID = "02th enqueue argument
* ENQUEUE_TYPE = "03th enqueue argument
* X_NID = ' ' "Fill argument 01 with initial value?
* X_OID = ' ' "Fill argument 02 with initial value?
* X_ENQUEUE_TYPE = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_ECMX_XS

MODE_CMX_XS_W_ENQUEUE - Lock mode for table CMX_XS_W_ENQUEUE

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)

NID - 01th enqueue argument

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

OID - 02th enqueue argument

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

ENQUEUE_TYPE - 03th enqueue argument

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

X_NID - Fill argument 01 with initial value?

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

X_OID - Fill argument 02 with initial value?

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

X_ENQUEUE_TYPE - 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_ECMX_XS 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_cmx_xs_w_enqueue  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_nid  TYPE CMX_XS_W_ENQUEUE-NID, "   
lv_oid  TYPE CMX_XS_W_ENQUEUE-OID, "   
lv_enqueue_type  TYPE CMX_XS_W_ENQUEUE-ENQUEUE_TYPE, "   
lv_x_nid  TYPE CMX_XS_W_ENQUEUE, "   SPACE
lv_x_oid  TYPE CMX_XS_W_ENQUEUE, "   SPACE
lv_x_enqueue_type  TYPE CMX_XS_W_ENQUEUE, "   SPACE
lv__scope  TYPE CMX_XS_W_ENQUEUE, "   '3'
lv__synchron  TYPE CMX_XS_W_ENQUEUE. "   SPACE

  CALL FUNCTION 'DEQUEUE_ECMX_XS'  "Release lock on object ECMX_XS
    EXPORTING
         MODE_CMX_XS_W_ENQUEUE = lv_mode_cmx_xs_w_enqueue
         _COLLECT = lv__collect
         NID = lv_nid
         OID = lv_oid
         ENQUEUE_TYPE = lv_enqueue_type
         X_NID = lv_x_nid
         X_OID = lv_x_oid
         X_ENQUEUE_TYPE = lv_x_enqueue_type
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_ECMX_XS




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ECMX_XS

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_cmx_xs_w_enqueue) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single NID FROM CMX_XS_W_ENQUEUE INTO @DATA(ld_nid).
 
"SELECT single OID FROM CMX_XS_W_ENQUEUE INTO @DATA(ld_oid).
 
"SELECT single ENQUEUE_TYPE FROM CMX_XS_W_ENQUEUE INTO @DATA(ld_enqueue_type).
 
DATA(ld_x_nid) = ' '.
 
DATA(ld_x_oid) = ' '.
 
DATA(ld_x_enqueue_type) = ' '.
 
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!