SAP OIO_NV_RMTL_TO_LIPS Function Module for Tracking: Material return to delivery item
OIO_NV_RMTL_TO_LIPS is a standard oio nv rmtl to lips SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Tracking: Material return to delivery item 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 nv rmtl to lips FM, simply by entering the name OIO_NV_RMTL_TO_LIPS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIO_NR
Program Name: SAPLOIO_NR
Main Program: SAPLOIO_NR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIO_NV_RMTL_TO_LIPS 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_NV_RMTL_TO_LIPS'"Tracking: Material return to delivery item.
EXPORTING
IS_PARENT = "Document flow parent object
IMPORTING
ET_CHILD = "Document flow objects
IMPORTING Parameters details for OIO_NV_RMTL_TO_LIPS
IS_PARENT - Document flow parent object
Data type: ROIO_OBJECT_PARENTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for OIO_NV_RMTL_TO_LIPS
ET_CHILD - Document flow objects
Data type: ROIO_T_OBJECTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIO_NV_RMTL_TO_LIPS 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_child | TYPE ROIO_T_OBJECT, " | |||
| lv_is_parent | TYPE ROIO_OBJECT_PARENT. " |
|   CALL FUNCTION 'OIO_NV_RMTL_TO_LIPS' "Tracking: Material return to delivery item |
| EXPORTING | ||
| IS_PARENT | = lv_is_parent | |
| IMPORTING | ||
| ET_CHILD | = lv_et_child | |
| . " OIO_NV_RMTL_TO_LIPS | ||
ABAP code using 7.40 inline data declarations to call FM OIO_NV_RMTL_TO_LIPS
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