MULTI_GLOBAL_GET_SINGLE SAP Function module - Function for standard text key

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

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

Pattern for FM MULTI_GLOBAL_GET_SINGLE - MULTI GLOBAL GET SINGLE

CALL FUNCTION 'MULTI_GLOBAL_GET_SINGLE' "Function for standard text key
  EXPORTING
    iv_application =            " cnldst_applic
    iv_object =                 " cnldst_object
    iv_objnr =                  " j_objnr       Object number
    iv_language =               " spras         Language Key
  IMPORTING
    es_return =                 " cnldst_shorttx
  EXCEPTIONS
    NO_ENTRY = 1                "               no entry
    .  "  MULTI_GLOBAL_GET_SINGLE

ABAP code example for Function Module MULTI_GLOBAL_GET_SINGLE

The ABAP code below is a full code listing to execute function module MULTI_GLOBAL_GET_SINGLE 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_es_return  
 
 TYPE CNLDST_SHORTTX
.


DATA(ld_iv_application) = 'Check type of data required'.

DATA(ld_iv_object) = 'Check type of data required'.

DATA(ld_iv_objnr) = 'Check type of data required'.

DATA(ld_iv_language) = 'Check type of data required'.
.

CALL FUNCTION 'MULTI_GLOBAL_GET_SINGLE'
  EXPORTING
    iv_application =             ld_iv_application
    iv_object =                  ld_iv_object
    iv_objnr =                   ld_iv_objnr
    iv_language =                ld_iv_language
  IMPORTING
    es_return =                  ld_es_return
  EXCEPTIONS
    NO_ENTRY =                   1
    .  "  MULTI_GLOBAL_GET_SINGLE

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_es_return
 
 TYPE CNLDST_SHORTTX ,
ld_iv_application
 
 TYPE CNLDST_APPLIC ,
ld_iv_object
 
 TYPE CNLDST_OBJECT ,
ld_iv_objnr
 
 TYPE J_OBJNR ,
ld_iv_language
 
 TYPE SPRAS .


ld_iv_application = 'Check type of data required'.
ld_iv_object = 'Check type of data required'.
ld_iv_objnr = 'Check type of data required'.
ld_iv_language = 'Check type of data required'.