KKR_TEXT_FOR_VALUE_IN_TBLFIELD SAP Function module

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

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

Pattern for FM KKR_TEXT_FOR_VALUE_IN_TBLFIELD - KKR TEXT FOR VALUE IN TBLFIELD

CALL FUNCTION 'KKR_TEXT_FOR_VALUE_IN_TBLFIELD' "
  EXPORTING
    i_table =                   " dcobjdef-name
    i_field =                   " dfies-fieldname
    i_value =                   " c
*   i_langu = SY-LANGU          " sy-langu
  IMPORTING
    e_ktext =                   " c
    e_not_specified =           " sy-batch
  EXCEPTIONS
    TABLE_NOT_FOUND = 1         "
    FIELD_NOT_FOUND = 2         "
    NO_TEXTFIELD_FOUND = 3      "
    VALUE_NOT_FOUND = 4         "
    .  "  KKR_TEXT_FOR_VALUE_IN_TBLFIELD

ABAP code example for Function Module KKR_TEXT_FOR_VALUE_IN_TBLFIELD

The ABAP code below is a full code listing to execute function module KKR_TEXT_FOR_VALUE_IN_TBLFIELD 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_e_ktext  
 
 TYPE C
,
ld_e_not_specified  
 
 TYPE SY-BATCH
.



DATA(ld_i_table) = some text here


DATA(ld_i_field) = some text here

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

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

CALL FUNCTION 'KKR_TEXT_FOR_VALUE_IN_TBLFIELD'
  EXPORTING
    i_table =                    ld_i_table
    i_field =                    ld_i_field
    i_value =                    ld_i_value
*   i_langu =                    ld_i_langu
  IMPORTING
    e_ktext =                    ld_e_ktext
    e_not_specified =            ld_e_not_specified
  EXCEPTIONS
    TABLE_NOT_FOUND =            1
    FIELD_NOT_FOUND =            2
    NO_TEXTFIELD_FOUND =         3
    VALUE_NOT_FOUND =            4
    .  "  KKR_TEXT_FOR_VALUE_IN_TBLFIELD

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_e_ktext
 
 TYPE C ,
ld_i_table
 
 TYPE DCOBJDEF-NAME ,
ld_e_not_specified
 
 TYPE SY-BATCH ,
ld_i_field
 
 TYPE DFIES-FIELDNAME ,
ld_i_value
 
 TYPE C ,
ld_i_langu
 
 TYPE SY-LANGU .



ld_i_table = some text here

ld_i_field = some text here
ld_i_value = 'Check type of data required'.
ld_i_langu = 'Check type of data required'.