SAP TEXT_TRANSLATE Function Module for NOTRANSL: Kompatibilität für REPORT WRITER - Übersetzung
TEXT_TRANSLATE is a standard text translate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Kompatibilität für REPORT WRITER - Übersetzung processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for text translate FM, simply by entering the name TEXT_TRANSLATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SKTU
Program Name: SAPLSKTU
Main Program: SAPLSKTU
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEXT_TRANSLATE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'TEXT_TRANSLATE'"NOTRANSL: Kompatibilität für REPORT WRITER - Übersetzung.
EXPORTING
* APPLIK = "
* HEADER1 = "SAPscript: Text Header
* HEADER2 = "SAPscript: Text Header
* SOURCE_LANGUAGE = "
* TARGET_LANGUAGE = "
* DOKU_CHECK = "Predefined Type
IMPORTING
STATE = "
TABLES
ILINE3 = "SAPscript: Text Lines
ILINE4 = "SAPscript: Text Lines
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for TEXT_TRANSLATE
APPLIK -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
HEADER1 - SAPscript: Text Header
Data type: THEADOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADER2 - SAPscript: Text Header
Data type: THEADOptional: Yes
Call by Reference: No ( called with pass by value option)
SOURCE_LANGUAGE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TARGET_LANGUAGE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DOKU_CHECK - Predefined Type
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TEXT_TRANSLATE
STATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TEXT_TRANSLATE
ILINE3 - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: No ( called with pass by value option)
ILINE4 - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TEXT_TRANSLATE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_error | TYPE STRING, " | |||
| lv_state | TYPE STRING, " | |||
| lv_applik | TYPE STRING, " | |||
| lt_iline3 | TYPE STANDARD TABLE OF TLINE, " | |||
| lt_iline4 | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_header1 | TYPE THEAD, " | |||
| lv_header2 | TYPE THEAD, " | |||
| lv_source_language | TYPE THEAD, " | |||
| lv_target_language | TYPE THEAD, " | |||
| lv_doku_check | TYPE I. " |
|   CALL FUNCTION 'TEXT_TRANSLATE' "NOTRANSL: Kompatibilität für REPORT WRITER - Übersetzung |
| EXPORTING | ||
| APPLIK | = lv_applik | |
| HEADER1 | = lv_header1 | |
| HEADER2 | = lv_header2 | |
| SOURCE_LANGUAGE | = lv_source_language | |
| TARGET_LANGUAGE | = lv_target_language | |
| DOKU_CHECK | = lv_doku_check | |
| IMPORTING | ||
| STATE | = lv_state | |
| TABLES | ||
| ILINE3 | = lt_iline3 | |
| ILINE4 | = lt_iline4 | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " TEXT_TRANSLATE | ||
ABAP code using 7.40 inline data declarations to call FM TEXT_TRANSLATE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects