SAP ME_TECH_MON_GET_LIST Function Module for Get the values for the OIP1 Subscreen
ME_TECH_MON_GET_LIST is a standard me tech mon get list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get the values for the OIP1 Subscreen 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 me tech mon get list FM, simply by entering the name ME_TECH_MON_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME_TECH_MON
Program Name: SAPLME_TECH_MON
Main Program: SAPLME_TECH_MON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function ME_TECH_MON_GET_LIST 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 'ME_TECH_MON_GET_LIST'"Get the values for the OIP1 Subscreen.
EXPORTING
* IT_USER = "Range table for parameter
IV_NUMBER_OF_LINES = "Number of lines generating for test
* IT_DEVICE_ID = "Range table for parameter
* IT_HGROUP = "Range table for parameter
* IT_STATUS = "Range table for parameter
* IT_SENDDATE = "Range table for parameter
* IT_SENDTIME = "Range table for parameter
* IT_ENDDATE = "Range table for parameter
* IT_ENDTIME = "Range table for parameter
* IV_SIMULATE = "Sent back some random data (self generated)
IMPORTING
ET_RETURN = "ME:ME:Technical Monitor - OIP table
ET_MESSAGES = "Error messages
IMPORTING Parameters details for ME_TECH_MON_GET_LIST
IT_USER - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NUMBER_OF_LINES - Number of lines generating for test
Data type: SYINDEXOptional: No
Call by Reference: No ( called with pass by value option)
IT_DEVICE_ID - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_HGROUP - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_STATUS - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SENDDATE - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SENDTIME - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ENDDATE - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ENDTIME - Range table for parameter
Data type: MEMON_RANGE_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SIMULATE - Sent back some random data (self generated)
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_TECH_MON_GET_LIST
ET_RETURN - ME:ME:Technical Monitor - OIP table
Data type: METECH_MON_OIP_TABOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Error messages
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_TECH_MON_GET_LIST 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_it_user | TYPE MEMON_RANGE_TAB, " | |||
| lv_et_return | TYPE METECH_MON_OIP_TAB, " | |||
| lv_iv_number_of_lines | TYPE SYINDEX, " | |||
| lv_et_messages | TYPE BAPIRET2_T, " | |||
| lv_it_device_id | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_hgroup | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_status | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_senddate | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_sendtime | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_enddate | TYPE MEMON_RANGE_TAB, " | |||
| lv_it_endtime | TYPE MEMON_RANGE_TAB, " | |||
| lv_iv_simulate | TYPE CHAR01. " |
| CALL FUNCTION 'ME_TECH_MON_GET_LIST' "Get the values for the OIP1 Subscreen |
| EXPORTING | ||
| IT_USER | = lv_it_user | |
| IV_NUMBER_OF_LINES | = lv_iv_number_of_lines | |
| IT_DEVICE_ID | = lv_it_device_id | |
| IT_HGROUP | = lv_it_hgroup | |
| IT_STATUS | = lv_it_status | |
| IT_SENDDATE | = lv_it_senddate | |
| IT_SENDTIME | = lv_it_sendtime | |
| IT_ENDDATE | = lv_it_enddate | |
| IT_ENDTIME | = lv_it_endtime | |
| IV_SIMULATE | = lv_iv_simulate | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| ET_MESSAGES | = lv_et_messages | |
| . " ME_TECH_MON_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM ME_TECH_MON_GET_LIST
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