SAP FI_MESSAGE_TEXT_GET Function Module for
FI_MESSAGE_TEXT_GET is a standard fi message text get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi message text get FM, simply by entering the name FI_MESSAGE_TEXT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMSG
Program Name: SAPLFMSG
Main Program: SAPLFMSG
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_MESSAGE_TEXT_GET 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 'FI_MESSAGE_TEXT_GET'".
EXPORTING
* I_LANGU = SY-LANGU "Language Key
I_MSGID = "Message Class
I_MSGNO = "Message Number
* I_MSGTY = "Message Type
* I_MSGV1 = "Message Variable 1
* I_MSGV2 = "Message Variable 2
* I_MSGV3 = "Message Variable 3
* I_MSGV4 = "Message Variable 4
* I_TOTAL = "
IMPORTING
E_MSGTX = "
EXCEPTIONS
NO_MESSAGE_FOUND = 1 MSGID_MISSING = 2 MSGNO_MISSING = 3
IMPORTING Parameters details for FI_MESSAGE_TEXT_GET
I_LANGU - Language Key
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGID - Message Class
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
I_MSGNO - Message Number
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
I_MSGTY - Message Type
Data type: SY-MSGTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV1 - Message Variable 1
Data type: SY-MSGV1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV2 - Message Variable 2
Data type: SY-MSGV2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV3 - Message Variable 3
Data type: SY-MSGV3Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV4 - Message Variable 4
Data type: SY-MSGV4Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TOTAL -
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FI_MESSAGE_TEXT_GET
E_MSGTX -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MESSAGE_FOUND - Message not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSGID_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSGNO_MISSING - No message number specified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FI_MESSAGE_TEXT_GET 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_e_msgtx | TYPE STRING, " | |||
| lv_i_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_no_message_found | TYPE SY, " | |||
| lv_i_msgid | TYPE SY-MSGID, " | |||
| lv_msgid_missing | TYPE SY, " | |||
| lv_i_msgno | TYPE SY-MSGNO, " | |||
| lv_msgno_missing | TYPE SY, " | |||
| lv_i_msgty | TYPE SY-MSGTY, " | |||
| lv_i_msgv1 | TYPE SY-MSGV1, " | |||
| lv_i_msgv2 | TYPE SY-MSGV2, " | |||
| lv_i_msgv3 | TYPE SY-MSGV3, " | |||
| lv_i_msgv4 | TYPE SY-MSGV4, " | |||
| lv_i_total | TYPE XFELD. " |
|   CALL FUNCTION 'FI_MESSAGE_TEXT_GET' " |
| EXPORTING | ||
| I_LANGU | = lv_i_langu | |
| I_MSGID | = lv_i_msgid | |
| I_MSGNO | = lv_i_msgno | |
| I_MSGTY | = lv_i_msgty | |
| I_MSGV1 | = lv_i_msgv1 | |
| I_MSGV2 | = lv_i_msgv2 | |
| I_MSGV3 | = lv_i_msgv3 | |
| I_MSGV4 | = lv_i_msgv4 | |
| I_TOTAL | = lv_i_total | |
| IMPORTING | ||
| E_MSGTX | = lv_e_msgtx | |
| EXCEPTIONS | ||
| NO_MESSAGE_FOUND = 1 | ||
| MSGID_MISSING = 2 | ||
| MSGNO_MISSING = 3 | ||
| . " FI_MESSAGE_TEXT_GET | ||
ABAP code using 7.40 inline data declarations to call FM FI_MESSAGE_TEXT_GET
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 LANGU FROM SY INTO @DATA(ld_i_langu). | ||||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| "SELECT single MSGID FROM SY INTO @DATA(ld_i_msgid). | ||||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty). | ||||
| "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