SAP CUD0_DISPLAY_KNOWLEDGE Function Module for NOTRANSL: Anzeige von Wissensdaten









CUD0_DISPLAY_KNOWLEDGE is a standard cud0 display knowledge 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: Anzeige von Wissensdaten 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 cud0 display knowledge FM, simply by entering the name CUD0_DISPLAY_KNOWLEDGE into the relevant SAP transaction such as SE37 or SE38.

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



Function CUD0_DISPLAY_KNOWLEDGE 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 'CUD0_DISPLAY_KNOWLEDGE'"NOTRANSL: Anzeige von Wissensdaten
  EXPORTING
*  KEY = ' ' "Key for reading a data record
*  LANGUAGE = SY-LANGU "Language key
*  OBJECT = ' ' "DDIC structure of OBJECTID
*  OBJECTID = ' ' "Object to be configured
   DATE =  "
*  CLINT =  "
*  ATINN =  "

EXCEPTIONS
   EITHER_KEY_OR_OBJECT = 1    NO_KNOWLEDGE = 2    NO_VALID_OBJECT = 3    OBJECT_NOT_INTEGRATED = 4
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCUD0_001 Configuration Decision to Load Configuration from External Source
EXIT_SAPLCUD0_002 Reaction Option to Conflicts When Finding Objects in Class Node
EXIT_SAPLCUD0_003 Time of Initialization for Variant Function Program Environment

IMPORTING Parameters details for CUD0_DISPLAY_KNOWLEDGE

KEY - Key for reading a data record

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

LANGUAGE - Language key

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT - DDIC structure of OBJECTID

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

OBJECTID - Object to be configured

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

DATE -

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

CLINT -

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

ATINN -

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

EXCEPTIONS details

EITHER_KEY_OR_OBJECT - Both a work area and a key entered

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

NO_KNOWLEDGE - No object dependency available

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

NO_VALID_OBJECT - Specified object not found

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

OBJECT_NOT_INTEGRATED - Specified object is not yet supported

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

Copy and paste ABAP code example for CUD0_DISPLAY_KNOWLEDGE 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_key  TYPE STRING, "   SPACE
lv_either_key_or_object  TYPE STRING, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_no_knowledge  TYPE SY, "   
lv_object  TYPE SY, "   SPACE
lv_no_valid_object  TYPE SY, "   
lv_objectid  TYPE SY, "   SPACE
lv_object_not_integrated  TYPE SY, "   
lv_date  TYPE SY-DATUM, "   
lv_clint  TYPE KLAH-CLINT, "   
lv_atinn  TYPE CABN-ATINN. "   

  CALL FUNCTION 'CUD0_DISPLAY_KNOWLEDGE'  "NOTRANSL: Anzeige von Wissensdaten
    EXPORTING
         KEY = lv_key
         LANGUAGE = lv_language
         OBJECT = lv_object
         OBJECTID = lv_objectid
         DATE = lv_date
         CLINT = lv_clint
         ATINN = lv_atinn
    EXCEPTIONS
        EITHER_KEY_OR_OBJECT = 1
        NO_KNOWLEDGE = 2
        NO_VALID_OBJECT = 3
        OBJECT_NOT_INTEGRATED = 4
. " CUD0_DISPLAY_KNOWLEDGE




ABAP code using 7.40 inline data declarations to call FM CUD0_DISPLAY_KNOWLEDGE

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_key) = ' '.
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
DATA(ld_object) = ' '.
 
 
DATA(ld_objectid) = ' '.
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date).
 
"SELECT single CLINT FROM KLAH INTO @DATA(ld_clint).
 
"SELECT single ATINN FROM CABN INTO @DATA(ld_atinn).
 


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!