SAP UPARI_PROCESS_MATBAS Function Module for Process product message type
UPARI_PROCESS_MATBAS is a standard upari process matbas 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 product 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 matbas FM, simply by entering the name UPARI_PROCESS_MATBAS into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPARI_FG_MATBAS
Program Name: SAPLUPARI_FG_MATBAS
Main Program: SAPLUPARI_FG_MATBAS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPARI_PROCESS_MATBAS 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_MATBAS'"Process product message type.
EXPORTING
* IT_SELOPT = "
I_MODE = "Single-character flag
* IT_CONTENT_MESSAGE = "
* IT_APPL_MESSAGE = "
* I_SELECT_DATA = ' ' "Single-character flag
* IS_MSGTP = "Message types
IS_PROXY_OUT = "Business information from the perspective of the sender appl
IMPORTING
ET_PRODUCT_RELEASED = "
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_MATBAS
IT_SELOPT -
Data type: UPARI_YT_SELOPTOptional: Yes
Call by Reference: Yes
I_MODE - Single-character flag
Data type: CHAR1Optional: No
Call by Reference: Yes
IT_CONTENT_MESSAGE -
Data type: IF_UPARI_T=>UPARI_YT_MATBAS_MSGOptional: Yes
Call by Reference: Yes
IT_APPL_MESSAGE -
Data type: IF_UPARI_T=>UPARI_YT_APPL_MSGOptional: Yes
Call by Reference: Yes
I_SELECT_DATA - Single-character flag
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
IS_MSGTP - Message types
Data type: UPARI_TC_MSGTPOptional: Yes
Call by Reference: Yes
IS_PROXY_OUT - Business information from the perspective of the sender appl
Data type: BCTCO_BUS_DOC_MSG_HDROptional: No
Call by Reference: Yes
EXPORTING Parameters details for UPARI_PROCESS_MATBAS
ET_PRODUCT_RELEASED -
Data type: IF_UPARI_T=>UPARI_YT_PRODUCTOptional: 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: No ( called with pass by value option)
Copy and paste ABAP code example for UPARI_PROCESS_MATBAS 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_it_selopt | TYPE UPARI_YT_SELOPT, " | |||
| lv_msg_inactiv | TYPE UPARI_YT_SELOPT, " | |||
| lv_et_product_released | TYPE IF_UPARI_T=>UPARI_YT_PRODUCT, " | |||
| lv_i_mode | TYPE CHAR1, " | |||
| lv_log_error | TYPE CHAR1, " | |||
| lv_custom_error | TYPE CHAR1, " | |||
| lv_it_content_message | TYPE IF_UPARI_T=>UPARI_YT_MATBAS_MSG, " | |||
| lv_it_appl_message | TYPE IF_UPARI_T=>UPARI_YT_APPL_MSG, " | |||
| lv_input_param_error | TYPE IF_UPARI_T=>UPARI_YT_APPL_MSG, " | |||
| lv_i_select_data | TYPE CHAR1, " SPACE | |||
| lv_get_data_error | TYPE CHAR1, " | |||
| lv_is_msgtp | TYPE UPARI_TC_MSGTP, " | |||
| lv_modify_error | TYPE UPARI_TC_MSGTP, " | |||
| lv_is_proxy_out | TYPE BCTCO_BUS_DOC_MSG_HDR. " |
|   CALL FUNCTION 'UPARI_PROCESS_MATBAS' "Process product message type |
| EXPORTING | ||
| IT_SELOPT | = lv_it_selopt | |
| I_MODE | = lv_i_mode | |
| IT_CONTENT_MESSAGE | = lv_it_content_message | |
| IT_APPL_MESSAGE | = lv_it_appl_message | |
| I_SELECT_DATA | = lv_i_select_data | |
| IS_MSGTP | = lv_is_msgtp | |
| IS_PROXY_OUT | = lv_is_proxy_out | |
| IMPORTING | ||
| ET_PRODUCT_RELEASED | = lv_et_product_released | |
| EXCEPTIONS | ||
| MSG_INACTIV = 1 | ||
| LOG_ERROR = 2 | ||
| CUSTOM_ERROR = 3 | ||
| INPUT_PARAM_ERROR = 4 | ||
| GET_DATA_ERROR = 5 | ||
| MODIFY_ERROR = 6 | ||
| . " UPARI_PROCESS_MATBAS | ||
ABAP code using 7.40 inline data declarations to call FM UPARI_PROCESS_MATBAS
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_select_data) | = ' '. | |||
Search for further information about these or an SAP related objects