SAP MRTRS320_TRANSFORM_HIST_READ Function Module for NOTRANSL: RMS-MRTRS : Read data of MR transformation history
MRTRS320_TRANSFORM_HIST_READ is a standard mrtrs320 transform hist read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RMS-MRTRS : Read data of MR transformation history 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 mrtrs320 transform hist read FM, simply by entering the name MRTRS320_TRANSFORM_HIST_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: MRTRS320
Program Name: SAPLMRTRS320
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MRTRS320_TRANSFORM_HIST_READ 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 'MRTRS320_TRANSFORM_HIST_READ'"NOTRANSL: RMS-MRTRS : Read data of MR transformation history.
EXPORTING
I_AKTYP = "Activity Type in the Transaction
IS_KEY = "RMS-MRTRS: Key of MR Transformation Header Without MANDT
IMPORTING
ET_TRANSFORM_PAIR = "RMS-MRTRS: Table Type for Structure MRTRSS_TRANSFORM_PAIR
ES_TRANSFORM_HIST = "RMS-MRTRS: Transformation History per Run (Appl Layer)
EXCEPTIONS
KEY_INCOMPLETE = 1 NOT_FOUND = 2 ALREADY_EXIST = 3 SYSTEM_ERROR = 4
IMPORTING Parameters details for MRTRS320_TRANSFORM_HIST_READ
I_AKTYP - Activity Type in the Transaction
Data type: AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
IS_KEY - RMS-MRTRS: Key of MR Transformation Header Without MANDT
Data type: MRTRSS_HDRKEY_NOMANDTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MRTRS320_TRANSFORM_HIST_READ
ET_TRANSFORM_PAIR - RMS-MRTRS: Table Type for Structure MRTRSS_TRANSFORM_PAIR
Data type: MRTRSTY_TRANSFORM_PAIROptional: No
Call by Reference: No ( called with pass by value option)
ES_TRANSFORM_HIST - RMS-MRTRS: Transformation History per Run (Appl Layer)
Data type: MRTRSS_API_TRANSFORM_HISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
KEY_INCOMPLETE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ALREADY_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MRTRS320_TRANSFORM_HIST_READ 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_i_aktyp | TYPE AKTYP, " | |||
| lv_key_incomplete | TYPE AKTYP, " | |||
| lv_et_transform_pair | TYPE MRTRSTY_TRANSFORM_PAIR, " | |||
| lv_is_key | TYPE MRTRSS_HDRKEY_NOMANDT, " | |||
| lv_not_found | TYPE MRTRSS_HDRKEY_NOMANDT, " | |||
| lv_es_transform_hist | TYPE MRTRSS_API_TRANSFORM_HIST, " | |||
| lv_already_exist | TYPE MRTRSS_API_TRANSFORM_HIST, " | |||
| lv_system_error | TYPE MRTRSS_API_TRANSFORM_HIST. " |
|   CALL FUNCTION 'MRTRS320_TRANSFORM_HIST_READ' "NOTRANSL: RMS-MRTRS : Read data of MR transformation history |
| EXPORTING | ||
| I_AKTYP | = lv_i_aktyp | |
| IS_KEY | = lv_is_key | |
| IMPORTING | ||
| ET_TRANSFORM_PAIR | = lv_et_transform_pair | |
| ES_TRANSFORM_HIST | = lv_es_transform_hist | |
| EXCEPTIONS | ||
| KEY_INCOMPLETE = 1 | ||
| NOT_FOUND = 2 | ||
| ALREADY_EXIST = 3 | ||
| SYSTEM_ERROR = 4 | ||
| . " MRTRS320_TRANSFORM_HIST_READ | ||
ABAP code using 7.40 inline data declarations to call FM MRTRS320_TRANSFORM_HIST_READ
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