SAP BAPI_SYSTEM_MTE_GETGENPROP Function Module for Read General Properties of a Monitor Tree Element









BAPI_SYSTEM_MTE_GETGENPROP is a standard bapi system mte getgenprop SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read General Properties of a Monitor Tree Element 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 getgenprop FM, simply by entering the name BAPI_SYSTEM_MTE_GETGENPROP 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_GETGENPROP 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_GETGENPROP'"Read General Properties of a Monitor Tree Element
EXPORTING
TID = "Monitor Tree Element ID
EXTERNAL_USER_NAME = "Name of the SAP-External User

IMPORTING
GENERAL_INFO = "General Data (Name, MTE Class and so on)
ONALERT_TOOL_DEF = "Effectively Assigned Auto-Reaction Method
ANALYZE_TOOL_DEF = "Effectively Assigned Analysis Method
COLLECTION_TOOL_RUN = "Runtime Information for Data Collection Method
ONALERT_TOOL_RUN = "Runtime Information for Auto-Reaction Method
PARENT_TID = "Parent Node ID
PARENT_DATA = "Information About the Parent Node
RETURN = "Return Messages
GENERAL_PROPERTIES = "General Customizing data
GENERAL_VALUES = "Current General Values
LAST_VALUE_TIME = "Time of Last Value Change
HIGHEST_ALERT = "ID of 'Highest Alert'
HIGHEST_ALERT_DATA = "Alert Value of 'Highest Alert'
ACTUAL_ALERT = "ID of 'Actual Alert'
ACTUAL_ALERT_DATA = "Alert Value of Actual Alert
COLLECTION_TOOL_DEF = "Effectively Assigned Data Collection Method
.



IMPORTING Parameters details for BAPI_SYSTEM_MTE_GETGENPROP

TID - Monitor Tree Element ID

Data type: BAPITID
Optional: No
Call by Reference: No ( called with pass by value option)

EXTERNAL_USER_NAME - Name of the SAP-External User

Data type: BAPIXMLOGR-EXTUSER
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_SYSTEM_MTE_GETGENPROP

GENERAL_INFO - General Data (Name, MTE Class and so on)

Data type: BAPIMTEGEN
Optional: No
Call by Reference: No ( called with pass by value option)

ONALERT_TOOL_DEF - Effectively Assigned Auto-Reaction Method

Data type: BAPITLDEF
Optional: No
Call by Reference: No ( called with pass by value option)

ANALYZE_TOOL_DEF - Effectively Assigned Analysis Method

Data type: BAPITLDEF
Optional: No
Call by Reference: No ( called with pass by value option)

COLLECTION_TOOL_RUN - Runtime Information for Data Collection Method

Data type: BAPITLRUN
Optional: No
Call by Reference: No ( called with pass by value option)

ONALERT_TOOL_RUN - Runtime Information for Auto-Reaction Method

Data type: BAPITLRUN
Optional: No
Call by Reference: No ( called with pass by value option)

PARENT_TID - Parent Node ID

Data type: BAPITID
Optional: No
Call by Reference: No ( called with pass by value option)

PARENT_DATA - Information About the Parent Node

Data type: BAPIPARENT
Optional: No
Call by Reference: No ( called with pass by value option)

RETURN - Return Messages

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

GENERAL_PROPERTIES - General Customizing data

Data type: BAPIMTEPRP
Optional: No
Call by Reference: No ( called with pass by value option)

GENERAL_VALUES - Current General Values

Data type: BAPIMTEVAL
Optional: No
Call by Reference: No ( called with pass by value option)

LAST_VALUE_TIME - Time of Last Value Change

Data type: BAPIALDATE
Optional: No
Call by Reference: No ( called with pass by value option)

HIGHEST_ALERT - ID of 'Highest Alert'

Data type: BAPIAID
Optional: No
Call by Reference: No ( called with pass by value option)

HIGHEST_ALERT_DATA - Alert Value of 'Highest Alert'

Data type: BAPIALDATA
Optional: No
Call by Reference: No ( called with pass by value option)

ACTUAL_ALERT - ID of 'Actual Alert'

Data type: BAPIAID
Optional: No
Call by Reference: No ( called with pass by value option)

ACTUAL_ALERT_DATA - Alert Value of Actual Alert

Data type: BAPIALDATA
Optional: No
Call by Reference: No ( called with pass by value option)

COLLECTION_TOOL_DEF - Effectively Assigned Data Collection Method

Data type: BAPITLDEF
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_SYSTEM_MTE_GETGENPROP 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_general_info  TYPE BAPIMTEGEN, "   
lv_onalert_tool_def  TYPE BAPITLDEF, "   
lv_analyze_tool_def  TYPE BAPITLDEF, "   
lv_collection_tool_run  TYPE BAPITLRUN, "   
lv_onalert_tool_run  TYPE BAPITLRUN, "   
lv_parent_tid  TYPE BAPITID, "   
lv_parent_data  TYPE BAPIPARENT, "   
lv_return  TYPE BAPIRET2, "   
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  TYPE BAPIAID, "   
lv_highest_alert_data  TYPE BAPIALDATA, "   
lv_actual_alert  TYPE BAPIAID, "   
lv_actual_alert_data  TYPE BAPIALDATA, "   
lv_collection_tool_def  TYPE BAPITLDEF. "   

  CALL FUNCTION 'BAPI_SYSTEM_MTE_GETGENPROP'  "Read General Properties of a Monitor Tree Element
    EXPORTING
         TID = lv_tid
         EXTERNAL_USER_NAME = lv_external_user_name
    IMPORTING
         GENERAL_INFO = lv_general_info
         ONALERT_TOOL_DEF = lv_onalert_tool_def
         ANALYZE_TOOL_DEF = lv_analyze_tool_def
         COLLECTION_TOOL_RUN = lv_collection_tool_run
         ONALERT_TOOL_RUN = lv_onalert_tool_run
         PARENT_TID = lv_parent_tid
         PARENT_DATA = lv_parent_data
         RETURN = lv_return
         GENERAL_PROPERTIES = lv_general_properties
         GENERAL_VALUES = lv_general_values
         LAST_VALUE_TIME = lv_last_value_time
         HIGHEST_ALERT = lv_highest_alert
         HIGHEST_ALERT_DATA = lv_highest_alert_data
         ACTUAL_ALERT = lv_actual_alert
         ACTUAL_ALERT_DATA = lv_actual_alert_data
         COLLECTION_TOOL_DEF = lv_collection_tool_def
. " BAPI_SYSTEM_MTE_GETGENPROP




ABAP code using 7.40 inline data declarations to call FM BAPI_SYSTEM_MTE_GETGENPROP

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!