SAP ENQUEUE_ES_LDQ_PROGRESS Function Module for Request lock for object ES_LDQ_PROGRESS









ENQUEUE_ES_LDQ_PROGRESS is a standard enqueue es ldq progress SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object ES_LDQ_PROGRESS 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 enqueue es ldq progress FM, simply by entering the name ENQUEUE_ES_LDQ_PROGRESS 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 ENQUEUE_ES_LDQ_PROGRESS 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 'ENQUEUE_ES_LDQ_PROGRESS'"Request lock for object ES_LDQ_PROGRESS
EXPORTING
* MODE_LDQ_PROGRESS = 'E' "Lock mode for table LDQ_PROGRESS
* APPLICATION_NAME = "01th enqueue argument
* CLIENT = SY-MANDT "02th enqueue argument
* X_APPLICATION_NAME = ' ' "Fill argument 01 with initial value?
* _SCOPE = '2' "
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_ES_LDQ_PROGRESS

MODE_LDQ_PROGRESS - Lock mode for table LDQ_PROGRESS

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_PROGRESS-APPLICATION_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLIENT - 02th enqueue argument

Data type: LDQ_PROGRESS-CLIENT
Default: SY-MANDT
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)

_SCOPE -

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

_WAIT -

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)

EXCEPTIONS details

FOREIGN_LOCK - Object already locked

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

SYSTEM_FAILURE - Internal error from enqueue server

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

Copy and paste ABAP code example for ENQUEUE_ES_LDQ_PROGRESS 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_foreign_lock  TYPE STRING, "   
lv_mode_ldq_progress  TYPE ENQMODE, "   'E'
lv_system_failure  TYPE ENQMODE, "   
lv_application_name  TYPE LDQ_PROGRESS-APPLICATION_NAME, "   
lv_client  TYPE LDQ_PROGRESS-CLIENT, "   SY-MANDT
lv_x_application_name  TYPE LDQ_PROGRESS, "   SPACE
lv__scope  TYPE LDQ_PROGRESS, "   '2'
lv__wait  TYPE LDQ_PROGRESS, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'ENQUEUE_ES_LDQ_PROGRESS'  "Request lock for object ES_LDQ_PROGRESS
    EXPORTING
         MODE_LDQ_PROGRESS = lv_mode_ldq_progress
         APPLICATION_NAME = lv_application_name
         CLIENT = lv_client
         X_APPLICATION_NAME = lv_x_application_name
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_ES_LDQ_PROGRESS




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_ES_LDQ_PROGRESS

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_progress) = 'E'.
 
 
"SELECT single APPLICATION_NAME FROM LDQ_PROGRESS INTO @DATA(ld_application_name).
 
"SELECT single CLIENT FROM LDQ_PROGRESS INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
DATA(ld_x_application_name) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 
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!