SAP FXM_SQL_MSG_SPLIT Function Module for SQL return message split
FXM_SQL_MSG_SPLIT is a standard fxm sql msg split SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SQL return message split 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 fxm sql msg split FM, simply by entering the name FXM_SQL_MSG_SPLIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FXM_BSE
Program Name: SAPLFXM_BSE
Main Program: SAPLFXM_BSE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FXM_SQL_MSG_SPLIT 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 'FXM_SQL_MSG_SPLIT'"SQL return message split.
EXPORTING
IV_STRING = "SQL return message
IMPORTING
EV_MSG1 = "Message Variable
EV_MSG2 = "Message Variable
EV_MSG3 = "Message Variable
EV_MSG4 = "Message Variable
IMPORTING Parameters details for FXM_SQL_MSG_SPLIT
IV_STRING - SQL return message
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FXM_SQL_MSG_SPLIT
EV_MSG1 - Message Variable
Data type: SYMSGVOptional: No
Call by Reference: Yes
EV_MSG2 - Message Variable
Data type: SYMSGVOptional: No
Call by Reference: Yes
EV_MSG3 - Message Variable
Data type: SYMSGVOptional: No
Call by Reference: Yes
EV_MSG4 - Message Variable
Data type: SYMSGVOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FXM_SQL_MSG_SPLIT 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_ev_msg1 | TYPE SYMSGV, " | |||
| lv_iv_string | TYPE STRING, " | |||
| lv_ev_msg2 | TYPE SYMSGV, " | |||
| lv_ev_msg3 | TYPE SYMSGV, " | |||
| lv_ev_msg4 | TYPE SYMSGV. " |
|   CALL FUNCTION 'FXM_SQL_MSG_SPLIT' "SQL return message split |
| EXPORTING | ||
| IV_STRING | = lv_iv_string | |
| IMPORTING | ||
| EV_MSG1 | = lv_ev_msg1 | |
| EV_MSG2 | = lv_ev_msg2 | |
| EV_MSG3 | = lv_ev_msg3 | |
| EV_MSG4 | = lv_ev_msg4 | |
| . " FXM_SQL_MSG_SPLIT | ||
ABAP code using 7.40 inline data declarations to call FM FXM_SQL_MSG_SPLIT
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