SAP Function Modules

DEQUEUE_E_LXE_PC SAP Function module - Release lock on object E_LXE_PC







DEQUEUE_E_LXE_PC is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DEQUEUE_E_LXE_PC into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: DWBEN/SAPLSEN0008
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM DEQUEUE_E_LXE_PC - DEQUEUE E LXE PC





CALL FUNCTION 'DEQUEUE_E_LXE_PC' "Release lock on object E_LXE_PC
* EXPORTING
*   mode_lxe_pc_hd = 'E'        " enqmode       Lock mode for table LXE_PC_HD
*   custmnr =                   " lxe_pc_hd-custmnr  01th enqueue argument
*   objname =                   " lxe_pc_hd-objname  02th enqueue argument
*   x_custmnr = SPACE           "               Fill argument 01 with initial value?
*   x_objname = SPACE           "               Fill argument 02 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_E_LXE_PC

ABAP code example for Function Module DEQUEUE_E_LXE_PC





The ABAP code below is a full code listing to execute function module DEQUEUE_E_LXE_PC including all data declarations. The code uses 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 original method of declaring data variables up front. 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).


DATA(ld_mode_lxe_pc_hd) = 'Check type of data required'.

SELECT single CUSTMNR
FROM LXE_PC_HD
INTO @DATA(ld_custmnr).


SELECT single OBJNAME
FROM LXE_PC_HD
INTO @DATA(ld_objname).

DATA(ld_x_custmnr) = 'some text here'.
DATA(ld_x_objname) = 'some text here'.
DATA(ld__scope) = 'some text here'.
DATA(ld__synchron) = 'some text here'.
DATA(ld__collect) = 'Check type of data required'. . CALL FUNCTION 'DEQUEUE_E_LXE_PC' * EXPORTING * mode_lxe_pc_hd = ld_mode_lxe_pc_hd * custmnr = ld_custmnr * objname = ld_objname * x_custmnr = ld_x_custmnr * x_objname = ld_x_objname * _scope = ld__scope * _synchron = ld__synchron * _collect = ld__collect . " DEQUEUE_E_LXE_PC
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_mode_lxe_pc_hd  TYPE ENQMODE ,
ld_custmnr  TYPE LXE_PC_HD-CUSTMNR ,
ld_objname  TYPE LXE_PC_HD-OBJNAME ,
ld_x_custmnr  TYPE STRING ,
ld_x_objname  TYPE STRING ,
ld__scope  TYPE STRING ,
ld__synchron  TYPE STRING ,
ld__collect  TYPE DDENQCOLL .

ld_mode_lxe_pc_hd = 'Check type of data required'.

SELECT single CUSTMNR
FROM LXE_PC_HD
INTO ld_custmnr.


SELECT single OBJNAME
FROM LXE_PC_HD
INTO ld_objname.

ld_x_custmnr = 'some text here'.
ld_x_objname = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name DEQUEUE_E_LXE_PC or its description.