SAP LC_GET_SINGLE_PARAMETER_DBMCLI Function Module for
LC_GET_SINGLE_PARAMETER_DBMCLI is a standard lc get single parameter dbmcli 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 lc get single parameter dbmcli FM, simply by entering the name LC_GET_SINGLE_PARAMETER_DBMCLI into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLCA
Program Name: SAPLSLCA
Main Program: SAPLSLCA
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function LC_GET_SINGLE_PARAMETER_DBMCLI 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 'LC_GET_SINGLE_PARAMETER_DBMCLI'".
EXPORTING
CON_NAME = "
PARAM_NAME = "Parameter name
* USE_DBMRFC = "
IMPORTING
PARAM_VALUE = "Parameter value
TABLES
* ACTION_PROTOCOL = "
EXCEPTIONS
NO_PERMISSION = 1 SXPG_COMMAND_EXECUTE_ERROR = 2 DBMCLI_COMMAND_EXECUTE_ERROR = 3 LC_GET_PARAM_ERROR = 4 NO_PARAM_INPUT_VALUE = 5 UNKOWN_PARAMETER = 6 EMPTY_CON_ENV = 7 DBMRFC_EXECUTE_ERROR = 8
IMPORTING Parameters details for LC_GET_SINGLE_PARAMETER_DBMCLI
CON_NAME -
Data type: DBCON-CON_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
PARAM_NAME - Parameter name
Data type: LVC_DBPARA-DESCROptional: No
Call by Reference: No ( called with pass by value option)
USE_DBMRFC -
Data type: SDB_CMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LC_GET_SINGLE_PARAMETER_DBMCLI
PARAM_VALUE - Parameter value
Data type: LVC_DBPARA-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LC_GET_SINGLE_PARAMETER_DBMCLI
ACTION_PROTOCOL -
Data type: LVC_APROTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_PERMISSION - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SXPG_COMMAND_EXECUTE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DBMCLI_COMMAND_EXECUTE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LC_GET_PARAM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PARAM_INPUT_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKOWN_PARAMETER - Unknown Parameter
Data type:Optional: No
Call by Reference: Yes
EMPTY_CON_ENV - No input in DBCON-CON_ENV
Data type:Optional: No
Call by Reference: Yes
DBMRFC_EXECUTE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LC_GET_SINGLE_PARAMETER_DBMCLI 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, " | |||
lv_param_value | TYPE LVC_DBPARA-VALUE, " | |||
lv_no_permission | TYPE LVC_DBPARA, " | |||
lt_action_protocol | TYPE STANDARD TABLE OF LVC_APROT, " | |||
lv_param_name | TYPE LVC_DBPARA-DESCR, " | |||
lv_sxpg_command_execute_error | TYPE LVC_DBPARA, " | |||
lv_use_dbmrfc | TYPE SDB_CMODE, " | |||
lv_dbmcli_command_execute_error | TYPE SDB_CMODE, " | |||
lv_lc_get_param_error | TYPE SDB_CMODE, " | |||
lv_no_param_input_value | TYPE SDB_CMODE, " | |||
lv_unkown_parameter | TYPE SDB_CMODE, " | |||
lv_empty_con_env | TYPE SDB_CMODE, " | |||
lv_dbmrfc_execute_error | TYPE SDB_CMODE. " |
  CALL FUNCTION 'LC_GET_SINGLE_PARAMETER_DBMCLI' " |
EXPORTING | ||
CON_NAME | = lv_con_name | |
PARAM_NAME | = lv_param_name | |
USE_DBMRFC | = lv_use_dbmrfc | |
IMPORTING | ||
PARAM_VALUE | = lv_param_value | |
TABLES | ||
ACTION_PROTOCOL | = lt_action_protocol | |
EXCEPTIONS | ||
NO_PERMISSION = 1 | ||
SXPG_COMMAND_EXECUTE_ERROR = 2 | ||
DBMCLI_COMMAND_EXECUTE_ERROR = 3 | ||
LC_GET_PARAM_ERROR = 4 | ||
NO_PARAM_INPUT_VALUE = 5 | ||
UNKOWN_PARAMETER = 6 | ||
EMPTY_CON_ENV = 7 | ||
DBMRFC_EXECUTE_ERROR = 8 | ||
. " LC_GET_SINGLE_PARAMETER_DBMCLI |
ABAP code using 7.40 inline data declarations to call FM LC_GET_SINGLE_PARAMETER_DBMCLI
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). | ||||
"SELECT single VALUE FROM LVC_DBPARA INTO @DATA(ld_param_value). | ||||
"SELECT single DESCR FROM LVC_DBPARA INTO @DATA(ld_param_name). | ||||
Search for further information about these or an SAP related objects