SAP Function Modules

LC_CHECK_UPDATE_POSSIBLE SAP Function module







LC_CHECK_UPDATE_POSSIBLE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LC_CHECK_UPDATE_POSSIBLE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SLCB
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM LC_CHECK_UPDATE_POSSIBLE - LC CHECK UPDATE POSSIBLE





CALL FUNCTION 'LC_CHECK_UPDATE_POSSIBLE' "
  EXPORTING
    con_name =                  " dbcon-con_name  Logical Name for a Database Connection
  IMPORTING
    lc_enable =                 " i             liveCache: Parameter value in SHOW_STAT_STATE
  EXCEPTIONS
    NO_CONNECTION = 1           "               No link to liveCache
    NO_ENTRY_FOUND = 2          "
    TABLE_NOT_FOUND = 3         "
    UNKNOWN_KERNEL_VERSION = 4  "
    KERNEL_VERSION_NOT_SUPPORTED = 5  "
    .  "  LC_CHECK_UPDATE_POSSIBLE

ABAP code example for Function Module LC_CHECK_UPDATE_POSSIBLE





The ABAP code below is a full code listing to execute function module LC_CHECK_UPDATE_POSSIBLE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_lc_enable  TYPE I .


SELECT single CON_NAME
FROM DBCON
INTO @DATA(ld_con_name).
. CALL FUNCTION 'LC_CHECK_UPDATE_POSSIBLE' EXPORTING con_name = ld_con_name IMPORTING lc_enable = ld_lc_enable EXCEPTIONS NO_CONNECTION = 1 NO_ENTRY_FOUND = 2 TABLE_NOT_FOUND = 3 UNKNOWN_KERNEL_VERSION = 4 KERNEL_VERSION_NOT_SUPPORTED = 5 . " LC_CHECK_UPDATE_POSSIBLE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_lc_enable  TYPE I ,
ld_con_name  TYPE DBCON-CON_NAME .


SELECT single CON_NAME
FROM DBCON
INTO ld_con_name.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LC_CHECK_UPDATE_POSSIBLE or its description.