SAP OIO_RT_DELIVERY_CHECK Function Module for Check returns delivery









OIO_RT_DELIVERY_CHECK is a standard oio rt delivery check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check returns delivery 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 delivery check FM, simply by entering the name OIO_RT_DELIVERY_CHECK 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_DELIVERY_CHECK 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_DELIVERY_CHECK'"Check returns delivery
EXPORTING
IT_RTITM = "Table of identifiers for returns items
IV_DLVTY = "Delivery type: 1-Return 2-Repeat

IMPORTING
EV_ERROR = "Error found
EV_LOG_HANDLE = "Application Log: Log handle

EXCEPTIONS
INVALID_DELIVERY_TYPE = 1
.



IMPORTING Parameters details for OIO_RT_DELIVERY_CHECK

IT_RTITM - Table of identifiers for returns items

Data type: ROIO_T_RT_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DLVTY - Delivery type: 1-Return 2-Repeat

Data type: FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OIO_RT_DELIVERY_CHECK

EV_ERROR - Error found

Data type: FLAG
Optional: No
Call by Reference: Yes

EV_LOG_HANDLE - Application Log: Log handle

Data type: BALLOGHNDL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_DELIVERY_TYPE - Delivery type is invalid

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIO_RT_DELIVERY_CHECK 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_ev_error  TYPE FLAG, "   
lv_it_rtitm  TYPE ROIO_T_RT_KEY, "   
lv_invalid_delivery_type  TYPE ROIO_T_RT_KEY, "   
lv_iv_dlvty  TYPE FLAG, "   
lv_ev_log_handle  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'OIO_RT_DELIVERY_CHECK'  "Check returns delivery
    EXPORTING
         IT_RTITM = lv_it_rtitm
         IV_DLVTY = lv_iv_dlvty
    IMPORTING
         EV_ERROR = lv_ev_error
         EV_LOG_HANDLE = lv_ev_log_handle
    EXCEPTIONS
        INVALID_DELIVERY_TYPE = 1
. " OIO_RT_DELIVERY_CHECK




ABAP code using 7.40 inline data declarations to call FM OIO_RT_DELIVERY_CHECK

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!