SAP DEQUEUE_ETNAMECHANGE Function Module for Release lock on object ETNAMECHANGE









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

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



Function DEQUEUE_ETNAMECHANGE 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_ETNAMECHANGE'"Release lock on object ETNAMECHANGE
  EXPORTING
*  MODE_TNAMECHANGE = 'E' "Lock mode for table TNAMECHANGE
*  _COLLECT = ' ' "Initially only collect lock
*  INPUT_VALUE =  "01th enqueue argument
*  ENVIRON =  "02th enqueue argument
*  CATTUSER =  "03th enqueue argument
*  X_INPUT_VALUE = ' ' "Fill argument 01 with initial value?
*  X_ENVIRON = ' ' "Fill argument 02 with initial value?
*  X_CATTUSER = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_ETNAMECHANGE

MODE_TNAMECHANGE - Lock mode for table TNAMECHANGE

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)

INPUT_VALUE - 01th enqueue argument

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

ENVIRON - 02th enqueue argument

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

CATTUSER - 03th enqueue argument

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

X_INPUT_VALUE - Fill argument 01 with initial value?

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

X_ENVIRON - Fill argument 02 with initial value?

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

X_CATTUSER - 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_ETNAMECHANGE 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_tnamechange  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_input_value  TYPE TNAMECHANGE-INPUT_VALUE, "   
lv_environ  TYPE TNAMECHANGE-ENVIRON, "   
lv_cattuser  TYPE TNAMECHANGE-CATTUSER, "   
lv_x_input_value  TYPE TNAMECHANGE, "   SPACE
lv_x_environ  TYPE TNAMECHANGE, "   SPACE
lv_x_cattuser  TYPE TNAMECHANGE, "   SPACE
lv__scope  TYPE TNAMECHANGE, "   '3'
lv__synchron  TYPE TNAMECHANGE. "   SPACE

  CALL FUNCTION 'DEQUEUE_ETNAMECHANGE'  "Release lock on object ETNAMECHANGE
    EXPORTING
         MODE_TNAMECHANGE = lv_mode_tnamechange
         _COLLECT = lv__collect
         INPUT_VALUE = lv_input_value
         ENVIRON = lv_environ
         CATTUSER = lv_cattuser
         X_INPUT_VALUE = lv_x_input_value
         X_ENVIRON = lv_x_environ
         X_CATTUSER = lv_x_cattuser
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_ETNAMECHANGE




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ETNAMECHANGE

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_tnamechange) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single INPUT_VALUE FROM TNAMECHANGE INTO @DATA(ld_input_value).
 
"SELECT single ENVIRON FROM TNAMECHANGE INTO @DATA(ld_environ).
 
"SELECT single CATTUSER FROM TNAMECHANGE INTO @DATA(ld_cattuser).
 
DATA(ld_x_input_value) = ' '.
 
DATA(ld_x_environ) = ' '.
 
DATA(ld_x_cattuser) = ' '.
 
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!