SAP SALR_MTE_READ_GENERAL Function Module for
SALR_MTE_READ_GENERAL is a standard salr mte read general SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 salr mte read general FM, simply by entering the name SALR_MTE_READ_GENERAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALR
Program Name: SAPLSALR
Main Program: SAPLSALR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SALR_MTE_READ_GENERAL 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 'SALR_MTE_READ_GENERAL'".
EXPORTING
TID = "
IMPORTING
GENERAL_INFO = "
GENERAL_CUSTOMIZATION = "
GENERAL_VALUES = "
COLLECTING_TOOL_DEF = "
ONALERT_TOOL_DEF = "
ANALYZE_TOOL_DEF = "
COLLECTING_TOOL_RUN = "
ONALERT_TOOL_RUN = "
PARENT_INFO = "
TABLES
* ALERTS = "
EXCEPTIONS
INVALID_TID = 1 COMMUNICATION_PROBLEM = 2 INTERNAL_ERROR = 3 OTHER_PROBLEM = 4
IMPORTING Parameters details for SALR_MTE_READ_GENERAL
TID -
Data type: ALGLOBTIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SALR_MTE_READ_GENERAL
GENERAL_INFO -
Data type: SALRMTEGENOptional: No
Call by Reference: No ( called with pass by value option)
GENERAL_CUSTOMIZATION -
Data type: SALRMTECUSOptional: No
Call by Reference: No ( called with pass by value option)
GENERAL_VALUES -
Data type: SALRMTEVALOptional: No
Call by Reference: No ( called with pass by value option)
COLLECTING_TOOL_DEF -
Data type: SALRTLDEFOptional: No
Call by Reference: No ( called with pass by value option)
ONALERT_TOOL_DEF -
Data type: SALRTLDEFOptional: No
Call by Reference: No ( called with pass by value option)
ANALYZE_TOOL_DEF -
Data type: SALRTLDEFOptional: No
Call by Reference: No ( called with pass by value option)
COLLECTING_TOOL_RUN -
Data type: SALRTLRUNOptional: No
Call by Reference: No ( called with pass by value option)
ONALERT_TOOL_RUN -
Data type: SALRTLRUNOptional: No
Call by Reference: No ( called with pass by value option)
PARENT_INFO -
Data type: SALRPARENTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SALR_MTE_READ_GENERAL
ALERTS -
Data type: ALGLOBAIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_TID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_PROBLEM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal error occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER_PROBLEM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SALR_MTE_READ_GENERAL 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 ALGLOBTID, " | |||
lt_alerts | TYPE STANDARD TABLE OF ALGLOBAID, " | |||
lv_invalid_tid | TYPE ALGLOBAID, " | |||
lv_general_info | TYPE SALRMTEGEN, " | |||
lv_communication_problem | TYPE SALRMTEGEN, " | |||
lv_general_customization | TYPE SALRMTECUS, " | |||
lv_general_values | TYPE SALRMTEVAL, " | |||
lv_internal_error | TYPE SALRMTEVAL, " | |||
lv_other_problem | TYPE SALRMTEVAL, " | |||
lv_collecting_tool_def | TYPE SALRTLDEF, " | |||
lv_onalert_tool_def | TYPE SALRTLDEF, " | |||
lv_analyze_tool_def | TYPE SALRTLDEF, " | |||
lv_collecting_tool_run | TYPE SALRTLRUN, " | |||
lv_onalert_tool_run | TYPE SALRTLRUN, " | |||
lv_parent_info | TYPE SALRPARENT. " |
  CALL FUNCTION 'SALR_MTE_READ_GENERAL' " |
EXPORTING | ||
TID | = lv_tid | |
IMPORTING | ||
GENERAL_INFO | = lv_general_info | |
GENERAL_CUSTOMIZATION | = lv_general_customization | |
GENERAL_VALUES | = lv_general_values | |
COLLECTING_TOOL_DEF | = lv_collecting_tool_def | |
ONALERT_TOOL_DEF | = lv_onalert_tool_def | |
ANALYZE_TOOL_DEF | = lv_analyze_tool_def | |
COLLECTING_TOOL_RUN | = lv_collecting_tool_run | |
ONALERT_TOOL_RUN | = lv_onalert_tool_run | |
PARENT_INFO | = lv_parent_info | |
TABLES | ||
ALERTS | = lt_alerts | |
EXCEPTIONS | ||
INVALID_TID = 1 | ||
COMMUNICATION_PROBLEM = 2 | ||
INTERNAL_ERROR = 3 | ||
OTHER_PROBLEM = 4 | ||
. " SALR_MTE_READ_GENERAL |
ABAP code using 7.40 inline data declarations to call FM SALR_MTE_READ_GENERAL
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