SAP DEQUEUE_EMT496D Function Module for Release lock on object EMT496D









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

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



Function DEQUEUE_EMT496D 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_EMT496D'"Release lock on object EMT496D
  EXPORTING
*  MODE_T496D = 'E' "Lock mode for table T496D
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
*  MANDT = SY-MANDT "01th enqueue argument
*  AUTYP =  "02th enqueue argument
*  PUSER =  "03th enqueue argument
*  WERKS =  "04th enqueue argument
*  X_AUTYP = ' ' "Fill argument 02 with initial value?
*  X_PUSER = ' ' "Fill argument 03 with initial value?
*  X_WERKS = ' ' "Fill argument 04 with initial value?
*  _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_EMT496D

MODE_T496D - Lock mode for table T496D

Data type: ENQMODE
Default: 'E'
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)

MANDT - 01th enqueue argument

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

AUTYP - 02th enqueue argument

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

PUSER - 03th enqueue argument

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

WERKS - 04th enqueue argument

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

X_AUTYP - Fill argument 02 with initial value?

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

X_PUSER - Fill argument 03 with initial value?

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

X_WERKS - Fill argument 04 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)

Copy and paste ABAP code example for DEQUEUE_EMT496D 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_t496d  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE T496D-MANDT, "   SY-MANDT
lv_autyp  TYPE T496D-AUTYP, "   
lv_puser  TYPE T496D-PUSER, "   
lv_werks  TYPE T496D-WERKS, "   
lv_x_autyp  TYPE T496D, "   SPACE
lv_x_puser  TYPE T496D, "   SPACE
lv_x_werks  TYPE T496D, "   SPACE
lv__scope  TYPE T496D. "   '3'

  CALL FUNCTION 'DEQUEUE_EMT496D'  "Release lock on object EMT496D
    EXPORTING
         MODE_T496D = lv_mode_t496d
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         AUTYP = lv_autyp
         PUSER = lv_puser
         WERKS = lv_werks
         X_AUTYP = lv_x_autyp
         X_PUSER = lv_x_puser
         X_WERKS = lv_x_werks
         _SCOPE = lv__scope
. " DEQUEUE_EMT496D




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EMT496D

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_t496d) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM T496D INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single AUTYP FROM T496D INTO @DATA(ld_autyp).
 
"SELECT single PUSER FROM T496D INTO @DATA(ld_puser).
 
"SELECT single WERKS FROM T496D INTO @DATA(ld_werks).
 
DATA(ld_x_autyp) = ' '.
 
DATA(ld_x_puser) = ' '.
 
DATA(ld_x_werks) = ' '.
 
DATA(ld__scope) = '3'.
 


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!