SAP ENQUEUE_E_THTEST Function Module for Request lock for object E_THTEST









ENQUEUE_E_THTEST is a standard enqueue e thtest 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 E_THTEST 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 e thtest FM, simply by entering the name ENQUEUE_E_THTEST into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_E_THTEST 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_E_THTEST'"Request lock for object E_THTEST
  EXPORTING
*  MODE_TTHTEST = 'E' "Lock mode for table TTHTEST
*  _COLLECT = ' ' "Initially only collect lock
*  DATUM =  "01th enqueue argument
*  UZEIT =  "02th enqueue argument
*  COUNTER =  "03th enqueue argument
*  X_DATUM = ' ' "Fill argument 01 with initial value?
*  X_UZEIT = ' ' "Fill argument 02 with initial value?
*  X_COUNTER = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '2' "
*  _WAIT = ' ' "

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_E_THTEST

MODE_TTHTEST - Lock mode for table TTHTEST

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)

DATUM - 01th enqueue argument

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

UZEIT - 02th enqueue argument

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

COUNTER - 03th enqueue argument

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

X_DATUM - Fill argument 01 with initial value?

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

X_UZEIT - Fill argument 02 with initial value?

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

X_COUNTER - 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: '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)

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_E_THTEST 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_tthtest  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_datum  TYPE TTHTEST-DATUM, "   
lv_system_failure  TYPE TTHTEST, "   
lv_uzeit  TYPE TTHTEST-UZEIT, "   
lv_counter  TYPE TTHTEST-COUNTER, "   
lv_x_datum  TYPE TTHTEST, "   SPACE
lv_x_uzeit  TYPE TTHTEST, "   SPACE
lv_x_counter  TYPE TTHTEST, "   SPACE
lv__scope  TYPE TTHTEST, "   '2'
lv__wait  TYPE TTHTEST. "   SPACE

  CALL FUNCTION 'ENQUEUE_E_THTEST'  "Request lock for object E_THTEST
    EXPORTING
         MODE_TTHTEST = lv_mode_tthtest
         _COLLECT = lv__collect
         DATUM = lv_datum
         UZEIT = lv_uzeit
         COUNTER = lv_counter
         X_DATUM = lv_x_datum
         X_UZEIT = lv_x_uzeit
         X_COUNTER = lv_x_counter
         _SCOPE = lv__scope
         _WAIT = lv__wait
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_E_THTEST




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_THTEST

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_tthtest) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single DATUM FROM TTHTEST INTO @DATA(ld_datum).
 
 
"SELECT single UZEIT FROM TTHTEST INTO @DATA(ld_uzeit).
 
"SELECT single COUNTER FROM TTHTEST INTO @DATA(ld_counter).
 
DATA(ld_x_datum) = ' '.
 
DATA(ld_x_uzeit) = ' '.
 
DATA(ld_x_counter) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 


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!