SAP DB_SET_TABLE_PARAMETER Function Module for









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

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



Function DB_SET_TABLE_PARAMETER 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_SET_TABLE_PARAMETER'"
EXPORTING
* DBSYS = SY-DBSYS "
* DD02DBS = ' ' "
* REF_TABLE = ' ' "Reference table whose parameters are copied
SOURCE = "
* TABART = ' ' "
* TABKAT = ' ' "
TABNAME = "
* USEFLAG = ' ' "

EXCEPTIONS
NOT_SET = 1 UNCOMPLETE_PARAMETER = 2 MISSING_DATA_CLASS = 3 MISSING_SIZE_CATEGORY = 4
.



IMPORTING Parameters details for DB_SET_TABLE_PARAMETER

DBSYS -

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

DD02DBS -

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

REF_TABLE - Reference table whose parameters are copied

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

SOURCE -

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

TABART -

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

TABKAT -

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

TABNAME -

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

USEFLAG -

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

EXCEPTIONS details

NOT_SET -

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

UNCOMPLETE_PARAMETER - ref_table or table type and table category must exist

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

MISSING_DATA_CLASS -

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

MISSING_SIZE_CATEGORY -

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

Copy and paste ABAP code example for DB_SET_TABLE_PARAMETER 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_not_set  TYPE SY, "   
lv_dd02dbs  TYPE SY, "   SPACE
lv_uncomplete_parameter  TYPE SY, "   
lv_ref_table  TYPE RSX02DB-TABNAME, "   SPACE
lv_missing_data_class  TYPE RSX02DB, "   
lv_source  TYPE RSX02DB-SOURCE, "   
lv_missing_size_category  TYPE RSX02DB, "   
lv_tabart  TYPE DD09V-TABART, "   SPACE
lv_tabkat  TYPE DD09V-TABKAT, "   SPACE
lv_tabname  TYPE RSX02DB-TABNAME, "   
lv_useflag  TYPE RSX02DB-USEFLAG. "   SPACE

  CALL FUNCTION 'DB_SET_TABLE_PARAMETER'  "
    EXPORTING
         DBSYS = lv_dbsys
         DD02DBS = lv_dd02dbs
         REF_TABLE = lv_ref_table
         SOURCE = lv_source
         TABART = lv_tabart
         TABKAT = lv_tabkat
         TABNAME = lv_tabname
         USEFLAG = lv_useflag
    EXCEPTIONS
        NOT_SET = 1
        UNCOMPLETE_PARAMETER = 2
        MISSING_DATA_CLASS = 3
        MISSING_SIZE_CATEGORY = 4
. " DB_SET_TABLE_PARAMETER




ABAP code using 7.40 inline data declarations to call FM DB_SET_TABLE_PARAMETER

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.
 
 
DATA(ld_dd02dbs) = ' '.
 
 
"SELECT single TABNAME FROM RSX02DB INTO @DATA(ld_ref_table).
DATA(ld_ref_table) = ' '.
 
 
"SELECT single SOURCE FROM RSX02DB INTO @DATA(ld_source).
 
 
"SELECT single TABART FROM DD09V INTO @DATA(ld_tabart).
DATA(ld_tabart) = ' '.
 
"SELECT single TABKAT FROM DD09V INTO @DATA(ld_tabkat).
DATA(ld_tabkat) = ' '.
 
"SELECT single TABNAME FROM RSX02DB INTO @DATA(ld_tabname).
 
"SELECT single USEFLAG FROM RSX02DB INTO @DATA(ld_useflag).
DATA(ld_useflag) = ' '.
 


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!