SAP OIO_RT_PRINT_VIEW Function Module for Get returns data for general output
OIO_RT_PRINT_VIEW is a standard oio rt print view 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 returns data for general output 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 oio rt print view FM, simply by entering the name OIO_RT_PRINT_VIEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIO_RT
Program Name: SAPLOIO_RT
Main Program: SAPLOIO_RT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIO_RT_PRINT_VIEW 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 'OIO_RT_PRINT_VIEW'"Get returns data for general output.
EXPORTING
I_DOCNR = "Returns document number
* I_OPTION_MTL = 'X' "Option - read material returns
* I_OPTION_CTR = 'X' "Option - read container returns
* I_OPTION_FLW = ' ' "Option - read object flow
* I_MTPROF_ID = "Material tracking profile id (reqd for object flow)
IMPORTING
ES_RTHDR = "OLM returns - header screen fields
ET_RTMTL = "OLM returns - material screen fields
ET_RTCTR = "OLM returns - container screen fields
ET_FLOW = "OLM object flow - navigation
ET_OBJECT = "OLM object flow - object details
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for OIO_RT_PRINT_VIEW
I_DOCNR - Returns document number
Data type: OIO_RT_DOCNROptional: No
Call by Reference: No ( called with pass by value option)
I_OPTION_MTL - Option - read material returns
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OPTION_CTR - Option - read container returns
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OPTION_FLW - Option - read object flow
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MTPROF_ID - Material tracking profile id (reqd for object flow)
Data type: OIO_MTPROF_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIO_RT_PRINT_VIEW
ES_RTHDR - OLM returns - header screen fields
Data type: ROIO_RT_RTDOC_SCROptional: No
Call by Reference: No ( called with pass by value option)
ET_RTMTL - OLM returns - material screen fields
Data type: ROIO_T_RT_RTMTL_SCROptional: No
Call by Reference: No ( called with pass by value option)
ET_RTCTR - OLM returns - container screen fields
Data type: ROIO_T_RT_RTCTR_SCROptional: No
Call by Reference: No ( called with pass by value option)
ET_FLOW - OLM object flow - navigation
Data type: ROIO_T_MT_FLOWOptional: No
Call by Reference: No ( called with pass by value option)
ET_OBJECT - OLM object flow - object details
Data type: ROIO_T_MT_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Returns document was not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIO_RT_PRINT_VIEW 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_docnr | TYPE OIO_RT_DOCNR, " | |||
| lv_es_rthdr | TYPE ROIO_RT_RTDOC_SCR, " | |||
| lv_not_found | TYPE ROIO_RT_RTDOC_SCR, " | |||
| lv_et_rtmtl | TYPE ROIO_T_RT_RTMTL_SCR, " | |||
| lv_i_option_mtl | TYPE XFELD, " 'X' | |||
| lv_et_rtctr | TYPE ROIO_T_RT_RTCTR_SCR, " | |||
| lv_i_option_ctr | TYPE XFELD, " 'X' | |||
| lv_et_flow | TYPE ROIO_T_MT_FLOW, " | |||
| lv_i_option_flw | TYPE XFELD, " ' ' | |||
| lv_et_object | TYPE ROIO_T_MT_OBJECT, " | |||
| lv_i_mtprof_id | TYPE OIO_MTPROF_ID. " |
|   CALL FUNCTION 'OIO_RT_PRINT_VIEW' "Get returns data for general output |
| EXPORTING | ||
| I_DOCNR | = lv_i_docnr | |
| I_OPTION_MTL | = lv_i_option_mtl | |
| I_OPTION_CTR | = lv_i_option_ctr | |
| I_OPTION_FLW | = lv_i_option_flw | |
| I_MTPROF_ID | = lv_i_mtprof_id | |
| IMPORTING | ||
| ES_RTHDR | = lv_es_rthdr | |
| ET_RTMTL | = lv_et_rtmtl | |
| ET_RTCTR | = lv_et_rtctr | |
| ET_FLOW | = lv_et_flow | |
| ET_OBJECT | = lv_et_object | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " OIO_RT_PRINT_VIEW | ||
ABAP code using 7.40 inline data declarations to call FM OIO_RT_PRINT_VIEW
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.| DATA(ld_i_option_mtl) | = 'X'. | |||
| DATA(ld_i_option_ctr) | = 'X'. | |||
| DATA(ld_i_option_flw) | = ' '. | |||
Search for further information about these or an SAP related objects