SAP METHOD_GET_MESSAGE_TYPE Function Module for
METHOD_GET_MESSAGE_TYPE is a standard method get message type 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 method get message type FM, simply by entering the name METHOD_GET_MESSAGE_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BD22
Program Name: SAPLBD22
Main Program: SAPLBD22
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function METHOD_GET_MESSAGE_TYPE 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 'METHOD_GET_MESSAGE_TYPE'".
EXPORTING
BOBJTYPE = "
METHOD = "
IMPORTING
MESTYP = "
IMPORTING Parameters details for METHOD_GET_MESSAGE_TYPE
BOBJTYPE -
Data type: BDI_API-BOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
METHOD -
Data type: BDI_API-METHODOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for METHOD_GET_MESSAGE_TYPE
MESTYP -
Data type: BDI_MTYP-MESTYPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for METHOD_GET_MESSAGE_TYPE 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_mestyp | TYPE BDI_MTYP-MESTYP, " | |||
| lv_bobjtype | TYPE BDI_API-BOBJTYPE, " | |||
| lv_method | TYPE BDI_API-METHOD. " |
|   CALL FUNCTION 'METHOD_GET_MESSAGE_TYPE' " |
| EXPORTING | ||
| BOBJTYPE | = lv_bobjtype | |
| METHOD | = lv_method | |
| IMPORTING | ||
| MESTYP | = lv_mestyp | |
| . " METHOD_GET_MESSAGE_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM METHOD_GET_MESSAGE_TYPE
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 MESTYP FROM BDI_MTYP INTO @DATA(ld_mestyp). | ||||
| "SELECT single BOBJTYPE FROM BDI_API INTO @DATA(ld_bobjtype). | ||||
| "SELECT single METHOD FROM BDI_API INTO @DATA(ld_method). | ||||
Search for further information about these or an SAP related objects