SAP TMW_PROJECT_LOCK_UPDATE Function Module for

Search SAP Function Modules

TMW_PROJECT_LOCK_UPDATE is a standard tmw project lock update 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 update FM, simply by entering the name TMW_PROJECT_LOCK_UPDATE 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): Remote-Enabled
Update:

Function TMW_PROJECT_LOCK_UPDATE 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_UPDATE'"
  EXPORTING
   IV_REQUEST =  "
*  IV_UPDATE_MODE = ' ' "
*  IV_DIALOGUE_MODE = ' ' "

 IMPORTING
   ET_TLOCKP =  "
   ET_TLOCKPC =  "
   EV_MSG_TYPE =  "

EXCEPTIONS
   INACTIVE = 1    INTERNAL_ERROR = 10    CANCEL = 11    NO_RFC_CONNECTION = 2    STRKORR_ONLY = 3    GET_PROJECT_LOCK_KEYS_FAILED = 4    NO_OBJECTS_TRANSFERED = 5    RFC_FAILURE = 6    REQUEST_OWNER_ONLY = 7    UNKNOWN_REQUEST = 8    EXTERNAL_ERROR = 9 

.

IMPORTING Parameters details for TMW_PROJECT_LOCK_UPDATE

IV_REQUEST -

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

IV_UPDATE_MODE -

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

IV_DIALOGUE_MODE -

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

EXPORTING Parameters details for TMW_PROJECT_LOCK_UPDATE

ET_TLOCKP -

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

ET_TLOCKPC -

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

EV_MSG_TYPE -

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

EXCEPTIONS details

INACTIVE -

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

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CANCEL -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_CONNECTION -

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

STRKORR_ONLY -

Data type:
Optional: No
Call by Reference: Yes

GET_PROJECT_LOCK_KEYS_FAILED -

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

NO_OBJECTS_TRANSFERED -

Data type:
Optional: No
Call by Reference: Yes

RFC_FAILURE -

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

REQUEST_OWNER_ONLY -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_REQUEST -

Data type:
Optional: No
Call by Reference: Yes

EXTERNAL_ERROR -

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

Copy and paste ABAP code example for TMW_PROJECT_LOCK_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM TMW_PROJECT_LOCK_UPDATE

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