SAP DEQUEUE_ES_LDQ_STATE Function Module for Release lock on object ES_LDQ_STATE









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

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



Function DEQUEUE_ES_LDQ_STATE 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_LDQ_STATE'"Release lock on object ES_LDQ_STATE
  EXPORTING
*  MODE_LDQ_STATE = 'E' "Lock mode for table LDQ_STATE
*  APPLICATION_NAME =  "01th enqueue argument
*  CLIENT = SY-MANDT "02th enqueue argument
*  QUEUE_NAME =  "03th enqueue argument
*  X_APPLICATION_NAME = ' ' "Fill argument 01 with initial value?
*  X_QUEUE_NAME = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_ES_LDQ_STATE

MODE_LDQ_STATE - Lock mode for table LDQ_STATE

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

APPLICATION_NAME - 01th enqueue argument

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

CLIENT - 02th enqueue argument

Data type: LDQ_STATE-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

QUEUE_NAME - 03th enqueue argument

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

X_APPLICATION_NAME - Fill argument 01 with initial value?

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

X_QUEUE_NAME - 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)

_COLLECT - Initially only collect lock

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

Copy and paste ABAP code example for DEQUEUE_ES_LDQ_STATE 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_ldq_state  TYPE ENQMODE, "   'E'
lv_application_name  TYPE LDQ_STATE-APPLICATION_NAME, "   
lv_client  TYPE LDQ_STATE-CLIENT, "   SY-MANDT
lv_queue_name  TYPE LDQ_STATE-QUEUE_NAME, "   
lv_x_application_name  TYPE LDQ_STATE, "   SPACE
lv_x_queue_name  TYPE LDQ_STATE, "   SPACE
lv__scope  TYPE LDQ_STATE, "   '3'
lv__synchron  TYPE LDQ_STATE, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_ES_LDQ_STATE'  "Release lock on object ES_LDQ_STATE
    EXPORTING
         MODE_LDQ_STATE = lv_mode_ldq_state
         APPLICATION_NAME = lv_application_name
         CLIENT = lv_client
         QUEUE_NAME = lv_queue_name
         X_APPLICATION_NAME = lv_x_application_name
         X_QUEUE_NAME = lv_x_queue_name
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_ES_LDQ_STATE




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ES_LDQ_STATE

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_ldq_state) = 'E'.
 
"SELECT single APPLICATION_NAME FROM LDQ_STATE INTO @DATA(ld_application_name).
 
"SELECT single CLIENT FROM LDQ_STATE INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single QUEUE_NAME FROM LDQ_STATE INTO @DATA(ld_queue_name).
 
DATA(ld_x_application_name) = ' '.
 
DATA(ld_x_queue_name) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 


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!