SAP Tables

OIK_DOMAIN_TEXT_GET SAP Function module - TAS/TPI: Get domain text






OIK_DOMAIN_TEXT_GETis a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name OIK_DOMAIN_TEXT_GET into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM OIK_DOMAIN_TEXT_GET - OIK DOMAIN TEXT GET
Associated Function Group: OIKZ
Released Date: Not Released
CALL FUNCTION 'OIK_DOMAIN_TEXT_GET' "TAS/TPI: Get domain text
  EXPORTING
    i_domain_name =             " dd07l-domname  Domain
*   i_language = SY-LANGU       " sy-langu      Language for short text
*   i_domvalue_l = SPACE        " dd07v-domvalue_l  Lower fixed value of domain
  IMPORTING
    e_ddtext =                  " dd07v-ddtext  Descriptive short text for lower fixed value
  EXCEPTIONS
    NO_DATA_FOUND = 1           "               No data found
    .  "  OIK_DOMAIN_TEXT_GET

ABAP code example for Function Module OIK_DOMAIN_TEXT_GET

The ABAP code below is a full code listing to execute function module OIK_DOMAIN_TEXT_GET including all data declarations. The code uses the latest in-line data declaration syntax but I have included an abap code snipet 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_e_ddtext   TYPE DD07V-DDTEXT.


SELECT single DOMNAME
FROM DD07L
INTO @DATA(ld_i_domain_name).

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

SELECT single DOMVALUE_L
FROM DD07V
INTO @DATA(ld_i_domvalue_l).
. CALL FUNCTION 'OIK_DOMAIN_TEXT_GET' EXPORTING i_domain_name = ld_i_domain_name * i_language = ld_i_language * i_domvalue_l = ld_i_domvalue_l IMPORTING e_ddtext = ld_e_ddtext EXCEPTIONS NO_DATA_FOUND = 1 . " OIK_DOMAIN_TEXT_GET
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_e_ddtext TYPE DD07V-DDTEXT ,
ld_i_domain_name TYPE DD07L-DOMNAME ,
ld_i_language TYPE SY-LANGU ,
ld_i_domvalue_l TYPE DD07V-DOMVALUE_L .


SELECT single DDTEXT
FROM DD07V
INTO ld_e_ddtext.


SELECT single DOMNAME
FROM DD07L
INTO ld_i_domain_name.

ld_i_language = 'Check type of data required'.

SELECT single DOMVALUE_L
FROM DD07V
INTO ld_i_domvalue_l.
.