SAP MSS_GET_TABLE_SIZE_INFO Function Module for Get size information on a table









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

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



Function MSS_GET_TABLE_SIZE_INFO 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 'MSS_GET_TABLE_SIZE_INFO'"Get  size information on a table
EXPORTING
* CON_NAME = 'DEFAULT' "DBCON name
* SCHEMA = ' ' "Target Schema
TABLE_NAME = "Table name
* SCHEMA_NAME = "Schema name
* DB_NAME = "Database name

IMPORTING
TABLE_SIZEINFO = "Table size information

EXCEPTIONS
NOT_RUNNING_ON_MSSQL = 1 DB_ERROR = 2 INTERNAL_ERROR = 3 DB_NOT_FOUND = 4 NO_DB_ACCESS = 5 SCHEMA_NOT_FOUND = 6 INVALID_INPUT = 7 TABLE_NOT_FOUND = 8 CONNECT_ERROR = 9
.



IMPORTING Parameters details for MSS_GET_TABLE_SIZE_INFO

CON_NAME - DBCON name

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

SCHEMA - Target Schema

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

TABLE_NAME - Table name

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

SCHEMA_NAME - Schema name

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

DB_NAME - Database name

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

EXPORTING Parameters details for MSS_GET_TABLE_SIZE_INFO

TABLE_SIZEINFO - Table size information

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

EXCEPTIONS details

NOT_RUNNING_ON_MSSQL -

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

DB_ERROR -

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

INTERNAL_ERROR -

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

DB_NOT_FOUND -

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

NO_DB_ACCESS -

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

SCHEMA_NOT_FOUND -

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

INVALID_INPUT -

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

TABLE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CONNECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MSS_GET_TABLE_SIZE_INFO 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_con_name  TYPE DBCON-CON_NAME, "   'DEFAULT'
lv_table_sizeinfo  TYPE MSSTABSIZEINFO, "   
lv_not_running_on_mssql  TYPE MSSTABSIZEINFO, "   
lv_schema  TYPE MSSSCHEMA, "   SPACE
lv_db_error  TYPE MSSSCHEMA, "   
lv_table_name  TYPE MSSTABLE, "   
lv_internal_error  TYPE MSSTABLE, "   
lv_schema_name  TYPE MSSSCHEMA, "   
lv_db_not_found  TYPE MSSSCHEMA, "   
lv_db_name  TYPE MSSDB, "   
lv_no_db_access  TYPE MSSDB, "   
lv_schema_not_found  TYPE MSSDB, "   
lv_invalid_input  TYPE MSSDB, "   
lv_table_not_found  TYPE MSSDB, "   
lv_connect_error  TYPE MSSDB. "   

  CALL FUNCTION 'MSS_GET_TABLE_SIZE_INFO'  "Get size information on a table
    EXPORTING
         CON_NAME = lv_con_name
         SCHEMA = lv_schema
         TABLE_NAME = lv_table_name
         SCHEMA_NAME = lv_schema_name
         DB_NAME = lv_db_name
    IMPORTING
         TABLE_SIZEINFO = lv_table_sizeinfo
    EXCEPTIONS
        NOT_RUNNING_ON_MSSQL = 1
        DB_ERROR = 2
        INTERNAL_ERROR = 3
        DB_NOT_FOUND = 4
        NO_DB_ACCESS = 5
        SCHEMA_NOT_FOUND = 6
        INVALID_INPUT = 7
        TABLE_NOT_FOUND = 8
        CONNECT_ERROR = 9
. " MSS_GET_TABLE_SIZE_INFO




ABAP code using 7.40 inline data declarations to call FM MSS_GET_TABLE_SIZE_INFO

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 CON_NAME FROM DBCON INTO @DATA(ld_con_name).
DATA(ld_con_name) = 'DEFAULT'.
 
 
 
DATA(ld_schema) = ' '.
 
 
 
 
 
 
 
 
 
 
 
 


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!