SAP CFG_API_GET_KNOWLEDGEBASE Function Module for Returns additional information for a knowledgebase









CFG_API_GET_KNOWLEDGEBASE is a standard cfg api get knowledgebase SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns additional information for a knowledgebase 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 cfg api get knowledgebase FM, simply by entering the name CFG_API_GET_KNOWLEDGEBASE into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_CFG_API_ENGINE_COMMAND
Program Name: SAPLCOM_CFG_API_ENGINE_COMMAND
Main Program: SAPLCOM_CFG_API_ENGINE_COMMAND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled JAVA Module
Update:



Function CFG_API_GET_KNOWLEDGEBASE 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 'CFG_API_GET_KNOWLEDGEBASE'"Returns additional information for a knowledgebase
  EXPORTING
*  KB_LOGSYS =  "Logical System
*  KB_NAME =  "KB Name
*  KB_VERSION =  "KB Version
*  KB_PROFILE =  "Profile name
*  KB_ID =  "Internal identifier of a knowledge base

 IMPORTING
   KB_USER_DESIGN =  "User Interface Name
   KB_DESIGNS =  "Table of ui names of knowledge bases

EXCEPTIONS
   KNOWLEDGEBASE_NOT_FOUND = 1    PARAMETER_EXCEPTION = 2    COMMAND_EXCEPTION = 3
.



IMPORTING Parameters details for CFG_API_GET_KNOWLEDGEBASE

KB_LOGSYS - Logical System

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

KB_NAME - KB Name

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

KB_VERSION - KB Version

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

KB_PROFILE - Profile name

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

KB_ID - Internal identifier of a knowledge base

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

EXPORTING Parameters details for CFG_API_GET_KNOWLEDGEBASE

KB_USER_DESIGN - User Interface Name

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

KB_DESIGNS - Table of ui names of knowledge bases

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

EXCEPTIONS details

KNOWLEDGEBASE_NOT_FOUND - Knowledgebase for given input parameters not found

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_EXCEPTION - Problem in using an import parameter

Data type:
Optional: No
Call by Reference: Yes

COMMAND_EXCEPTION - Problem in executing the configuration command

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CFG_API_GET_KNOWLEDGEBASE 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_kb_logsys  TYPE COMT_CFGD_KBLOGSYS, "   
lv_kb_user_design  TYPE COMT_CFGD_UINAME, "   
lv_knowledgebase_not_found  TYPE COMT_CFGD_UINAME, "   
lv_kb_name  TYPE COMT_CFGD_KBNAME, "   
lv_kb_designs  TYPE COMT_CFGM_UINAME_I, "   
lv_parameter_exception  TYPE COMT_CFGM_UINAME_I, "   
lv_kb_version  TYPE COMT_CFGD_KBVERSION, "   
lv_command_exception  TYPE COMT_CFGD_KBVERSION, "   
lv_kb_profile  TYPE COMT_CFGD_PROFNAME, "   
lv_kb_id  TYPE COMT_CFGD_KBID. "   

  CALL FUNCTION 'CFG_API_GET_KNOWLEDGEBASE'  "Returns additional information for a knowledgebase
    EXPORTING
         KB_LOGSYS = lv_kb_logsys
         KB_NAME = lv_kb_name
         KB_VERSION = lv_kb_version
         KB_PROFILE = lv_kb_profile
         KB_ID = lv_kb_id
    IMPORTING
         KB_USER_DESIGN = lv_kb_user_design
         KB_DESIGNS = lv_kb_designs
    EXCEPTIONS
        KNOWLEDGEBASE_NOT_FOUND = 1
        PARAMETER_EXCEPTION = 2
        COMMAND_EXCEPTION = 3
. " CFG_API_GET_KNOWLEDGEBASE




ABAP code using 7.40 inline data declarations to call FM CFG_API_GET_KNOWLEDGEBASE

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



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!