SAP LXE_XT_YTEXT_WRITE Function Module for Write YNAT Texts
LXE_XT_YTEXT_WRITE is a standard lxe xt ytext write 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 YNAT 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 xt ytext write FM, simply by entering the name LXE_XT_YTEXT_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_XT
Program Name: SAPLLXE_XT
Main Program: SAPLLXE_XT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_XT_YTEXT_WRITE 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_XT_YTEXT_WRITE'"Write YNAT Texts.
EXPORTING
S_LANG = "ISO Language ID
T_LANG = "ISO Language ID
TRL_AREA = "Customer Number
OBJNAME = "Name of Translation Object
IT_TEXTS = "Long Texts With Key
* REPLACE = '' "Single-Character Flag
EXCEPTIONS
OBJECT_DOES_NOT_EXIST = 1 ORIG_LANG_CONFLICT = 2 NO_VALID_TEXT_FOUND = 3 DB_ERROR = 4
IMPORTING Parameters details for LXE_XT_YTEXT_WRITE
S_LANG - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
T_LANG - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
TRL_AREA - Customer Number
Data type: LXECUSTMNROptional: No
Call by Reference: Yes
OBJNAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: Yes
IT_TEXTS - Long Texts With Key
Data type: LXE_TEXT_TABOptional: No
Call by Reference: Yes
REPLACE - Single-Character Flag
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
OBJECT_DOES_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ORIG_LANG_CONFLICT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_TEXT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXE_XT_YTEXT_WRITE 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_s_lang | TYPE LXEISOLANG, " | |||
| lv_object_does_not_exist | TYPE LXEISOLANG, " | |||
| lv_t_lang | TYPE LXEISOLANG, " | |||
| lv_orig_lang_conflict | TYPE LXEISOLANG, " | |||
| lv_trl_area | TYPE LXECUSTMNR, " | |||
| lv_no_valid_text_found | TYPE LXECUSTMNR, " | |||
| lv_objname | TYPE LXEOBJNAME, " | |||
| lv_db_error | TYPE LXEOBJNAME, " | |||
| lv_it_texts | TYPE LXE_TEXT_TAB, " | |||
| lv_replace | TYPE CHAR1. " '' |
|   CALL FUNCTION 'LXE_XT_YTEXT_WRITE' "Write YNAT Texts |
| EXPORTING | ||
| S_LANG | = lv_s_lang | |
| T_LANG | = lv_t_lang | |
| TRL_AREA | = lv_trl_area | |
| OBJNAME | = lv_objname | |
| IT_TEXTS | = lv_it_texts | |
| REPLACE | = lv_replace | |
| EXCEPTIONS | ||
| OBJECT_DOES_NOT_EXIST = 1 | ||
| ORIG_LANG_CONFLICT = 2 | ||
| NO_VALID_TEXT_FOUND = 3 | ||
| DB_ERROR = 4 | ||
| . " LXE_XT_YTEXT_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM LXE_XT_YTEXT_WRITE
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.| DATA(ld_replace) | = ''. | |||
Search for further information about these or an SAP related objects