SAP KKEK_MESSAGE Function Module for
KKEK_MESSAGE is a standard kkek message 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 kkek message FM, simply by entering the name KKEK_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: KKE6
Program Name: SAPLKKE6
Main Program: SAPLKKE6
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function KKEK_MESSAGE 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 'KKEK_MESSAGE'".
EXPORTING
* APPEND_SAME_MSG = 'X' "
* POSNR = 0 "Item Number of the SD Document
* OBJECT_DEPENDENT = 'X' "Message is Object-Dependent
* CMFE_INTO_SMSG = ' ' "
ARBGB = "
MSGNR = "
MSGTY = "
* MSGV1 = ' ' "Message Parameter 1
* MSGV2 = ' ' "Message Parameter 2
* MSGV3 = ' ' "Message Parameter 3
* MSGV4 = ' ' "Message Parameter 4
* MSG_ON_SCREEN = ' ' "
EXCEPTIONS
MESAGE_TYPE_NOT_VALID = 1 NO_SY_MESSAGE = 2
IMPORTING Parameters details for KKEK_MESSAGE
APPEND_SAME_MSG -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
POSNR - Item Number of the SD Document
Data type: CK_POSNROptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_DEPENDENT - Message is Object-Dependent
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CMFE_INTO_SMSG -
Data type: CMFIMSG-SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARBGB -
Data type: CMIMSG-ARBGBOptional: No
Call by Reference: No ( called with pass by value option)
MSGNR -
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
MSGTY -
Data type: CMIMSG-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
MSGV1 - Message Parameter 1
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV2 - Message Parameter 2
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV3 - Message Parameter 3
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV4 - Message Parameter 4
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSG_ON_SCREEN -
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MESAGE_TYPE_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SY_MESSAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KKEK_MESSAGE 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_append_same_msg | TYPE STRING, " 'X' | |||
lv_mesage_type_not_valid | TYPE STRING, " | |||
lv_posnr | TYPE CK_POSNR, " 0 | |||
lv_object_dependent | TYPE CK_POSNR, " 'X' | |||
lv_cmfe_into_smsg | TYPE CMFIMSG-SELKZ, " SPACE | |||
lv_arbgb | TYPE CMIMSG-ARBGB, " | |||
lv_no_sy_message | TYPE CMIMSG, " | |||
lv_msgnr | TYPE SY-MSGNO, " | |||
lv_msgty | TYPE CMIMSG-MSGTY, " | |||
lv_msgv1 | TYPE CMIMSG, " SPACE | |||
lv_msgv2 | TYPE CMIMSG, " SPACE | |||
lv_msgv3 | TYPE CMIMSG, " SPACE | |||
lv_msgv4 | TYPE CMIMSG, " SPACE | |||
lv_msg_on_screen | TYPE XFLAG. " SPACE |
  CALL FUNCTION 'KKEK_MESSAGE' " |
EXPORTING | ||
APPEND_SAME_MSG | = lv_append_same_msg | |
POSNR | = lv_posnr | |
OBJECT_DEPENDENT | = lv_object_dependent | |
CMFE_INTO_SMSG | = lv_cmfe_into_smsg | |
ARBGB | = lv_arbgb | |
MSGNR | = lv_msgnr | |
MSGTY | = lv_msgty | |
MSGV1 | = lv_msgv1 | |
MSGV2 | = lv_msgv2 | |
MSGV3 | = lv_msgv3 | |
MSGV4 | = lv_msgv4 | |
MSG_ON_SCREEN | = lv_msg_on_screen | |
EXCEPTIONS | ||
MESAGE_TYPE_NOT_VALID = 1 | ||
NO_SY_MESSAGE = 2 | ||
. " KKEK_MESSAGE |
ABAP code using 7.40 inline data declarations to call FM KKEK_MESSAGE
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_append_same_msg) | = 'X'. | |||
DATA(ld_object_dependent) | = 'X'. | |||
"SELECT single SELKZ FROM CMFIMSG INTO @DATA(ld_cmfe_into_smsg). | ||||
DATA(ld_cmfe_into_smsg) | = ' '. | |||
"SELECT single ARBGB FROM CMIMSG INTO @DATA(ld_arbgb). | ||||
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgnr). | ||||
"SELECT single MSGTY FROM CMIMSG INTO @DATA(ld_msgty). | ||||
DATA(ld_msgv1) | = ' '. | |||
DATA(ld_msgv2) | = ' '. | |||
DATA(ld_msgv3) | = ' '. | |||
DATA(ld_msgv4) | = ' '. | |||
DATA(ld_msg_on_screen) | = ' '. | |||
Search for further information about these or an SAP related objects