SAP DB_TABLE_SET_LOCK Function Module for









DB_TABLE_SET_LOCK is a standard db table set lock 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 db table set lock FM, simply by entering the name DB_TABLE_SET_LOCK into the relevant SAP transaction such as SE37 or SE38.

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



Function DB_TABLE_SET_LOCK 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 'DB_TABLE_SET_LOCK'"
  EXPORTING
*  DBSYS = SY-DBSYS "DBS for which program is generated
*  NO_EXEC = ' ' "X: Do not execute generated program
*  PRID = 0 "
*  PROGNAME = ' ' "Name of gen. program
*  TABNAME = ' ' "Name of table
*  MAX_SEVERITY = 'E' "

 IMPORTING
   GENPROG =  "Actual name of the generated program
   SUBRC =  "

TABLES
*  STATEMENTS =  "Table of the generated statements

EXCEPTIONS
   ILLEGAL_VALUE = 1
.



IMPORTING Parameters details for DB_TABLE_SET_LOCK

DBSYS - DBS for which program is generated

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

NO_EXEC - X: Do not execute generated program

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

PRID -

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

PROGNAME - Name of gen. program

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

TABNAME - Name of table

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

MAX_SEVERITY -

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

EXPORTING Parameters details for DB_TABLE_SET_LOCK

GENPROG - Actual name of the generated program

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

SUBRC -

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

TABLES Parameters details for DB_TABLE_SET_LOCK

STATEMENTS - Table of the generated statements

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

EXCEPTIONS details

ILLEGAL_VALUE -

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

Copy and paste ABAP code example for DB_TABLE_SET_LOCK 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_dbsys  TYPE SY-DBSYS, "   SY-DBSYS
lv_genprog  TYPE TRDIR-NAME, "   
lt_statements  TYPE STANDARD TABLE OF TRDIR, "   
lv_illegal_value  TYPE TRDIR, "   
lv_subrc  TYPE SY-SUBRC, "   
lv_no_exec  TYPE DDREFSTRUC-BOOL, "   SPACE
lv_prid  TYPE SY-TABIX, "   0
lv_progname  TYPE TRDIR-NAME, "   SPACE
lv_tabname  TYPE DDREFSTRUC-SYMBOL, "   SPACE
lv_max_severity  TYPE DDREFSTRUC. "   'E'

  CALL FUNCTION 'DB_TABLE_SET_LOCK'  "
    EXPORTING
         DBSYS = lv_dbsys
         NO_EXEC = lv_no_exec
         PRID = lv_prid
         PROGNAME = lv_progname
         TABNAME = lv_tabname
         MAX_SEVERITY = lv_max_severity
    IMPORTING
         GENPROG = lv_genprog
         SUBRC = lv_subrc
    TABLES
         STATEMENTS = lt_statements
    EXCEPTIONS
        ILLEGAL_VALUE = 1
. " DB_TABLE_SET_LOCK




ABAP code using 7.40 inline data declarations to call FM DB_TABLE_SET_LOCK

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.

"SELECT single DBSYS FROM SY INTO @DATA(ld_dbsys).
DATA(ld_dbsys) = SY-DBSYS.
 
"SELECT single NAME FROM TRDIR INTO @DATA(ld_genprog).
 
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_subrc).
 
"SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_no_exec).
DATA(ld_no_exec) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_prid).
 
"SELECT single NAME FROM TRDIR INTO @DATA(ld_progname).
DATA(ld_progname) = ' '.
 
"SELECT single SYMBOL FROM DDREFSTRUC INTO @DATA(ld_tabname).
DATA(ld_tabname) = ' '.
 
DATA(ld_max_severity) = 'E'.
 


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!