SAP GET_LOCKINFO_MSS Function Module for retrieve blocking/locking data

Search SAP Function Modules

GET_LOCKINFO_MSS is a standard get lockinfo mss SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for retrieve blocking/locking data 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 get lockinfo mss FM, simply by entering the name GET_LOCKINFO_MSS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SMSSDATA1
Program Name: SAPLSMSSDATA1
Main Program: SAPLSMSSDATA1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GET_LOCKINFO_MSS 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 'GET_LOCKINFO_MSS'"retrieve blocking/locking data
  EXPORTING
*  CON_NAME =  "Logical name for a database connection
*  SCHEMA = ' ' "Schema name
*  LIGHTWEIGHT = 0 "0 - normal, 1 - sm66
*  SAVEDDATA = 0 "0 - real time, 1-table sap_dblocks

TABLES
*  LOCKINFO =  "MS sql server lock info information for blockers and waiters
*  LOCKINFO_SNAP =  "DB Locks snapshot - includes handles

EXCEPTIONS
   DB_ERROR = 1    NOT_RUNNING_ON_MSSQL = 2    CONNECT_ERROR = 3    INTERNAL_ERROR = 4 

.

IMPORTING Parameters details for GET_LOCKINFO_MSS

CON_NAME - Logical name for a database connection

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

SCHEMA - Schema name

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

LIGHTWEIGHT - 0 - normal, 1 - sm66

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

SAVEDDATA - 0 - real time, 1-table sap_dblocks

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

TABLES Parameters details for GET_LOCKINFO_MSS

LOCKINFO - MS sql server lock info information for blockers and waiters

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

LOCKINFO_SNAP - DB Locks snapshot - includes handles

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

EXCEPTIONS details

DB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_RUNNING_ON_MSSQL -

Data type:
Optional: No
Call by Reference: Yes

CONNECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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