SAP J_1I6_MESSAGE_TYPE Function Module for Configurable Message Type is returned
J_1I6_MESSAGE_TYPE is a standard j 1i6 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 for Configurable Message Type is returned 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 j 1i6 message type FM, simply by entering the name J_1I6_MESSAGE_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1I6
Program Name: SAPLJ1I6
Main Program: SAPLJ1I6
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1I6_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 'J_1I6_MESSAGE_TYPE'"Configurable Message Type is returned.
EXPORTING
ARBGB = "Application area
MSGNR = "Message number
CHANGING
DEF_MSGTY = "Message type
IMPORTING Parameters details for J_1I6_MESSAGE_TYPE
ARBGB - Application area
Data type: J_1IMESG-ARBGBOptional: No
Call by Reference: Yes
MSGNR - Message number
Data type: J_1IMESG-MSGNROptional: No
Call by Reference: Yes
CHANGING Parameters details for J_1I6_MESSAGE_TYPE
DEF_MSGTY - Message type
Data type: J_1IMESG-MSGTYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1I6_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_arbgb | TYPE J_1IMESG-ARBGB, " | |||
| lv_def_msgty | TYPE J_1IMESG-MSGTY, " | |||
| lv_msgnr | TYPE J_1IMESG-MSGNR. " |
|   CALL FUNCTION 'J_1I6_MESSAGE_TYPE' "Configurable Message Type is returned |
| EXPORTING | ||
| ARBGB | = lv_arbgb | |
| MSGNR | = lv_msgnr | |
| CHANGING | ||
| DEF_MSGTY | = lv_def_msgty | |
| . " J_1I6_MESSAGE_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM J_1I6_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 ARBGB FROM J_1IMESG INTO @DATA(ld_arbgb). | ||||
| "SELECT single MSGTY FROM J_1IMESG INTO @DATA(ld_def_msgty). | ||||
| "SELECT single MSGNR FROM J_1IMESG INTO @DATA(ld_msgnr). | ||||
Search for further information about these or an SAP related objects