SAP TR_FEATURE_LOCK_INTERFACE Function Module for lock features









TR_FEATURE_LOCK_INTERFACE is a standard tr feature lock interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for lock features 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 tr feature lock interface FM, simply by entering the name TR_FEATURE_LOCK_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SGTA
Program Name: SAPLSGTA
Main Program: SAPLSGTA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TR_FEATURE_LOCK_INTERFACE 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 'TR_FEATURE_LOCK_INTERFACE'"lock features
  EXPORTING
   IV_MODE =  "Not More Closely Defined Area, Possibly Used for Patchlevels
*  IV_REG_WITH_OLD_LAYOUT =  "Boolean Variable (X=True, -=False, Space=Unknown)
*  IT_OBJECTS =  "
*  IT_KEYS =  "
*  IS_HEADER =  "
*  IV_FEATURE =  "Software Component
*  IV_FEATURE_NEW =  "Software Component
*  IV_SIMULATION =  "Boolean Variable (X=True, -=False, Space=Unknown)
*  IV_GET_DURATION =  "Single-Character Flag
*  IV_TEST =  "Boolean Variable (X=True, -=False, Space=Unknown)

 IMPORTING
   ET_OBJ_LOCKS =  "Table Type for GTABKEY_FEATURE_LOCK_OBJ
   ET_KEY_LOCKS =  "Table Type for GTABKEY_FEATURE_LOCK_KEY
   E_GTABKEY_RES =  "
   ET_GTABKEY =  "Global Table Keys

EXCEPTIONS
   WRONG_CALL = 1    ENQUEUE_FAILED = 2    GLOBAL_KEY_ERROR = 3
.



IMPORTING Parameters details for TR_FEATURE_LOCK_INTERFACE

IV_MODE - Not More Closely Defined Area, Possibly Used for Patchlevels

Data type: CHAR10
Optional: No
Call by Reference: Yes

IV_REG_WITH_OLD_LAYOUT - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

IT_OBJECTS -

Data type: TRWBO_T_E071
Optional: Yes
Call by Reference: Yes

IT_KEYS -

Data type: TRWBO_T_E071K
Optional: Yes
Call by Reference: Yes

IS_HEADER -

Data type: TRWBO_REQUEST_HEADER
Optional: Yes
Call by Reference: Yes

IV_FEATURE - Software Component

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

IV_FEATURE_NEW - Software Component

Data type: DLVUNIT
Optional: Yes
Call by Reference: Yes

IV_SIMULATION - Boolean Variable (X=True, -=False, Space=Unknown)

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

IV_GET_DURATION - Single-Character Flag

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

IV_TEST - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TR_FEATURE_LOCK_INTERFACE

ET_OBJ_LOCKS - Table Type for GTABKEY_FEATURE_LOCK_OBJ

Data type: GTABKEY_FEATURE_LOCK_OBJS
Optional: No
Call by Reference: Yes

ET_KEY_LOCKS - Table Type for GTABKEY_FEATURE_LOCK_KEY

Data type: GTABKEY_FEATURE_LOCK_KEYS
Optional: No
Call by Reference: Yes

E_GTABKEY_RES -

Data type: GTABKEYERROR
Optional: No
Call by Reference: Yes

ET_GTABKEY - Global Table Keys

Data type: TR_GTABKEYS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_CALL -

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

ENQUEUE_FAILED -

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

GLOBAL_KEY_ERROR -

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

Copy and paste ABAP code example for TR_FEATURE_LOCK_INTERFACE 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_iv_mode  TYPE CHAR10, "   
lv_wrong_call  TYPE CHAR10, "   
lv_et_obj_locks  TYPE GTABKEY_FEATURE_LOCK_OBJS, "   
lv_iv_reg_with_old_layout  TYPE BOOLEAN, "   
lv_it_objects  TYPE TRWBO_T_E071, "   
lv_et_key_locks  TYPE GTABKEY_FEATURE_LOCK_KEYS, "   
lv_enqueue_failed  TYPE GTABKEY_FEATURE_LOCK_KEYS, "   
lv_it_keys  TYPE TRWBO_T_E071K, "   
lv_e_gtabkey_res  TYPE GTABKEYERROR, "   
lv_global_key_error  TYPE GTABKEYERROR, "   
lv_is_header  TYPE TRWBO_REQUEST_HEADER, "   
lv_et_gtabkey  TYPE TR_GTABKEYS, "   
lv_iv_feature  TYPE DLVUNIT, "   
lv_iv_feature_new  TYPE DLVUNIT, "   
lv_iv_simulation  TYPE BOOLEAN, "   
lv_iv_get_duration  TYPE BOOLEAN, "   
lv_iv_test  TYPE BOOLEAN. "   

  CALL FUNCTION 'TR_FEATURE_LOCK_INTERFACE'  "lock features
    EXPORTING
         IV_MODE = lv_iv_mode
         IV_REG_WITH_OLD_LAYOUT = lv_iv_reg_with_old_layout
         IT_OBJECTS = lv_it_objects
         IT_KEYS = lv_it_keys
         IS_HEADER = lv_is_header
         IV_FEATURE = lv_iv_feature
         IV_FEATURE_NEW = lv_iv_feature_new
         IV_SIMULATION = lv_iv_simulation
         IV_GET_DURATION = lv_iv_get_duration
         IV_TEST = lv_iv_test
    IMPORTING
         ET_OBJ_LOCKS = lv_et_obj_locks
         ET_KEY_LOCKS = lv_et_key_locks
         E_GTABKEY_RES = lv_e_gtabkey_res
         ET_GTABKEY = lv_et_gtabkey
    EXCEPTIONS
        WRONG_CALL = 1
        ENQUEUE_FAILED = 2
        GLOBAL_KEY_ERROR = 3
. " TR_FEATURE_LOCK_INTERFACE




ABAP code using 7.40 inline data declarations to call FM TR_FEATURE_LOCK_INTERFACE

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!