SAP CUXA_ANALYZE_RUNTIME_KB Function Module for NOTRANSL: Analyse SCE KB Laufzeitversion









CUXA_ANALYZE_RUNTIME_KB is a standard cuxa analyze runtime kb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Analyse SCE KB Laufzeitversion 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 cuxa analyze runtime kb FM, simply by entering the name CUXA_ANALYZE_RUNTIME_KB into the relevant SAP transaction such as SE37 or SE38.

Function Group: CUXA
Program Name: SAPLCUXA
Main Program: SAPLCUXA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CUXA_ANALYZE_RUNTIME_KB 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 'CUXA_ANALYZE_RUNTIME_KB'"NOTRANSL: Analyse SCE KB Laufzeitversion
  EXPORTING
   I_KB =  "Runtime Version of SCE Knowledge Base
*  I_ALLOW_DIALOGS = 'X' "Single-character Indicator
*  I_WITH_STATISTICS = 'X' "Single-character Indicator
*  I_WITH_CLASSES = 'X' "Single-character Indicator
*  I_WITH_BOM = 'X' "Single-character Indicator
*  I_WITH_DEPENDENCIES = 'X' "Single-character Indicator
*  I_WITH_VARIANT_TABS = 'X' "Single-character Indicator
*  I_WITH_VARIANT_FUNS = 'X' "Single-character Indicator
*  I_TRACE_LEVEL = '0' "Level of Detail of Trace Display
   I_APPL_LOG_HANDLE =  "Application Log: Log Handle

 IMPORTING
   E_RESULT =  "

TABLES
*  ET_MESSAGES =  "Analysis Results

EXCEPTIONS
   INTERNAL_ERROR = 1    NOT_FOUND = 2
.



IMPORTING Parameters details for CUXA_ANALYZE_RUNTIME_KB

I_KB - Runtime Version of SCE Knowledge Base

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

I_ALLOW_DIALOGS - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_STATISTICS - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_CLASSES - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_BOM - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_DEPENDENCIES - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_VARIANT_TABS - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_WITH_VARIANT_FUNS - Single-character Indicator

Data type: CHAR1
Default: 'X'
Optional: No
Call by Reference: Yes

I_TRACE_LEVEL - Level of Detail of Trace Display

Data type: RCUTC-LEVEL
Default: '0'
Optional: No
Call by Reference: Yes

I_APPL_LOG_HANDLE - Application Log: Log Handle

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

EXPORTING Parameters details for CUXA_ANALYZE_RUNTIME_KB

E_RESULT -

Data type: SY-MSGTY
Optional: No
Call by Reference: Yes

TABLES Parameters details for CUXA_ANALYZE_RUNTIME_KB

ET_MESSAGES - Analysis Results

Data type: BAPIRET2_T
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR - Internal error

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUXA_ANALYZE_RUNTIME_KB 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_i_kb  TYPE SCEKB, "   
lv_e_result  TYPE SY-MSGTY, "   
lt_et_messages  TYPE STANDARD TABLE OF BAPIRET2_T, "   
lv_internal_error  TYPE BAPIRET2_T, "   
lv_i_allow_dialogs  TYPE CHAR1, "   'X'
lv_not_found  TYPE CHAR1, "   
lv_i_with_statistics  TYPE CHAR1, "   'X'
lv_i_with_classes  TYPE CHAR1, "   'X'
lv_i_with_bom  TYPE CHAR1, "   'X'
lv_i_with_dependencies  TYPE CHAR1, "   'X'
lv_i_with_variant_tabs  TYPE CHAR1, "   'X'
lv_i_with_variant_funs  TYPE CHAR1, "   'X'
lv_i_trace_level  TYPE RCUTC-LEVEL, "   '0'
lv_i_appl_log_handle  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'CUXA_ANALYZE_RUNTIME_KB'  "NOTRANSL: Analyse SCE KB Laufzeitversion
    EXPORTING
         I_KB = lv_i_kb
         I_ALLOW_DIALOGS = lv_i_allow_dialogs
         I_WITH_STATISTICS = lv_i_with_statistics
         I_WITH_CLASSES = lv_i_with_classes
         I_WITH_BOM = lv_i_with_bom
         I_WITH_DEPENDENCIES = lv_i_with_dependencies
         I_WITH_VARIANT_TABS = lv_i_with_variant_tabs
         I_WITH_VARIANT_FUNS = lv_i_with_variant_funs
         I_TRACE_LEVEL = lv_i_trace_level
         I_APPL_LOG_HANDLE = lv_i_appl_log_handle
    IMPORTING
         E_RESULT = lv_e_result
    TABLES
         ET_MESSAGES = lt_et_messages
    EXCEPTIONS
        INTERNAL_ERROR = 1
        NOT_FOUND = 2
. " CUXA_ANALYZE_RUNTIME_KB




ABAP code using 7.40 inline data declarations to call FM CUXA_ANALYZE_RUNTIME_KB

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 MSGTY FROM SY INTO @DATA(ld_e_result).
 
 
 
DATA(ld_i_allow_dialogs) = 'X'.
 
 
DATA(ld_i_with_statistics) = 'X'.
 
DATA(ld_i_with_classes) = 'X'.
 
DATA(ld_i_with_bom) = 'X'.
 
DATA(ld_i_with_dependencies) = 'X'.
 
DATA(ld_i_with_variant_tabs) = 'X'.
 
DATA(ld_i_with_variant_funs) = 'X'.
 
"SELECT single LEVEL FROM RCUTC INTO @DATA(ld_i_trace_level).
DATA(ld_i_trace_level) = '0'.
 
 


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!