SAP LXE_STH_WRITE_TEXTS Function Module for Write object texts
LXE_STH_WRITE_TEXTS is a standard lxe sth write texts SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write object texts 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 sth write texts FM, simply by entering the name LXE_STH_WRITE_TEXTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_WB_INTF
Program Name: SAPLLXE_WB_INTF
Main Program: SAPLLXE_WB_INTF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function LXE_STH_WRITE_TEXTS 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_STH_WRITE_TEXTS'"Write object texts.
EXPORTING
I_SRC_LANG = "Source Language
I_TGT_LANG = "Target Language
I_OBJ_TYPE = "Type of Translation Object
I_OBJ_NAME = "Name of Translation Object
TABLES
IT_TEXTS = "Text Pairs
EXCEPTIONS
OBJECT_INVALID = 1 OBJECT_NO_TEXT = 2 DB_WRITE_ERROR = 3 ORIGINAL_LANGUAGE_CONFLICT = 4 TARGET_LANGUAGE_INVALID = 5 SOURCE_LANGUAGE_INVALID = 6 NO_AUTHORIZATION = 7 MAX_LENGTH_EXCEEDED = 8
IMPORTING Parameters details for LXE_STH_WRITE_TEXTS
I_SRC_LANG - Source Language
Data type: LXEISOLANGOptional: No
Call by Reference: No ( called with pass by value option)
I_TGT_LANG - Target Language
Data type: LXEISOLANGOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJ_TYPE - Type of Translation Object
Data type: LXEOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJ_NAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LXE_STH_WRITE_TEXTS
IT_TEXTS - Text Pairs
Data type: LXE_PCX_S1Optional: No
Call by Reference: Yes
EXCEPTIONS details
OBJECT_INVALID -
Data type:Optional: No
Call by Reference: Yes
OBJECT_NO_TEXT -
Data type:Optional: No
Call by Reference: Yes
DB_WRITE_ERROR -
Data type:Optional: No
Call by Reference: Yes
ORIGINAL_LANGUAGE_CONFLICT -
Data type:Optional: No
Call by Reference: Yes
TARGET_LANGUAGE_INVALID -
Data type:Optional: No
Call by Reference: Yes
SOURCE_LANGUAGE_INVALID -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
MAX_LENGTH_EXCEEDED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_STH_WRITE_TEXTS 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: | ||||
| lt_it_texts | TYPE STANDARD TABLE OF LXE_PCX_S1, " | |||
| lv_i_src_lang | TYPE LXEISOLANG, " | |||
| lv_object_invalid | TYPE LXEISOLANG, " | |||
| lv_i_tgt_lang | TYPE LXEISOLANG, " | |||
| lv_object_no_text | TYPE LXEISOLANG, " | |||
| lv_i_obj_type | TYPE LXEOBJTYPE, " | |||
| lv_db_write_error | TYPE LXEOBJTYPE, " | |||
| lv_i_obj_name | TYPE LXEOBJNAME, " | |||
| lv_original_language_conflict | TYPE LXEOBJNAME, " | |||
| lv_target_language_invalid | TYPE LXEOBJNAME, " | |||
| lv_source_language_invalid | TYPE LXEOBJNAME, " | |||
| lv_no_authorization | TYPE LXEOBJNAME, " | |||
| lv_max_length_exceeded | TYPE LXEOBJNAME. " |
|   CALL FUNCTION 'LXE_STH_WRITE_TEXTS' "Write object texts |
| EXPORTING | ||
| I_SRC_LANG | = lv_i_src_lang | |
| I_TGT_LANG | = lv_i_tgt_lang | |
| I_OBJ_TYPE | = lv_i_obj_type | |
| I_OBJ_NAME | = lv_i_obj_name | |
| TABLES | ||
| IT_TEXTS | = lt_it_texts | |
| EXCEPTIONS | ||
| OBJECT_INVALID = 1 | ||
| OBJECT_NO_TEXT = 2 | ||
| DB_WRITE_ERROR = 3 | ||
| ORIGINAL_LANGUAGE_CONFLICT = 4 | ||
| TARGET_LANGUAGE_INVALID = 5 | ||
| SOURCE_LANGUAGE_INVALID = 6 | ||
| NO_AUTHORIZATION = 7 | ||
| MAX_LENGTH_EXCEEDED = 8 | ||
| . " LXE_STH_WRITE_TEXTS | ||
ABAP code using 7.40 inline data declarations to call FM LXE_STH_WRITE_TEXTS
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