SAP DEQUEUE_ECNV_PE_BTC_CFGL Function Module for Release lock on object ECNV_PE_BTC_CFGL









DEQUEUE_ECNV_PE_BTC_CFGL is a standard dequeue ecnv pe btc cfgl 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_PE_BTC_CFGL 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 pe btc cfgl FM, simply by entering the name DEQUEUE_ECNV_PE_BTC_CFGL into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_ECNV_PE_BTC_CFGL 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_PE_BTC_CFGL'"Release lock on object ECNV_PE_BTC_CFGL
EXPORTING
* MODE_CNV_PE_BTC_CFGL = 'X' "Lock mode for table CNV_PE_BTC_CFGL
* MANDT = SY-MANDT "Enqueue argument 01
* OWNER_ID = "Enqueue argument 02
* TARGET = "Enqueue argument 03
* X_OWNER_ID = ' ' "Fill argument 02 with initial value?
* X_TARGET = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_ECNV_PE_BTC_CFGL

MODE_CNV_PE_BTC_CFGL - Lock mode for table CNV_PE_BTC_CFGL

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

MANDT - Enqueue argument 01

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

OWNER_ID - Enqueue argument 02

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

TARGET - Enqueue argument 03

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

X_OWNER_ID - Fill argument 02 with initial value?

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

X_TARGET - 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_ECNV_PE_BTC_CFGL 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_pe_btc_cfgl  TYPE ENQMODE, "   'X'
lv_mandt  TYPE CNV_PE_BTC_CFGL-MANDT, "   SY-MANDT
lv_owner_id  TYPE CNV_PE_BTC_CFGL-OWNER_ID, "   
lv_target  TYPE CNV_PE_BTC_CFGL-TARGET, "   
lv_x_owner_id  TYPE CNV_PE_BTC_CFGL, "   SPACE
lv_x_target  TYPE CNV_PE_BTC_CFGL, "   SPACE
lv__scope  TYPE CNV_PE_BTC_CFGL, "   '3'
lv__synchron  TYPE CNV_PE_BTC_CFGL, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_ECNV_PE_BTC_CFGL'  "Release lock on object ECNV_PE_BTC_CFGL
    EXPORTING
         MODE_CNV_PE_BTC_CFGL = lv_mode_cnv_pe_btc_cfgl
         MANDT = lv_mandt
         OWNER_ID = lv_owner_id
         TARGET = lv_target
         X_OWNER_ID = lv_x_owner_id
         X_TARGET = lv_x_target
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_ECNV_PE_BTC_CFGL




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ECNV_PE_BTC_CFGL

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_pe_btc_cfgl) = 'X'.
 
"SELECT single MANDT FROM CNV_PE_BTC_CFGL INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single OWNER_ID FROM CNV_PE_BTC_CFGL INTO @DATA(ld_owner_id).
 
"SELECT single TARGET FROM CNV_PE_BTC_CFGL INTO @DATA(ld_target).
 
DATA(ld_x_owner_id) = ' '.
 
DATA(ld_x_target) = ' '.
 
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!