SAP GET_STATICSERVER_MSS Function Module for get data on the Server and SQL Server system is on
GET_STATICSERVER_MSS is a standard get staticserver 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 Server and SQL Server system is on 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 staticserver mss FM, simply by entering the name GET_STATICSERVER_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_STATICSERVER_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_STATICSERVER_MSS'"get data on the Server and SQL Server system is on.
EXPORTING
* CON_NAME = 'DEFAULT' "Logical name for a database connection
* SCHEMA = ' ' "Schema name
TABLES
SERVERDATA = "Data about operating system files which make up a db
EXCEPTIONS
INTERNAL_ERROR = 1 DB_ERROR = 2 NOT_RUNNING_ON_MSSQL = 3 CONNECT_ERROR = 4
IMPORTING Parameters details for GET_STATICSERVER_MSS
CON_NAME - Logical name for a database connection
Data type: DBCON-CON_NAMEDefault: 'DEFAULT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SCHEMA - Schema name
Data type: MSSSCHEMADefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GET_STATICSERVER_MSS
SERVERDATA - Data about operating system files which make up a db
Data type: MSS_STSERVOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
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)
NOT_RUNNING_ON_MSSQL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONNECT_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_STATICSERVER_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: | ||||
| lv_con_name | TYPE DBCON-CON_NAME, " 'DEFAULT' | |||
| lt_serverdata | TYPE STANDARD TABLE OF MSS_STSERV, " | |||
| lv_internal_error | TYPE MSS_STSERV, " | |||
| lv_schema | TYPE MSSSCHEMA, " ' ' | |||
| lv_db_error | TYPE MSSSCHEMA, " | |||
| lv_not_running_on_mssql | TYPE MSSSCHEMA, " | |||
| lv_connect_error | TYPE MSSSCHEMA. " |
|   CALL FUNCTION 'GET_STATICSERVER_MSS' "get data on the Server and SQL Server system is on |
| EXPORTING | ||
| CON_NAME | = lv_con_name | |
| SCHEMA | = lv_schema | |
| TABLES | ||
| SERVERDATA | = lt_serverdata | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| DB_ERROR = 2 | ||
| NOT_RUNNING_ON_MSSQL = 3 | ||
| CONNECT_ERROR = 4 | ||
| . " GET_STATICSERVER_MSS | ||
ABAP code using 7.40 inline data declarations to call FM GET_STATICSERVER_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) | = ' '. | |||
Search for further information about these or an SAP related objects