SAP LXE_XT_GET_TEXT_ATTRIBUTE Function Module for Get Optional Text Attributes
LXE_XT_GET_TEXT_ATTRIBUTE is a standard lxe xt get text attribute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Optional Text Attributes 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 get text attribute FM, simply by entering the name LXE_XT_GET_TEXT_ATTRIBUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_XT
Program Name: SAPLLXE_XT
Main Program: SAPLLXE_XT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_XT_GET_TEXT_ATTRIBUTE 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_GET_TEXT_ATTRIBUTE'"Get Optional Text Attributes.
EXPORTING
TRL_AREA = "Customer Number
OBJNAME = "Name of Translation Object
TEXTKEY = "Text Key
ATTR_NAME = "Attribute Key
IMPORTING
VALUE = "Text
IMPORTING Parameters details for LXE_XT_GET_TEXT_ATTRIBUTE
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
TEXTKEY - Text Key
Data type: LXETEXTKEYOptional: No
Call by Reference: Yes
ATTR_NAME - Attribute Key
Data type: LXEPARKEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LXE_XT_GET_TEXT_ATTRIBUTE
VALUE - Text
Data type: LXESTRINGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_XT_GET_TEXT_ATTRIBUTE 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_value | TYPE LXESTRING, " | |||
| lv_trl_area | TYPE LXECUSTMNR, " | |||
| lv_objname | TYPE LXEOBJNAME, " | |||
| lv_textkey | TYPE LXETEXTKEY, " | |||
| lv_attr_name | TYPE LXEPARKEY. " |
|   CALL FUNCTION 'LXE_XT_GET_TEXT_ATTRIBUTE' "Get Optional Text Attributes |
| EXPORTING | ||
| TRL_AREA | = lv_trl_area | |
| OBJNAME | = lv_objname | |
| TEXTKEY | = lv_textkey | |
| ATTR_NAME | = lv_attr_name | |
| IMPORTING | ||
| VALUE | = lv_value | |
| . " LXE_XT_GET_TEXT_ATTRIBUTE | ||
ABAP code using 7.40 inline data declarations to call FM LXE_XT_GET_TEXT_ATTRIBUTE
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