SAP DEQUEUE_ECNV_10020_PATH Function Module for Release lock on object ECNV_10020_PATH









DEQUEUE_ECNV_10020_PATH is a standard dequeue ecnv 10020 path 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 ECNV_10020_PATH 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 ecnv 10020 path FM, simply by entering the name DEQUEUE_ECNV_10020_PATH into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_ECNV_10020_PATH 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_ECNV_10020_PATH'"Release lock on object ECNV_10020_PATH
EXPORTING
* MODE_CNV_10020_PATH = 'E' "Lock mode for table CNV_10020_PATH
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* PACKID = "02th enqueue argument
* PATHID = "03th enqueue argument
* PATHTYPE = "04th enqueue argument
* X_PACKID = ' ' "Fill argument 02 with initial value?
* X_PATHID = ' ' "Fill argument 03 with initial value?
* X_PATHTYPE = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_ECNV_10020_PATH

MODE_CNV_10020_PATH - Lock mode for table CNV_10020_PATH

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: CNV_10020_PATH-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PACKID - 02th enqueue argument

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

PATHID - 03th enqueue argument

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

PATHTYPE - 04th enqueue argument

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

X_PACKID - Fill argument 02 with initial value?

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

X_PATHID - Fill argument 03 with initial value?

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

X_PATHTYPE - 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_ECNV_10020_PATH 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_cnv_10020_path  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE CNV_10020_PATH-MANDT, "   SY-MANDT
lv_packid  TYPE CNV_10020_PATH-PACKID, "   
lv_pathid  TYPE CNV_10020_PATH-PATHID, "   
lv_pathtype  TYPE CNV_10020_PATH-PATHTYPE, "   
lv_x_packid  TYPE CNV_10020_PATH, "   SPACE
lv_x_pathid  TYPE CNV_10020_PATH, "   SPACE
lv_x_pathtype  TYPE CNV_10020_PATH, "   SPACE
lv__scope  TYPE CNV_10020_PATH. "   '3'

  CALL FUNCTION 'DEQUEUE_ECNV_10020_PATH'  "Release lock on object ECNV_10020_PATH
    EXPORTING
         MODE_CNV_10020_PATH = lv_mode_cnv_10020_path
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         PACKID = lv_packid
         PATHID = lv_pathid
         PATHTYPE = lv_pathtype
         X_PACKID = lv_x_packid
         X_PATHID = lv_x_pathid
         X_PATHTYPE = lv_x_pathtype
         _SCOPE = lv__scope
. " DEQUEUE_ECNV_10020_PATH




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ECNV_10020_PATH

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_cnv_10020_path) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM CNV_10020_PATH INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single PACKID FROM CNV_10020_PATH INTO @DATA(ld_packid).
 
"SELECT single PATHID FROM CNV_10020_PATH INTO @DATA(ld_pathid).
 
"SELECT single PATHTYPE FROM CNV_10020_PATH INTO @DATA(ld_pathtype).
 
DATA(ld_x_packid) = ' '.
 
DATA(ld_x_pathid) = ' '.
 
DATA(ld_x_pathtype) = ' '.
 
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!