SAP UPX_API_MESSAGE_TEXT Function Module for Get long text for error message
UPX_API_MESSAGE_TEXT is a standard upx api message text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get long text for error message 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 upx api message text FM, simply by entering the name UPX_API_MESSAGE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPX_API
Program Name: SAPLUPX_API
Main Program: SAPLUPX_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UPX_API_MESSAGE_TEXT 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 'UPX_API_MESSAGE_TEXT'"Get long text for error message.
EXPORTING
* I_MSGTY = 'I' "Messages, Message Type
I_MSGNO = "Messages, Message Number
* I_MSGID = 'UPX' "Messages, Message Class
* I_MSGV1 = "Messages, Message Variable
* I_MSGV2 = "Messages, Message Variable
* I_MSGV3 = "Messages, Message Variable
* I_MSGV4 = "Messages, Message Variable
TABLES
* ET_RETURN = "Return Parameter
IMPORTING Parameters details for UPX_API_MESSAGE_TEXT
I_MSGTY - Messages, Message Type
Data type: SY-MSGTYDefault: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGNO - Messages, Message Number
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
I_MSGID - Messages, Message Class
Data type: SY-MSGIDDefault: 'UPX'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV1 - Messages, Message Variable
Data type: SY-MSGV1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV2 - Messages, Message Variable
Data type: SY-MSGV2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV3 - Messages, Message Variable
Data type: SY-MSGV3Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV4 - Messages, Message Variable
Data type: SY-MSGV4Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for UPX_API_MESSAGE_TEXT
ET_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for UPX_API_MESSAGE_TEXT 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_i_msgty | TYPE SY-MSGTY, " 'I' | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_i_msgno | TYPE SY-MSGNO, " | |||
| lv_i_msgid | TYPE SY-MSGID, " 'UPX' | |||
| lv_i_msgv1 | TYPE SY-MSGV1, " | |||
| lv_i_msgv2 | TYPE SY-MSGV2, " | |||
| lv_i_msgv3 | TYPE SY-MSGV3, " | |||
| lv_i_msgv4 | TYPE SY-MSGV4. " |
|   CALL FUNCTION 'UPX_API_MESSAGE_TEXT' "Get long text for error message |
| EXPORTING | ||
| I_MSGTY | = lv_i_msgty | |
| I_MSGNO | = lv_i_msgno | |
| I_MSGID | = lv_i_msgid | |
| I_MSGV1 | = lv_i_msgv1 | |
| I_MSGV2 | = lv_i_msgv2 | |
| I_MSGV3 | = lv_i_msgv3 | |
| I_MSGV4 | = lv_i_msgv4 | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| . " UPX_API_MESSAGE_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM UPX_API_MESSAGE_TEXT
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.| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty). | ||||
| DATA(ld_i_msgty) | = 'I'. | |||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno). | ||||
| "SELECT single MSGID FROM SY INTO @DATA(ld_i_msgid). | ||||
| DATA(ld_i_msgid) | = 'UPX'. | |||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_i_msgv1). | ||||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_i_msgv2). | ||||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_i_msgv3). | ||||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_i_msgv4). | ||||
Search for further information about these or an SAP related objects