SAP LXE_TS_API_PUT_TRANSLATION3 Function Module for Puts translations to the translation system
LXE_TS_API_PUT_TRANSLATION3 is a standard lxe ts api put translation3 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Puts translations to the translation system 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 lxe ts api put translation3 FM, simply by entering the name LXE_TS_API_PUT_TRANSLATION3 into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_TS_API_AREA_GEN3
Program Name: SAPLLXE_TS_API_AREA_GEN3
Main Program: SAPLLXE_TS_API_AREA_GEN3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function LXE_TS_API_PUT_TRANSLATION3 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 'LXE_TS_API_PUT_TRANSLATION3'"Puts translations to the translation system.
EXPORTING
TRANSAREA = "Translation Area
OBJNAME3 = "Text
LANGUAGE = "ISO Language ID
XTEXT_TAB = "Short Texts
YTEXT_TAB = "Long Texts
ZTEXT_TAB = "Special Texts
ZBIN_TAB = "Special Binary Texts
EXCEPTIONS
UNAUTHORIZED = 1 ORIG_LANG_CONFLICT = 10 TEXT_DEFECTIVE = 11 DB_ERROR = 12 INVALID_TEXTKEY = 13 LOCKED = 14 UNKNOWN_TRANS_AREA = 2 UNSUPPORTED_TRANS_AREA_TYPE = 3 UNKNOWN_LANGUAGE = 4 IS_ORIGINAL_LANGUAGE = 5 IMPORT_FAILED = 6 INVALID_OBJECT = 7 HASH_ERROR = 8 OBJECT_NOT_FOUND = 9
IMPORTING Parameters details for LXE_TS_API_PUT_TRANSLATION3
TRANSAREA - Translation Area
Data type: LXECUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
OBJNAME3 - Text
Data type: LXESTRINGOptional: No
Call by Reference: No ( called with pass by value option)
LANGUAGE - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: No ( called with pass by value option)
XTEXT_TAB - Short Texts
Data type: LXE_TT_XTEXT_TRLOptional: No
Call by Reference: No ( called with pass by value option)
YTEXT_TAB - Long Texts
Data type: LXE_TT_YTEXT_TRLOptional: No
Call by Reference: No ( called with pass by value option)
ZTEXT_TAB - Special Texts
Data type: LXE_TT_ZTEXT_TRLOptional: No
Call by Reference: No ( called with pass by value option)
ZBIN_TAB - Special Binary Texts
Data type: LXE_TT_ZBIN_TRLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNAUTHORIZED - Unauthorized
Data type:Optional: No
Call by Reference: Yes
ORIG_LANG_CONFLICT - Tried to upload an original language
Data type:Optional: No
Call by Reference: Yes
TEXT_DEFECTIVE - A text is defective
Data type:Optional: No
Call by Reference: Yes
DB_ERROR - Database error
Data type:Optional: No
Call by Reference: Yes
INVALID_TEXTKEY - Invalid text key
Data type:Optional: No
Call by Reference: Yes
LOCKED - Operation is currently locked
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_TRANS_AREA - Unknown translation area
Data type:Optional: No
Call by Reference: Yes
UNSUPPORTED_TRANS_AREA_TYPE - Unsupported translation area type
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_LANGUAGE - Unknown language
Data type:Optional: No
Call by Reference: Yes
IS_ORIGINAL_LANGUAGE - Passed language is an original language
Data type:Optional: No
Call by Reference: Yes
IMPORT_FAILED - Import failed
Data type:Optional: No
Call by Reference: Yes
INVALID_OBJECT - Invalid object
Data type:Optional: No
Call by Reference: Yes
HASH_ERROR - Hash error
Data type:Optional: No
Call by Reference: Yes
OBJECT_NOT_FOUND - Object not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_TS_API_PUT_TRANSLATION3 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_transarea | TYPE LXECUSTMNR, " | |||
| lv_unauthorized | TYPE LXECUSTMNR, " | |||
| lv_orig_lang_conflict | TYPE LXECUSTMNR, " | |||
| lv_text_defective | TYPE LXECUSTMNR, " | |||
| lv_db_error | TYPE LXECUSTMNR, " | |||
| lv_invalid_textkey | TYPE LXECUSTMNR, " | |||
| lv_locked | TYPE LXECUSTMNR, " | |||
| lv_objname3 | TYPE LXESTRING, " | |||
| lv_unknown_trans_area | TYPE LXESTRING, " | |||
| lv_language | TYPE LXEISOLANG, " | |||
| lv_unsupported_trans_area_type | TYPE LXEISOLANG, " | |||
| lv_xtext_tab | TYPE LXE_TT_XTEXT_TRL, " | |||
| lv_unknown_language | TYPE LXE_TT_XTEXT_TRL, " | |||
| lv_ytext_tab | TYPE LXE_TT_YTEXT_TRL, " | |||
| lv_is_original_language | TYPE LXE_TT_YTEXT_TRL, " | |||
| lv_ztext_tab | TYPE LXE_TT_ZTEXT_TRL, " | |||
| lv_import_failed | TYPE LXE_TT_ZTEXT_TRL, " | |||
| lv_zbin_tab | TYPE LXE_TT_ZBIN_TRL, " | |||
| lv_invalid_object | TYPE LXE_TT_ZBIN_TRL, " | |||
| lv_hash_error | TYPE LXE_TT_ZBIN_TRL, " | |||
| lv_object_not_found | TYPE LXE_TT_ZBIN_TRL. " |
|   CALL FUNCTION 'LXE_TS_API_PUT_TRANSLATION3' "Puts translations to the translation system |
| EXPORTING | ||
| TRANSAREA | = lv_transarea | |
| OBJNAME3 | = lv_objname3 | |
| LANGUAGE | = lv_language | |
| XTEXT_TAB | = lv_xtext_tab | |
| YTEXT_TAB | = lv_ytext_tab | |
| ZTEXT_TAB | = lv_ztext_tab | |
| ZBIN_TAB | = lv_zbin_tab | |
| EXCEPTIONS | ||
| UNAUTHORIZED = 1 | ||
| ORIG_LANG_CONFLICT = 10 | ||
| TEXT_DEFECTIVE = 11 | ||
| DB_ERROR = 12 | ||
| INVALID_TEXTKEY = 13 | ||
| LOCKED = 14 | ||
| UNKNOWN_TRANS_AREA = 2 | ||
| UNSUPPORTED_TRANS_AREA_TYPE = 3 | ||
| UNKNOWN_LANGUAGE = 4 | ||
| IS_ORIGINAL_LANGUAGE = 5 | ||
| IMPORT_FAILED = 6 | ||
| INVALID_OBJECT = 7 | ||
| HASH_ERROR = 8 | ||
| OBJECT_NOT_FOUND = 9 | ||
| . " LXE_TS_API_PUT_TRANSLATION3 | ||
ABAP code using 7.40 inline data declarations to call FM LXE_TS_API_PUT_TRANSLATION3
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