SAP GET_SQLFILES_MSS Function Module for get data on the files of a SQL Server database









GET_SQLFILES_MSS is a standard get sqlfiles 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 get data on the files of a SQL Server database 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 sqlfiles mss FM, simply by entering the name GET_SQLFILES_MSS 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 GET_SQLFILES_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_SQLFILES_MSS'"get data on the files of a SQL Server database
EXPORTING
* CON_NAME = 'DEFAULT' "DBCON name
* SCHEMA = ' ' "Target Schema
* DBNAME = "Database name

TABLES
DBFILES = "Data about operating system files which make up a db

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



IMPORTING Parameters details for GET_SQLFILES_MSS

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)

DBNAME - Database name

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

TABLES Parameters details for GET_SQLFILES_MSS

DBFILES - Data about operating system files which make up a db

Data type: MSQ_FILES
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DB_ERROR -

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

NOT_RUNNING_ON_MSSQL -

Data type:
Optional: No
Call by Reference: Yes

DB_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 GET_SQLFILES_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.

DATA:
lt_dbfiles  TYPE STANDARD TABLE OF MSQ_FILES, "   
lv_con_name  TYPE DBCON-CON_NAME, "   'DEFAULT'
lv_internal_error  TYPE DBCON, "   
lv_schema  TYPE MSSSCHEMA, "   SPACE
lv_db_error  TYPE MSSSCHEMA, "   
lv_dbname  TYPE MSS_DBDATA-DBNAME, "   
lv_no_db_access  TYPE MSS_DBDATA, "   
lv_schema_not_found  TYPE MSS_DBDATA, "   
lv_not_running_on_mssql  TYPE MSS_DBDATA, "   
lv_db_not_found  TYPE MSS_DBDATA, "   
lv_connect_error  TYPE MSS_DBDATA. "   

  CALL FUNCTION 'GET_SQLFILES_MSS'  "get data on the files of a SQL Server database
    EXPORTING
         CON_NAME = lv_con_name
         SCHEMA = lv_schema
         DBNAME = lv_dbname
    TABLES
         DBFILES = lt_dbfiles
    EXCEPTIONS
        INTERNAL_ERROR = 1
        DB_ERROR = 2
        NO_DB_ACCESS = 3
        SCHEMA_NOT_FOUND = 4
        NOT_RUNNING_ON_MSSQL = 5
        DB_NOT_FOUND = 6
        CONNECT_ERROR = 7
. " GET_SQLFILES_MSS




ABAP code using 7.40 inline data declarations to call FM GET_SQLFILES_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.

 
"SELECT single CON_NAME FROM DBCON INTO @DATA(ld_con_name).
DATA(ld_con_name) = 'DEFAULT'.
 
 
DATA(ld_schema) = ' '.
 
 
"SELECT single DBNAME FROM MSS_DBDATA INTO @DATA(ld_dbname).
 
 
 
 
 
 


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!