SAP Function Modules

RKC_GET_OBJECT_DESCRIPTION SAP Function module







RKC_GET_OBJECT_DESCRIPTION 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 RKC_GET_OBJECT_DESCRIPTION into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM RKC_GET_OBJECT_DESCRIPTION - RKC GET OBJECT DESCRIPTION





CALL FUNCTION 'RKC_GET_OBJECT_DESCRIPTION' "
  EXPORTING
*   application = SPACE         " tkeb1-applclass
    object =                    " tkcos         Object to be investigated
  IMPORTING
    flag_keynode =              "
    text_objectid =             "               Formatted Object Key
    text_objecttype =           "               Text of the object type
    related_textclass =         " tkcod-txtcl
  EXCEPTIONS
    NO_DESCRIPTION = 1          "               No object description possible
    .  "  RKC_GET_OBJECT_DESCRIPTION

ABAP code example for Function Module RKC_GET_OBJECT_DESCRIPTION





The ABAP code below is a full code listing to execute function module RKC_GET_OBJECT_DESCRIPTION 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_flag_keynode  TYPE STRING ,
ld_text_objectid  TYPE STRING ,
ld_text_objecttype  TYPE STRING ,
ld_related_textclass  TYPE TKCOD-TXTCL .


SELECT single APPLCLASS
FROM TKEB1
INTO @DATA(ld_application).

DATA(ld_object) = 'Check type of data required'. . CALL FUNCTION 'RKC_GET_OBJECT_DESCRIPTION' EXPORTING * application = ld_application object = ld_object IMPORTING flag_keynode = ld_flag_keynode text_objectid = ld_text_objectid text_objecttype = ld_text_objecttype related_textclass = ld_related_textclass EXCEPTIONS NO_DESCRIPTION = 1 . " RKC_GET_OBJECT_DESCRIPTION
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_flag_keynode  TYPE STRING ,
ld_application  TYPE TKEB1-APPLCLASS ,
ld_text_objectid  TYPE STRING ,
ld_object  TYPE TKCOS ,
ld_text_objecttype  TYPE STRING ,
ld_related_textclass  TYPE TKCOD-TXTCL .


SELECT single APPLCLASS
FROM TKEB1
INTO ld_application.

ld_object = 'Check type of data required'.

SAP Documentation for FM RKC_GET_OBJECT_DESCRIPTION


As the identifiying object information is not suitable for an output, this function attempts to change the information objekt type and object ...See here for full SAP fm documentation














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 RKC_GET_OBJECT_DESCRIPTION or its description.