GET_TEXT_OF_OBJECT SAP Function module - Assigns the Text to a Hierarchy Object of Application Monitor

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

Associated Function Group: STMO
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM GET_TEXT_OF_OBJECT - GET TEXT OF OBJECT

CALL FUNCTION 'GET_TEXT_OF_OBJECT' "Assigns the Text to a Hierarchy Object of Application Monitor
  EXPORTING
    asked_level =               " ewagg-hi_level  Object Level
    objectname =                " ewagg-obj_name  Object Name
    object_typ =                " tadir-object  Object Type (Report, Transaction, Table, and so on)
*   object_pgmid = 'R3TR'       " tadir-pgmid
  IMPORTING
    asked_text =                "               Associated Text
  EXCEPTIONS
    WRONG_LEVEL = 1             "
    WRONG_OBJECT = 2            "               Unknown Object
    WRONG_PGMID = 3             "
    WRONG_TYP = 4               "
    .  "  GET_TEXT_OF_OBJECT

ABAP code example for Function Module GET_TEXT_OF_OBJECT

The ABAP code below is a full code listing to execute function module GET_TEXT_OF_OBJECT 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_asked_text  
 
 TYPE STRING
.

 

SELECT single HI_LEVEL 
  FROM EWAGG 
  INTO @DATA(ld_asked_level).

 

SELECT single OBJ_NAME 
  FROM EWAGG 
  INTO @DATA(ld_objectname).

 

SELECT single OBJECT 
  FROM TADIR 
  INTO @DATA(ld_object_typ).

 

SELECT single PGMID 
  FROM TADIR 
  INTO @DATA(ld_object_pgmid).

.

CALL FUNCTION 'GET_TEXT_OF_OBJECT'
  EXPORTING
    asked_level =                ld_asked_level
    objectname =                 ld_objectname
    object_typ =                 ld_object_typ
*   object_pgmid =               ld_object_pgmid
  IMPORTING
    asked_text =                 ld_asked_text
  EXCEPTIONS
    WRONG_LEVEL =                1
    WRONG_OBJECT =               2
    WRONG_PGMID =                3
    WRONG_TYP =                  4
    .  "  GET_TEXT_OF_OBJECT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_asked_text
 
 TYPE STRING ,
ld_asked_level
 
 TYPE EWAGG-HI_LEVEL ,
ld_objectname
 
 TYPE EWAGG-OBJ_NAME ,
ld_object_typ
 
 TYPE TADIR-OBJECT ,
ld_object_pgmid
 
 TYPE TADIR-PGMID .



SELECT single HI_LEVEL 
  FROM EWAGG 
  INTO ld_asked_level.


SELECT single OBJ_NAME 
  FROM EWAGG 
  INTO ld_objectname.


SELECT single OBJECT 
  FROM TADIR 
  INTO ld_object_typ.


SELECT single PGMID 
  FROM TADIR 
  INTO ld_object_pgmid.