SAP TMW_PROJECT_LOCK_MAIN Function Module for









TMW_PROJECT_LOCK_MAIN is a standard tmw project lock main SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 tmw project lock main FM, simply by entering the name TMW_PROJECT_LOCK_MAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function TMW_PROJECT_LOCK_MAIN 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 'TMW_PROJECT_LOCK_MAIN'"
  EXPORTING
*  IV_REQUEST =  "
   IV_SUPPRESS_DIALOG =  "
   IT_OBJECTS =  "
   IT_KEYS =  "
   IT_CID =  "

EXCEPTIONS
   INACTIVE = 1    INTERNAL_ERROR = 10    UNKNOWN_REQUEST = 11    CANCEL = 12    NO_OBJECTS_TRANSFERED = 2    FOREIGN_LOCK = 3    NO_RFC_CONNECTION = 4    GET_PROJECT_LOCK_KEYS_FAILED = 5    OBJECT_TYPE_NOT_ALLOWED = 6    NO_ATTRIBUTES_TRANSFERED = 7    RFC_FAILURE = 8    EXTERNAL_ERROR = 9
.



IMPORTING Parameters details for TMW_PROJECT_LOCK_MAIN

IV_REQUEST -

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

IV_SUPPRESS_DIALOG -

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

IT_OBJECTS -

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

IT_KEYS -

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

IT_CID -

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

EXCEPTIONS details

INACTIVE -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_REQUEST -

Data type:
Optional: No
Call by Reference: Yes

CANCEL -

Data type:
Optional: No
Call by Reference: Yes

NO_OBJECTS_TRANSFERED -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_CONNECTION -

Data type:
Optional: No
Call by Reference: Yes

GET_PROJECT_LOCK_KEYS_FAILED -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_TYPE_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

NO_ATTRIBUTES_TRANSFERED -

Data type:
Optional: No
Call by Reference: Yes

RFC_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

EXTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMW_PROJECT_LOCK_MAIN 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_inactive  TYPE STRING, "   
lv_iv_request  TYPE TRKORR, "   
lv_internal_error  TYPE TRKORR, "   
lv_unknown_request  TYPE TRKORR, "   
lv_cancel  TYPE TRKORR, "   
lv_iv_suppress_dialog  TYPE SYBATCH, "   
lv_no_objects_transfered  TYPE SYBATCH, "   
lv_it_objects  TYPE TR_OBJECTS, "   
lv_foreign_lock  TYPE TR_OBJECTS, "   
lv_it_keys  TYPE TR_KEYS, "   
lv_no_rfc_connection  TYPE TR_KEYS, "   
lv_it_cid  TYPE TMW_ADMS, "   
lv_get_project_lock_keys_failed  TYPE TMW_ADMS, "   
lv_object_type_not_allowed  TYPE TMW_ADMS, "   
lv_no_attributes_transfered  TYPE TMW_ADMS, "   
lv_rfc_failure  TYPE TMW_ADMS, "   
lv_external_error  TYPE TMW_ADMS. "   

  CALL FUNCTION 'TMW_PROJECT_LOCK_MAIN'  "
    EXPORTING
         IV_REQUEST = lv_iv_request
         IV_SUPPRESS_DIALOG = lv_iv_suppress_dialog
         IT_OBJECTS = lv_it_objects
         IT_KEYS = lv_it_keys
         IT_CID = lv_it_cid
    EXCEPTIONS
        INACTIVE = 1
        INTERNAL_ERROR = 10
        UNKNOWN_REQUEST = 11
        CANCEL = 12
        NO_OBJECTS_TRANSFERED = 2
        FOREIGN_LOCK = 3
        NO_RFC_CONNECTION = 4
        GET_PROJECT_LOCK_KEYS_FAILED = 5
        OBJECT_TYPE_NOT_ALLOWED = 6
        NO_ATTRIBUTES_TRANSFERED = 7
        RFC_FAILURE = 8
        EXTERNAL_ERROR = 9
. " TMW_PROJECT_LOCK_MAIN




ABAP code using 7.40 inline data declarations to call FM TMW_PROJECT_LOCK_MAIN

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!