SAP DEQUEUE_E_TFW_MINITP Function Module for Release lock on object E_TFW_MINITP









DEQUEUE_E_TFW_MINITP is a standard dequeue e tfw minitp 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 E_TFW_MINITP 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 e tfw minitp FM, simply by entering the name DEQUEUE_E_TFW_MINITP into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_TFW_MINITP 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_E_TFW_MINITP'"Release lock on object E_TFW_MINITP
EXPORTING
* MODE_TFW_MINITP = 'E' "Lock mode for table TFW_MINITP
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* CLIENT = SY-MANDT "01th enqueue argument
* TFW_OBJECT = "02th enqueue argument
* MINITP_TYPE = "03th enqueue argument
* MINITP_ID = "04th enqueue argument
* X_TFW_OBJECT = ' ' "Fill argument 02 with initial value?
* X_MINITP_TYPE = ' ' "Fill argument 03 with initial value?
* X_MINITP_ID = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_TFW_MINITP

MODE_TFW_MINITP - Lock mode for table TFW_MINITP

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)

CLIENT - 01th enqueue argument

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

TFW_OBJECT - 02th enqueue argument

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

MINITP_TYPE - 03th enqueue argument

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

MINITP_ID - 04th enqueue argument

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

X_TFW_OBJECT - Fill argument 02 with initial value?

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

X_MINITP_TYPE - Fill argument 03 with initial value?

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

X_MINITP_ID - 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_E_TFW_MINITP 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_tfw_minitp  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_client  TYPE TFW_MINITP-CLIENT, "   SY-MANDT
lv_tfw_object  TYPE TFW_MINITP-TFW_OBJECT, "   
lv_minitp_type  TYPE TFW_MINITP-MINITP_TYPE, "   
lv_minitp_id  TYPE TFW_MINITP-MINITP_ID, "   
lv_x_tfw_object  TYPE TFW_MINITP, "   SPACE
lv_x_minitp_type  TYPE TFW_MINITP, "   SPACE
lv_x_minitp_id  TYPE TFW_MINITP, "   SPACE
lv__scope  TYPE TFW_MINITP. "   '3'

  CALL FUNCTION 'DEQUEUE_E_TFW_MINITP'  "Release lock on object E_TFW_MINITP
    EXPORTING
         MODE_TFW_MINITP = lv_mode_tfw_minitp
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         CLIENT = lv_client
         TFW_OBJECT = lv_tfw_object
         MINITP_TYPE = lv_minitp_type
         MINITP_ID = lv_minitp_id
         X_TFW_OBJECT = lv_x_tfw_object
         X_MINITP_TYPE = lv_x_minitp_type
         X_MINITP_ID = lv_x_minitp_id
         _SCOPE = lv__scope
. " DEQUEUE_E_TFW_MINITP




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_TFW_MINITP

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_tfw_minitp) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single CLIENT FROM TFW_MINITP INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single TFW_OBJECT FROM TFW_MINITP INTO @DATA(ld_tfw_object).
 
"SELECT single MINITP_TYPE FROM TFW_MINITP INTO @DATA(ld_minitp_type).
 
"SELECT single MINITP_ID FROM TFW_MINITP INTO @DATA(ld_minitp_id).
 
DATA(ld_x_tfw_object) = ' '.
 
DATA(ld_x_minitp_type) = ' '.
 
DATA(ld_x_minitp_id) = ' '.
 
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!