SAP MSS_GET_TABLE_COLUMNS Function Module for
MSS_GET_TABLE_COLUMNS is a standard mss get table columns 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 mss get table columns FM, simply by entering the name MSS_GET_TABLE_COLUMNS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SFMSS_SYSCAT
Program Name: SAPLSFMSS_SYSCAT
Main Program: SAPLSFMSS_SYSCAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MSS_GET_TABLE_COLUMNS 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_COLUMNS'".
EXPORTING
TABLE_NAME = "Table name
* SCHEMA_NAME = "Schema name
* DB_NAME = "Database name
* NAMES_ONLY = "If 'X', then only the names of the coumns are returned.
TABLES
TABLE_COLS = "Table column properties
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
IMPORTING Parameters details for MSS_GET_TABLE_COLUMNS
TABLE_NAME - Table name
Data type: MSSTABLEOptional: No
Call by Reference: No ( called with pass by value option)
SCHEMA_NAME - Schema name
Data type: MSSSCHEMAOptional: Yes
Call by Reference: No ( called with pass by value option)
DB_NAME - Database name
Data type: MSSDBOptional: Yes
Call by Reference: No ( called with pass by value option)
NAMES_ONLY - If 'X', then only the names of the coumns are returned.
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MSS_GET_TABLE_COLUMNS
TABLE_COLS - Table column properties
Data type: MSSTABCOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_RUNNING_ON_MSSQL -
Data type:Optional: No
Call by Reference: Yes
DB_ERROR -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
DB_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NO_DB_ACCESS -
Data type:Optional: No
Call by Reference: Yes
SCHEMA_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
INVALID_INPUT -
Data type:Optional: No
Call by Reference: Yes
TABLE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MSS_GET_TABLE_COLUMNS 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: | ||||
| lt_table_cols | TYPE STANDARD TABLE OF MSSTABCOL, " | |||
| lv_table_name | TYPE MSSTABLE, " | |||
| lv_not_running_on_mssql | TYPE MSSTABLE, " | |||
| lv_db_error | TYPE MSSTABLE, " | |||
| lv_schema_name | TYPE MSSSCHEMA, " | |||
| lv_db_name | TYPE MSSDB, " | |||
| lv_internal_error | TYPE MSSDB, " | |||
| lv_names_only | TYPE CHAR1, " | |||
| lv_db_not_found | TYPE CHAR1, " | |||
| lv_no_db_access | TYPE CHAR1, " | |||
| lv_schema_not_found | TYPE CHAR1, " | |||
| lv_invalid_input | TYPE CHAR1, " | |||
| lv_table_not_found | TYPE CHAR1. " |
|   CALL FUNCTION 'MSS_GET_TABLE_COLUMNS' " |
| EXPORTING | ||
| TABLE_NAME | = lv_table_name | |
| SCHEMA_NAME | = lv_schema_name | |
| DB_NAME | = lv_db_name | |
| NAMES_ONLY | = lv_names_only | |
| TABLES | ||
| TABLE_COLS | = lt_table_cols | |
| 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 | ||
| . " MSS_GET_TABLE_COLUMNS | ||
ABAP code using 7.40 inline data declarations to call FM MSS_GET_TABLE_COLUMNS
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