SAP DEQUEUE_ESOTRTEXT Function Module for Release lock on object ESOTRTEXT









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

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



Function DEQUEUE_ESOTRTEXT 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_ESOTRTEXT'"Release lock on object ESOTRTEXT
EXPORTING
* MODE_SOTR_TEXT = 'E' "Lock mode for table SOTR_TEXT
* _COLLECT = ' ' "Initially only collect lock
* CONCEPT = "01th enqueue argument
* LANGU = "02th enqueue argument
* OBJECT = "03th enqueue argument
* X_CONCEPT = ' ' "Fill argument 01 with initial value?
* X_LANGU = ' ' "Fill argument 02 with initial value?
* X_OBJECT = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_ESOTRTEXT

MODE_SOTR_TEXT - Lock mode for table SOTR_TEXT

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)

CONCEPT - 01th enqueue argument

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

LANGU - 02th enqueue argument

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

OBJECT - 03th enqueue argument

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

X_CONCEPT - Fill argument 01 with initial value?

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

X_LANGU - Fill argument 02 with initial value?

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

X_OBJECT - 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_ESOTRTEXT 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_sotr_text  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_concept  TYPE SOTR_TEXT-CONCEPT, "   
lv_langu  TYPE SOTR_TEXT-LANGU, "   
lv_object  TYPE SOTR_TEXT-OBJECT, "   
lv_x_concept  TYPE SOTR_TEXT, "   SPACE
lv_x_langu  TYPE SOTR_TEXT, "   SPACE
lv_x_object  TYPE SOTR_TEXT, "   SPACE
lv__scope  TYPE SOTR_TEXT, "   '3'
lv__synchron  TYPE SOTR_TEXT. "   SPACE

  CALL FUNCTION 'DEQUEUE_ESOTRTEXT'  "Release lock on object ESOTRTEXT
    EXPORTING
         MODE_SOTR_TEXT = lv_mode_sotr_text
         _COLLECT = lv__collect
         CONCEPT = lv_concept
         LANGU = lv_langu
         OBJECT = lv_object
         X_CONCEPT = lv_x_concept
         X_LANGU = lv_x_langu
         X_OBJECT = lv_x_object
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_ESOTRTEXT




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ESOTRTEXT

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_sotr_text) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single CONCEPT FROM SOTR_TEXT INTO @DATA(ld_concept).
 
"SELECT single LANGU FROM SOTR_TEXT INTO @DATA(ld_langu).
 
"SELECT single OBJECT FROM SOTR_TEXT INTO @DATA(ld_object).
 
DATA(ld_x_concept) = ' '.
 
DATA(ld_x_langu) = ' '.
 
DATA(ld_x_object) = ' '.
 
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!