SAP /MRSS/R3_API_MATERIAL_READ Function Module for Read Material Data
/MRSS/R3_API_MATERIAL_READ is a standard /mrss/r3 api material 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 Read Material Data 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 /mrss/r3 api material read FM, simply by entering the name /MRSS/R3_API_MATERIAL_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: /MRSS/R3_BO_INTERACTION
Program Name: /MRSS/SAPLR3_BO_INTERACTION
Main Program: /MRSS/SAPLR3_BO_INTERACTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /MRSS/R3_API_MATERIAL_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 '/MRSS/R3_API_MATERIAL_READ'"Read Material Data.
EXPORTING
* IV_MATERIAL_ID = "Field length 18
* IV_EQUIPMENT_ID = "Equipment number
* IV_PLANT = "Plant of Work Center
* IV_WORKCENTER = "Work center ID of operation or item
IS_CONTROL_PARAMETERS = "Control Parameters for material selections
* IV_DEMAND_HEADER_GUID = "Demand ID
IMPORTING
ET_MATERIAL_DATA = "Get Material Data
EV_FAILED = "Boolean Variable
ET_MESSAGES = "Message Table
IMPORTING Parameters details for /MRSS/R3_API_MATERIAL_READ
IV_MATERIAL_ID - Field length 18
Data type: MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EQUIPMENT_ID - Equipment number
Data type: CC_EQUNROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PLANT - Plant of Work Center
Data type: /MRSS/T_RSG_WORKCENTER_PLANTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_WORKCENTER - Work center ID of operation or item
Data type: /MRSS/T_RSG_DEM_WORKCENTER_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_CONTROL_PARAMETERS - Control Parameters for material selections
Data type: /MRSS/T_R3_MAT_SELECT_PARAMSOptional: No
Call by Reference: No ( called with pass by value option)
IV_DEMAND_HEADER_GUID - Demand ID
Data type: /MRSS/T_DEM_H_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /MRSS/R3_API_MATERIAL_READ
ET_MATERIAL_DATA - Get Material Data
Data type: /MRSS/T_R3_MATERIAL_DATA_TABOptional: No
Call by Reference: No ( called with pass by value option)
EV_FAILED - Boolean Variable
Data type: /MRSS/T_RSG_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Message Table
Data type: /MRSS/T_R3_MESSAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /MRSS/R3_API_MATERIAL_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_iv_material_id | TYPE MATNR, " | |||
| lv_et_material_data | TYPE /MRSS/T_R3_MATERIAL_DATA_TAB, " | |||
| lv_ev_failed | TYPE /MRSS/T_RSG_BOOLEAN, " | |||
| lv_iv_equipment_id | TYPE CC_EQUNR, " | |||
| lv_iv_plant | TYPE /MRSS/T_RSG_WORKCENTER_PLANT, " | |||
| lv_et_messages | TYPE /MRSS/T_R3_MESSAGE_TAB, " | |||
| lv_iv_workcenter | TYPE /MRSS/T_RSG_DEM_WORKCENTER_ID, " | |||
| lv_is_control_parameters | TYPE /MRSS/T_R3_MAT_SELECT_PARAMS, " | |||
| lv_iv_demand_header_guid | TYPE /MRSS/T_DEM_H_ID. " |
|   CALL FUNCTION '/MRSS/R3_API_MATERIAL_READ' "Read Material Data |
| EXPORTING | ||
| IV_MATERIAL_ID | = lv_iv_material_id | |
| IV_EQUIPMENT_ID | = lv_iv_equipment_id | |
| IV_PLANT | = lv_iv_plant | |
| IV_WORKCENTER | = lv_iv_workcenter | |
| IS_CONTROL_PARAMETERS | = lv_is_control_parameters | |
| IV_DEMAND_HEADER_GUID | = lv_iv_demand_header_guid | |
| IMPORTING | ||
| ET_MATERIAL_DATA | = lv_et_material_data | |
| EV_FAILED | = lv_ev_failed | |
| ET_MESSAGES | = lv_et_messages | |
| . " /MRSS/R3_API_MATERIAL_READ | ||
ABAP code using 7.40 inline data declarations to call FM /MRSS/R3_API_MATERIAL_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