SAP OIUT2_OB_CONTROLLER Function Module for Outbound Controller









OIUT2_OB_CONTROLLER is a standard oiut2 ob controller SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Outbound Controller 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 oiut2 ob controller FM, simply by entering the name OIUT2_OB_CONTROLLER into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIUT2_MAIN
Program Name: SAPLOIUT2_MAIN
Main Program: SAPLOIUT2_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function OIUT2_OB_CONTROLLER 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 'OIUT2_OB_CONTROLLER'"Outbound Controller
EXPORTING
* OBJECT_TYPE = 'FDN' "Object Type
* COMMAND = 'NOTIFY' "Command for interface

EXCEPTIONS
INVALID_OBJECT = 1 INVALID_COMMAND = 2 INVALID_API = 3
.



IMPORTING Parameters details for OIUT2_OB_CONTROLLER

OBJECT_TYPE - Object Type

Data type: OIUT2_OBJECT_TYPE
Default: 'FDN'
Optional: Yes
Call by Reference: No ( called with pass by value option)

COMMAND - Command for interface

Data type: OIUT2_COMMAND
Default: 'NOTIFY'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_OBJECT - Invalid Object

Data type:
Optional: No
Call by Reference: Yes

INVALID_COMMAND - Invalid Command

Data type:
Optional: No
Call by Reference: Yes

INVALID_API - Invalid API

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIUT2_OB_CONTROLLER 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_object_type  TYPE OIUT2_OBJECT_TYPE, "   'FDN'
lv_invalid_object  TYPE OIUT2_OBJECT_TYPE, "   
lv_command  TYPE OIUT2_COMMAND, "   'NOTIFY'
lv_invalid_command  TYPE OIUT2_COMMAND, "   
lv_invalid_api  TYPE OIUT2_COMMAND. "   

  CALL FUNCTION 'OIUT2_OB_CONTROLLER'  "Outbound Controller
    EXPORTING
         OBJECT_TYPE = lv_object_type
         COMMAND = lv_command
    EXCEPTIONS
        INVALID_OBJECT = 1
        INVALID_COMMAND = 2
        INVALID_API = 3
. " OIUT2_OB_CONTROLLER




ABAP code using 7.40 inline data declarations to call FM OIUT2_OB_CONTROLLER

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_object_type) = 'FDN'.
 
 
DATA(ld_command) = 'NOTIFY'.
 
 
 


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!