SAP IPC_FIND_KNOWLEDGEBASES Function Module for findKnowledgebases (IPC Kommando)









IPC_FIND_KNOWLEDGEBASES is a standard ipc find knowledgebases SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for findKnowledgebases (IPC Kommando) 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 ipc find knowledgebases FM, simply by entering the name IPC_FIND_KNOWLEDGEBASES into the relevant SAP transaction such as SE37 or SE38.

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



Function IPC_FIND_KNOWLEDGEBASES 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 'IPC_FIND_KNOWLEDGEBASES'"findKnowledgebases (IPC Kommando)
EXPORTING
IV_OBJECT_ID = "Name des Objekts
IV_OBJECT_TYPE = "Objekttyp
IV_OBJECT_LOGSYS = "Logisches System
IV_DATE = "
* IV_USAGE = "
* IV_ORGTYPE = "
* IV_ORGID = "
* IV_STATUS = "Freigegeben (2), initial = alle Status
* IV_WITH_KB_PROFILES = 'T' "Boolean (T=True, F=False)

IMPORTING
ET_KB_HEADERS = "Enthält Kopfinformation einer SCE Wissensbasis

EXCEPTIONS
KNOWLEDGEBASE_NOT_FOUND = 1
.



IMPORTING Parameters details for IPC_FIND_KNOWLEDGEBASES

IV_OBJECT_ID - Name des Objekts

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

IV_OBJECT_TYPE - Objekttyp

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

IV_OBJECT_LOGSYS - Logisches System

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

IV_DATE -

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

IV_USAGE -

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

IV_ORGTYPE -

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

IV_ORGID -

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

IV_STATUS - Freigegeben (2), initial = alle Status

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

IV_WITH_KB_PROFILES - Boolean (T=True, F=False)

Data type: COMT_CFGM_BOOLEAN
Default: 'T'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for IPC_FIND_KNOWLEDGEBASES

ET_KB_HEADERS - Enthält Kopfinformation einer SCE Wissensbasis

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

EXCEPTIONS details

KNOWLEDGEBASE_NOT_FOUND - Wissensbasis konnte nicht bestimmt werden

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IPC_FIND_KNOWLEDGEBASES 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_iv_object_id  TYPE COMT_IPC_OBJECT_ID, "   
lv_et_kb_headers  TYPE COMT_CFG_KB_HEADER_TAB, "   
lv_knowledgebase_not_found  TYPE COMT_CFG_KB_HEADER_TAB, "   
lv_iv_object_type  TYPE COMT_PRODUCT_TYPE, "   
lv_iv_object_logsys  TYPE LOGSYS, "   
lv_iv_date  TYPE COMT_CFGD_KBDATE, "   
lv_iv_usage  TYPE COMT_CFGD_USAGE, "   
lv_iv_orgtype  TYPE COMT_CFGD_ORGTYPE, "   
lv_iv_orgid  TYPE COMT_CFGD_ORGID, "   
lv_iv_status  TYPE COMT_CFGD_STATUSID, "   
lv_iv_with_kb_profiles  TYPE COMT_CFGM_BOOLEAN. "   'T'

  CALL FUNCTION 'IPC_FIND_KNOWLEDGEBASES'  "findKnowledgebases (IPC Kommando)
    EXPORTING
         IV_OBJECT_ID = lv_iv_object_id
         IV_OBJECT_TYPE = lv_iv_object_type
         IV_OBJECT_LOGSYS = lv_iv_object_logsys
         IV_DATE = lv_iv_date
         IV_USAGE = lv_iv_usage
         IV_ORGTYPE = lv_iv_orgtype
         IV_ORGID = lv_iv_orgid
         IV_STATUS = lv_iv_status
         IV_WITH_KB_PROFILES = lv_iv_with_kb_profiles
    IMPORTING
         ET_KB_HEADERS = lv_et_kb_headers
    EXCEPTIONS
        KNOWLEDGEBASE_NOT_FOUND = 1
. " IPC_FIND_KNOWLEDGEBASES




ABAP code using 7.40 inline data declarations to call FM IPC_FIND_KNOWLEDGEBASES

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.

 
 
 
 
 
 
 
 
 
 
DATA(ld_iv_with_kb_profiles) = 'T'.
 


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!