SAP Function Modules

TEXT_TRANSLATE SAP Function module







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

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


Pattern for FM TEXT_TRANSLATE - TEXT TRANSLATE





CALL FUNCTION 'TEXT_TRANSLATE' "
* EXPORTING
*   applik =                    "
*   header1 =                   " thead
*   header2 =                   " thead
*   source_language =           "
*   target_language =           "
*   doku_check =                " i
  IMPORTING
    state =                     "
  TABLES
    iline3 =                    " tline
    iline4 =                    " tline
  EXCEPTIONS
    ERROR = 1                   "
    .  "  TEXT_TRANSLATE

ABAP code example for Function Module TEXT_TRANSLATE





The ABAP code below is a full code listing to execute function module TEXT_TRANSLATE 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_state  TYPE STRING ,
it_iline3  TYPE STANDARD TABLE OF TLINE,"TABLES PARAM
wa_iline3  LIKE LINE OF it_iline3 ,
it_iline4  TYPE STANDARD TABLE OF TLINE,"TABLES PARAM
wa_iline4  LIKE LINE OF it_iline4 .

DATA(ld_applik) = 'some text here'.
DATA(ld_header1) = 'Check type of data required'.
DATA(ld_header2) = 'Check type of data required'.
DATA(ld_source_language) = 'some text here'.
DATA(ld_target_language) = 'some text here'.
DATA(ld_doku_check) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_iline3 to it_iline3.

"populate fields of struture and append to itab
append wa_iline4 to it_iline4. . CALL FUNCTION 'TEXT_TRANSLATE' * EXPORTING * applik = ld_applik * header1 = ld_header1 * header2 = ld_header2 * source_language = ld_source_language * target_language = ld_target_language * doku_check = ld_doku_check IMPORTING state = ld_state TABLES iline3 = it_iline3 iline4 = it_iline4 EXCEPTIONS ERROR = 1 . " TEXT_TRANSLATE
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_state  TYPE STRING ,
ld_applik  TYPE STRING ,
it_iline3  TYPE STANDARD TABLE OF TLINE ,
wa_iline3  LIKE LINE OF it_iline3,
ld_header1  TYPE THEAD ,
it_iline4  TYPE STANDARD TABLE OF TLINE ,
wa_iline4  LIKE LINE OF it_iline4,
ld_header2  TYPE THEAD ,
ld_source_language  TYPE STRING ,
ld_target_language  TYPE STRING ,
ld_doku_check  TYPE I .

ld_applik = 'some text here'.

"populate fields of struture and append to itab
append wa_iline3 to it_iline3.
ld_header1 = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_iline4 to it_iline4.
ld_header2 = 'Check type of data required'.
ld_source_language = 'some text here'.
ld_target_language = 'some text here'.
ld_doku_check = 'Check type of data required'.

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