SAP UPARI_PROCESS_OTB Function Module for Process OTB message type

Search SAP Function Modules

UPARI_PROCESS_OTB is a standard upari process otb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process OTB message type 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 upari process otb FM, simply by entering the name UPARI_PROCESS_OTB into the relevant SAP transaction such as SE37 or SE38.

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

Function UPARI_PROCESS_OTB 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 'UPARI_PROCESS_OTB'"Process OTB message type
  EXPORTING
*  IT_SELOPT =  "
   I_MODE =  "Single-character flag
   IS_MSGTP =  "Message types

EXCEPTIONS
   MSG_INACTIV = 1    LOG_ERROR = 2    CUSTOM_ERROR = 3    INPUT_PARAM_ERROR = 4    GET_DATA_ERROR = 5    MODIFY_ERROR = 6 

.

IMPORTING Parameters details for UPARI_PROCESS_OTB

IT_SELOPT -

Data type: UPARI_YT_SELOPT
Optional: Yes
Call by Reference: Yes

I_MODE - Single-character flag

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

IS_MSGTP - Message types

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

EXCEPTIONS details

MSG_INACTIV - Message is inactive

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

LOG_ERROR - Error while writing into the application log

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

CUSTOM_ERROR - Error while reading customizing

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

INPUT_PARAM_ERROR - Error in input parameters

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

GET_DATA_ERROR - Error while getting data

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

MODIFY_ERROR - Error while modifying message (in Badi)

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPARI_PROCESS_OTB 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.

ABAP code using 7.40 inline data declarations to call FM UPARI_PROCESS_OTB

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