SAP LC_GET_CONFIG_LOG_DBMCLI Function Module for

Search SAP Function Modules

LC_GET_CONFIG_LOG_DBMCLI is a standard lc get config log 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 config log dbmcli FM, simply by entering the name LC_GET_CONFIG_LOG_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_CONFIG_LOG_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_CONFIG_LOG_DBMCLI'"
  EXPORTING
   CON_NAME =  "
*  USE_DBMRFC =  "

 IMPORTING
   LOG_MODE =  "Name of devspace
   USED_LOGPAGES =  "Devspace size
   USED_LOGDEVS =  "
   MAX_LOGDEVS =  "

TABLES
   LOG_CONFIG =  "
   ACTION_PROTOCOL =  "Structure for Action Log for LiveCache Administration

EXCEPTIONS
   NO_PERMISSION = 1    SXPG_COMMAND_EXECUTE_ERROR = 2    DBMCLI_COMMAND_EXECUTE_ERROR = 3    LC_GET_CONFIG_LOG_ERROR = 4    EMPTY_CON_ENV = 5    DBMRFC_EXECUTE_ERROR = 6 

.

IMPORTING Parameters details for LC_GET_CONFIG_LOG_DBMCLI

CON_NAME -

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

USE_DBMRFC -

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

EXPORTING Parameters details for LC_GET_CONFIG_LOG_DBMCLI

LOG_MODE - Name of devspace

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

USED_LOGPAGES - Devspace size

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

USED_LOGDEVS -

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

MAX_LOGDEVS -

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

TABLES Parameters details for LC_GET_CONFIG_LOG_DBMCLI

LOG_CONFIG -

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

ACTION_PROTOCOL - Structure for Action Log for LiveCache Administration

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

EXCEPTIONS details

NO_PERMISSION -

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_CONFIG_LOG_ERROR - No configuration data existing

Data type:
Optional: No
Call by Reference: Yes

EMPTY_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_CONFIG_LOG_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.

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

Search for further information about these or an SAP related objects