SAP DEQUEUE_ERTC_ERI Function Module for Release lock on object ERTC_ERI









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

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



Function DEQUEUE_ERTC_ERI 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_ERTC_ERI'"Release lock on object ERTC_ERI
  EXPORTING
*  MODE_RTC_CT1200 = 'E' "Lock mode for table RTC_CT1200
*  _COLLECT = ' ' "Initially only collect lock
*  MODE_RTC_CT120T = 'E' "Lock mode for table RTC_CT120T
*  MANDT = SY-MANDT "01th enqueue argument
*  XRIND =  "02th enqueue argument
*  LANGU =  "03th enqueue argument
*  X_XRIND = ' ' "Fill argument 02 with initial value?
*  X_LANGU = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_ERTC_ERI

MODE_RTC_CT1200 - Lock mode for table RTC_CT1200

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)

MODE_RTC_CT120T - Lock mode for table RTC_CT120T

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

MANDT - 01th enqueue argument

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

XRIND - 02th enqueue argument

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

LANGU - 03th enqueue argument

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

X_XRIND - Fill argument 02 with initial value?

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

X_LANGU - 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_ERTC_ERI 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_rtc_ct1200  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mode_rtc_ct120t  TYPE ENQMODE, "   'E'
lv_mandt  TYPE RTC_CT1200-MANDT, "   SY-MANDT
lv_xrind  TYPE RTC_CT1200-XRIND, "   
lv_langu  TYPE RTC_CT120T-LANGU, "   
lv_x_xrind  TYPE RTC_CT120T, "   SPACE
lv_x_langu  TYPE RTC_CT120T, "   SPACE
lv__scope  TYPE RTC_CT120T, "   '3'
lv__synchron  TYPE RTC_CT120T. "   SPACE

  CALL FUNCTION 'DEQUEUE_ERTC_ERI'  "Release lock on object ERTC_ERI
    EXPORTING
         MODE_RTC_CT1200 = lv_mode_rtc_ct1200
         _COLLECT = lv__collect
         MODE_RTC_CT120T = lv_mode_rtc_ct120t
         MANDT = lv_mandt
         XRIND = lv_xrind
         LANGU = lv_langu
         X_XRIND = lv_x_xrind
         X_LANGU = lv_x_langu
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_ERTC_ERI




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ERTC_ERI

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_rtc_ct1200) = 'E'.
 
DATA(ld__collect) = ' '.
 
DATA(ld_mode_rtc_ct120t) = 'E'.
 
"SELECT single MANDT FROM RTC_CT1200 INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single XRIND FROM RTC_CT1200 INTO @DATA(ld_xrind).
 
"SELECT single LANGU FROM RTC_CT120T INTO @DATA(ld_langu).
 
DATA(ld_x_xrind) = ' '.
 
DATA(ld_x_langu) = ' '.
 
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!