SAP MSR_TRC_GET_OVERVIEW_DATA Function Module for Get Data for Tracking Overview for remote Calls
MSR_TRC_GET_OVERVIEW_DATA is a standard msr trc get overview data 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 Data for Tracking Overview for remote Calls 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 msr trc get overview data FM, simply by entering the name MSR_TRC_GET_OVERVIEW_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: MSR_TRC_UI
Program Name: SAPLMSR_TRC_UI
Main Program: SAPLMSR_TRC_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MSR_TRC_GET_OVERVIEW_DATA 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 'MSR_TRC_GET_OVERVIEW_DATA'"Get Data for Tracking Overview for remote Calls.
EXPORTING
IV_DOC_TYPE = "Document Type
IV_DOC_NR = "Document Number
IV_DOC_ITEM = "Document Item
IV_MSR_ID = "Process Identification Number
* IV_LANGUAGE = "Language Key
IMPORTING
ET_EXECUTED = "Multi-step returns - main tracking table
ET_OUTTAB = "Multi-Step Returns: Screen Structure for Tracking Details
ET_ITEMS = "Multi-Step Returns: Tracking Overview Item List
ES_HEAD = "Multistep Returns - Tracking Overview Header List
IMPORTING Parameters details for MSR_TRC_GET_OVERVIEW_DATA
IV_DOC_TYPE - Document Type
Data type: MSR_DOC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_DOC_NR - Document Number
Data type: MSR_DOC_NROptional: No
Call by Reference: No ( called with pass by value option)
IV_DOC_ITEM - Document Item
Data type: MSR_DOC_ITEMOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSR_ID - Process Identification Number
Data type: MSR_PROCESS_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_LANGUAGE - Language Key
Data type: SPRASOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MSR_TRC_GET_OVERVIEW_DATA
ET_EXECUTED - Multi-step returns - main tracking table
Data type: MSR_T_EXECUTEDOptional: No
Call by Reference: No ( called with pass by value option)
ET_OUTTAB - Multi-Step Returns: Screen Structure for Tracking Details
Data type: MSR_T_SCR_TRC_DETAILSOptional: No
Call by Reference: No ( called with pass by value option)
ET_ITEMS - Multi-Step Returns: Tracking Overview Item List
Data type: MSR_T_SCR_ITEM_LISTOptional: No
Call by Reference: No ( called with pass by value option)
ES_HEAD - Multistep Returns - Tracking Overview Header List
Data type: MSR_S_SCR_HEAD_LISTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSR_TRC_GET_OVERVIEW_DATA 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_et_executed | TYPE MSR_T_EXECUTED, " | |||
| lv_iv_doc_type | TYPE MSR_DOC_TYPE, " | |||
| lv_et_outtab | TYPE MSR_T_SCR_TRC_DETAILS, " | |||
| lv_iv_doc_nr | TYPE MSR_DOC_NR, " | |||
| lv_et_items | TYPE MSR_T_SCR_ITEM_LIST, " | |||
| lv_iv_doc_item | TYPE MSR_DOC_ITEM, " | |||
| lv_es_head | TYPE MSR_S_SCR_HEAD_LIST, " | |||
| lv_iv_msr_id | TYPE MSR_PROCESS_ID, " | |||
| lv_iv_language | TYPE SPRAS. " |
|   CALL FUNCTION 'MSR_TRC_GET_OVERVIEW_DATA' "Get Data for Tracking Overview for remote Calls |
| EXPORTING | ||
| IV_DOC_TYPE | = lv_iv_doc_type | |
| IV_DOC_NR | = lv_iv_doc_nr | |
| IV_DOC_ITEM | = lv_iv_doc_item | |
| IV_MSR_ID | = lv_iv_msr_id | |
| IV_LANGUAGE | = lv_iv_language | |
| IMPORTING | ||
| ET_EXECUTED | = lv_et_executed | |
| ET_OUTTAB | = lv_et_outtab | |
| ET_ITEMS | = lv_et_items | |
| ES_HEAD | = lv_es_head | |
| . " MSR_TRC_GET_OVERVIEW_DATA | ||
ABAP code using 7.40 inline data declarations to call FM MSR_TRC_GET_OVERVIEW_DATA
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