SAP GET_CONFIGPARAMS_MSQ Function Module for MS SQL server function to get configuration options









GET_CONFIGPARAMS_MSQ is a standard get configparams msq SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MS SQL server function to get configuration options 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 configparams msq FM, simply by entering the name GET_CONFIGPARAMS_MSQ into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_CONFIGPARAMS_MSQ 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_CONFIGPARAMS_MSQ'"MS SQL server function to get configuration options
EXPORTING
* CON_NAME = 'DEFAULT' "Logical name for a database connection
* SCHEMA = ' ' "Schema name

TABLES
CONFIGVAL = "

EXCEPTIONS
INTERNAL_ERROR = 1 DB_ERROR = 2 CONNECT_ERROR = 3
.



IMPORTING Parameters details for GET_CONFIGPARAMS_MSQ

CON_NAME - Logical name for a database connection

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

SCHEMA - Schema name

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

TABLES Parameters details for GET_CONFIGPARAMS_MSQ

CONFIGVAL -

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

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DB_ERROR -

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_CONFIGPARAMS_MSQ 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_configval  TYPE STANDARD TABLE OF MSQCONFPAR, "   
lv_internal_error  TYPE MSQCONFPAR, "   
lv_schema  TYPE MSSSCHEMA, "   ' '
lv_db_error  TYPE MSSSCHEMA, "   
lv_connect_error  TYPE MSSSCHEMA. "   

  CALL FUNCTION 'GET_CONFIGPARAMS_MSQ'  "MS SQL server function to get configuration options
    EXPORTING
         CON_NAME = lv_con_name
         SCHEMA = lv_schema
    TABLES
         CONFIGVAL = lt_configval
    EXCEPTIONS
        INTERNAL_ERROR = 1
        DB_ERROR = 2
        CONNECT_ERROR = 3
. " GET_CONFIGPARAMS_MSQ




ABAP code using 7.40 inline data declarations to call FM GET_CONFIGPARAMS_MSQ

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!