SAP /MRSS/R3_API_ORDER_READ Function Module for API to read Order Data from R3









/MRSS/R3_API_ORDER_READ is a standard /mrss/r3 api order 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 API to read Order Data from R3 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 order read FM, simply by entering the name /MRSS/R3_API_ORDER_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_ORDER_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_ORDER_READ'"API to read Order Data from R3
  EXPORTING
   IT_DEMAND_KEYS =  "Table of Header IDs
*  IV_DEMAND_TYPE =  "Demand Type
   IS_CONTROL_PARAMETERS =  "Parameters for Order Data Selection

 IMPORTING
   ET_ORDER_HEADER_DATA =  "Order header data from Demand source system
   ET_ORDER_ITEM_DATA =  "Item Data
   ET_ORDER_LONG_TEXT =  "Order Long text
   ET_ORDER_NOTIFICATIONS =  "Notifications of an order
   EV_FAILED =  "Boolean Variable
   ET_MESSAGES =  "Message Table
.



IMPORTING Parameters details for /MRSS/R3_API_ORDER_READ

IT_DEMAND_KEYS - Table of Header IDs

Data type: /MRSS/T_R3_DEM_KEY_EXT_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DEMAND_TYPE - Demand Type

Data type: /MRSS/T_RSG_DEM_TYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_CONTROL_PARAMETERS - Parameters for Order Data Selection

Data type: /MRSS/T_R3_ORDER_SELECT_PARAMS
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for /MRSS/R3_API_ORDER_READ

ET_ORDER_HEADER_DATA - Order header data from Demand source system

Data type: /MRSS/T_R3_ORDER_HDR_DATA_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

ET_ORDER_ITEM_DATA - Item Data

Data type: /MRSS/T_R3_ORDER_ITEM_DATA_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

ET_ORDER_LONG_TEXT - Order Long text

Data type: /MRSS/T_R3_ORDER_LONG_TEXT_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

ET_ORDER_NOTIFICATIONS - Notifications of an order

Data type: /MRSS/T_R3_ORDER_NOTIF_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

EV_FAILED - Boolean Variable

Data type: /MRSS/T_RSG_BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGES - Message Table

Data type: /MRSS/T_R3_MESSAGE_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for /MRSS/R3_API_ORDER_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_it_demand_keys  TYPE /MRSS/T_R3_DEM_KEY_EXT_TAB, "   
lv_et_order_header_data  TYPE /MRSS/T_R3_ORDER_HDR_DATA_TAB, "   
lv_iv_demand_type  TYPE /MRSS/T_RSG_DEM_TYPE, "   
lv_et_order_item_data  TYPE /MRSS/T_R3_ORDER_ITEM_DATA_TAB, "   
lv_et_order_long_text  TYPE /MRSS/T_R3_ORDER_LONG_TEXT_TAB, "   
lv_is_control_parameters  TYPE /MRSS/T_R3_ORDER_SELECT_PARAMS, "   
lv_et_order_notifications  TYPE /MRSS/T_R3_ORDER_NOTIF_TAB, "   
lv_ev_failed  TYPE /MRSS/T_RSG_BOOLEAN, "   
lv_et_messages  TYPE /MRSS/T_R3_MESSAGE_TAB. "   

  CALL FUNCTION '/MRSS/R3_API_ORDER_READ'  "API to read Order Data from R3
    EXPORTING
         IT_DEMAND_KEYS = lv_it_demand_keys
         IV_DEMAND_TYPE = lv_iv_demand_type
         IS_CONTROL_PARAMETERS = lv_is_control_parameters
    IMPORTING
         ET_ORDER_HEADER_DATA = lv_et_order_header_data
         ET_ORDER_ITEM_DATA = lv_et_order_item_data
         ET_ORDER_LONG_TEXT = lv_et_order_long_text
         ET_ORDER_NOTIFICATIONS = lv_et_order_notifications
         EV_FAILED = lv_ev_failed
         ET_MESSAGES = lv_et_messages
. " /MRSS/R3_API_ORDER_READ




ABAP code using 7.40 inline data declarations to call FM /MRSS/R3_API_ORDER_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!