SAP DEQUEUE_ES_CUATEXT Function Module for Release lock on object ES_CUATEXT









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

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



Function DEQUEUE_ES_CUATEXT 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_ES_CUATEXT'"Release lock on object ES_CUATEXT
  EXPORTING
*  MODE_CUATEXTS = 'E' "Lock mode for table CUATEXTS
*  _COLLECT = ' ' "Initially only collect lock
*  PROG =  "01th enqueue argument
*  CODE =  "02th enqueue argument
*  SPRSL =  "03th enqueue argument
*  X_PROG = ' ' "Fill argument 01 with initial value?
*  X_CODE = ' ' "Fill argument 02 with initial value?
*  X_SPRSL = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_ES_CUATEXT

MODE_CUATEXTS - Lock mode for table CUATEXTS

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)

PROG - 01th enqueue argument

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

CODE - 02th enqueue argument

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

SPRSL - 03th enqueue argument

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

X_PROG - Fill argument 01 with initial value?

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

X_CODE - Fill argument 02 with initial value?

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

X_SPRSL - 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_ES_CUATEXT 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_cuatexts  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_prog  TYPE CUATEXTS-PROG, "   
lv_code  TYPE CUATEXTS-CODE, "   
lv_sprsl  TYPE CUATEXTS-SPRSL, "   
lv_x_prog  TYPE CUATEXTS, "   SPACE
lv_x_code  TYPE CUATEXTS, "   SPACE
lv_x_sprsl  TYPE CUATEXTS, "   SPACE
lv__scope  TYPE CUATEXTS, "   '3'
lv__synchron  TYPE CUATEXTS. "   SPACE

  CALL FUNCTION 'DEQUEUE_ES_CUATEXT'  "Release lock on object ES_CUATEXT
    EXPORTING
         MODE_CUATEXTS = lv_mode_cuatexts
         _COLLECT = lv__collect
         PROG = lv_prog
         CODE = lv_code
         SPRSL = lv_sprsl
         X_PROG = lv_x_prog
         X_CODE = lv_x_code
         X_SPRSL = lv_x_sprsl
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_ES_CUATEXT




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ES_CUATEXT

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_cuatexts) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single PROG FROM CUATEXTS INTO @DATA(ld_prog).
 
"SELECT single CODE FROM CUATEXTS INTO @DATA(ld_code).
 
"SELECT single SPRSL FROM CUATEXTS INTO @DATA(ld_sprsl).
 
DATA(ld_x_prog) = ' '.
 
DATA(ld_x_code) = ' '.
 
DATA(ld_x_sprsl) = ' '.
 
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!