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

Function LXE_COMMON_XSTRING_TO_TABLE 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_COMMON_XSTRING_TO_TABLE'"Convers..
EXPORTING
IN_XSTRING = "Predefined Type
IMPORTING
PSTATUS = "Process Status
TABLES
EX_TAB = "Binary String
IMPORTING Parameters details for LXE_COMMON_XSTRING_TO_TABLE
IN_XSTRING - Predefined Type
Data type: XSTRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LXE_COMMON_XSTRING_TO_TABLE
PSTATUS - Process Status
Data type: LXESTATPRCOptional: No
Call by Reference: Yes
TABLES Parameters details for LXE_COMMON_XSTRING_TO_TABLE
EX_TAB - Binary String
Data type: LXE_XTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_COMMON_XSTRING_TO_TABLE 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_ex_tab | TYPE STANDARD TABLE OF LXE_XTAB, " | |||
| lv_pstatus | TYPE LXESTATPRC, " | |||
| lv_in_xstring | TYPE XSTRING. " |
|   CALL FUNCTION 'LXE_COMMON_XSTRING_TO_TABLE' "Convers. |
| EXPORTING | ||
| IN_XSTRING | = lv_in_xstring | |
| IMPORTING | ||
| PSTATUS | = lv_pstatus | |
| TABLES | ||
| EX_TAB | = lt_ex_tab | |
| . " LXE_COMMON_XSTRING_TO_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM LXE_COMMON_XSTRING_TO_TABLE
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