SAP DEQUEUE_E_TEM_VERSION Function Module for Release lock on object E_TEM_VERSION









DEQUEUE_E_TEM_VERSION is a standard dequeue e tem version 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 E_TEM_VERSION 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 e tem version FM, simply by entering the name DEQUEUE_E_TEM_VERSION into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_TEM_VERSION 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_E_TEM_VERSION'"Release lock on object E_TEM_VERSION
EXPORTING
* MODE_TEMT_VERSION = 'E' "Lock mode for table TEMT_VERSION
* MANDT = SY-MANDT "01th enqueue argument
* PROFILE_ID = "02th enqueue argument
* VERSION_NO = "03th enqueue argument
* X_PROFILE_ID = ' ' "Fill argument 02 with initial value?
* X_VERSION_NO = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_E_TEM_VERSION

MODE_TEMT_VERSION - Lock mode for table TEMT_VERSION

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

MANDT - 01th enqueue argument

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

PROFILE_ID - 02th enqueue argument

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

VERSION_NO - 03th enqueue argument

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

X_PROFILE_ID - Fill argument 02 with initial value?

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

X_VERSION_NO - 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_E_TEM_VERSION 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_temt_version  TYPE ENQMODE, "   'E'
lv_mandt  TYPE TEMT_VERSION-MANDT, "   SY-MANDT
lv_profile_id  TYPE TEMT_VERSION-PROFILE_ID, "   
lv_version_no  TYPE TEMT_VERSION-VERSION_NO, "   
lv_x_profile_id  TYPE TEMT_VERSION, "   SPACE
lv_x_version_no  TYPE TEMT_VERSION, "   SPACE
lv__scope  TYPE TEMT_VERSION, "   '3'
lv__synchron  TYPE TEMT_VERSION, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_E_TEM_VERSION'  "Release lock on object E_TEM_VERSION
    EXPORTING
         MODE_TEMT_VERSION = lv_mode_temt_version
         MANDT = lv_mandt
         PROFILE_ID = lv_profile_id
         VERSION_NO = lv_version_no
         X_PROFILE_ID = lv_x_profile_id
         X_VERSION_NO = lv_x_version_no
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_E_TEM_VERSION




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_TEM_VERSION

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_temt_version) = 'E'.
 
"SELECT single MANDT FROM TEMT_VERSION INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single PROFILE_ID FROM TEMT_VERSION INTO @DATA(ld_profile_id).
 
"SELECT single VERSION_NO FROM TEMT_VERSION INTO @DATA(ld_version_no).
 
DATA(ld_x_profile_id) = ' '.
 
DATA(ld_x_version_no) = ' '.
 
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!