SAP BAPI_SYSTEM_MTE_SPLITTDATA Function Module for Splits the Data for a Node into Logical Units
BAPI_SYSTEM_MTE_SPLITTDATA is a standard bapi system mte splittdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Splits the Data for a Node into Logical Units 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 bapi system mte splittdata FM, simply by entering the name BAPI_SYSTEM_MTE_SPLITTDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALX
Program Name: SAPLSALX
Main Program: SAPLSALX
Appliation area: S
Release date: 09-Nov-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SYSTEM_MTE_SPLITTDATA 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 'BAPI_SYSTEM_MTE_SPLITTDATA'"Splits the Data for a Node into Logical Units.
EXPORTING
NODE_DATA = "All Available Information About a MTE
EXTERNAL_USER_NAME = "Name of SAP-External User
IMPORTING
TID = "MTE ID (TID)
NODE_INFO = "Node-Related Data (Position in Tree and so on)
RETURN = "BAPI Return Structure
GENERAL_INFO = "General Data for a Monitor Tree Element
GENERAL_PROPERTIES = "General MTE Data (Name, MTE Class, and so on)
GENERAL_VALUES = "Current General Values
LAST_VALUE_TIME = "Time of Last Value Change
HIGHEST_ALERT_DATA = "Alert Value of 'Highest Alert'
HIGHEST_ALERT = "ID of 'Highest Alert'
ACTUAL_ALERT_DATA = "Alert Value of Actual Alert
ACTUAL_ALERT = "ID of 'Actual Alert'
IMPORTING Parameters details for BAPI_SYSTEM_MTE_SPLITTDATA
NODE_DATA - All Available Information About a MTE
Data type: BAPITNDEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME - Name of SAP-External User
Data type: BAPIXMLOGR-EXTUSEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_SYSTEM_MTE_SPLITTDATA
TID - MTE ID (TID)
Data type: BAPITIDOptional: No
Call by Reference: No ( called with pass by value option)
NODE_INFO - Node-Related Data (Position in Tree and so on)
Data type: BAPITREENDOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - BAPI Return Structure
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
GENERAL_INFO - General Data for a Monitor Tree Element
Data type: BAPIMTEGENOptional: No
Call by Reference: No ( called with pass by value option)
GENERAL_PROPERTIES - General MTE Data (Name, MTE Class, and so on)
Data type: BAPIMTEPRPOptional: No
Call by Reference: No ( called with pass by value option)
GENERAL_VALUES - Current General Values
Data type: BAPIMTEVALOptional: No
Call by Reference: No ( called with pass by value option)
LAST_VALUE_TIME - Time of Last Value Change
Data type: BAPIALDATEOptional: No
Call by Reference: No ( called with pass by value option)
HIGHEST_ALERT_DATA - Alert Value of 'Highest Alert'
Data type: BAPIALDATAOptional: No
Call by Reference: No ( called with pass by value option)
HIGHEST_ALERT - ID of 'Highest Alert'
Data type: BAPIAIDOptional: No
Call by Reference: No ( called with pass by value option)
ACTUAL_ALERT_DATA - Alert Value of Actual Alert
Data type: BAPIALDATAOptional: No
Call by Reference: No ( called with pass by value option)
ACTUAL_ALERT - ID of 'Actual Alert'
Data type: BAPIAIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SYSTEM_MTE_SPLITTDATA 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_tid | TYPE BAPITID, " | |||
| lv_node_data | TYPE BAPITNDEXT, " | |||
| lv_node_info | TYPE BAPITREEND, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_general_info | TYPE BAPIMTEGEN, " | |||
| lv_external_user_name | TYPE BAPIXMLOGR-EXTUSER, " | |||
| lv_general_properties | TYPE BAPIMTEPRP, " | |||
| lv_general_values | TYPE BAPIMTEVAL, " | |||
| lv_last_value_time | TYPE BAPIALDATE, " | |||
| lv_highest_alert_data | TYPE BAPIALDATA, " | |||
| lv_highest_alert | TYPE BAPIAID, " | |||
| lv_actual_alert_data | TYPE BAPIALDATA, " | |||
| lv_actual_alert | TYPE BAPIAID. " |
|   CALL FUNCTION 'BAPI_SYSTEM_MTE_SPLITTDATA' "Splits the Data for a Node into Logical Units |
| EXPORTING | ||
| NODE_DATA | = lv_node_data | |
| EXTERNAL_USER_NAME | = lv_external_user_name | |
| IMPORTING | ||
| TID | = lv_tid | |
| NODE_INFO | = lv_node_info | |
| RETURN | = lv_return | |
| GENERAL_INFO | = lv_general_info | |
| GENERAL_PROPERTIES | = lv_general_properties | |
| GENERAL_VALUES | = lv_general_values | |
| LAST_VALUE_TIME | = lv_last_value_time | |
| HIGHEST_ALERT_DATA | = lv_highest_alert_data | |
| HIGHEST_ALERT | = lv_highest_alert | |
| ACTUAL_ALERT_DATA | = lv_actual_alert_data | |
| ACTUAL_ALERT | = lv_actual_alert | |
| . " BAPI_SYSTEM_MTE_SPLITTDATA | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SYSTEM_MTE_SPLITTDATA
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.| "SELECT single EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_external_user_name). | ||||
Search for further information about these or an SAP related objects