SAP VE_CREATE_MESSAGE Function Module for VE Objects Message handling
VE_CREATE_MESSAGE is a standard ve create message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VE Objects Message handling 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 ve create message FM, simply by entering the name VE_CREATE_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CV_VE_DATA_EXTRACTION
Program Name: SAPLCV_VE_DATA_EXTRACTION
Main Program: SAPLCV_VE_DATA_EXTRACTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VE_CREATE_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 'VE_CREATE_MESSAGE'"VE Objects Message handling.
EXPORTING
* IV_MSG_ID = 'VEOBJ_MESSAGES' "Message Class
IV_MSG_NUMBER = "Message Number
IV_MSG_TYPE = "Message type: S Success, E Error, W Warning, I Info, A Abort
* IV_MSG_V1 = "Message Variable
* IV_MSG_V2 = "Message Variable
* IV_MSG_V3 = "Message Variable
* IV_MSG_V4 = "Message Variable
IMPORTING
ES_MESSAGE = "Return Parameter
IMPORTING Parameters details for VE_CREATE_MESSAGE
IV_MSG_ID - Message Class
Data type: SYMSGIDDefault: 'VEOBJ_MESSAGES'
Optional: Yes
Call by Reference: Yes
IV_MSG_NUMBER - Message Number
Data type: SYMSGNOOptional: No
Call by Reference: Yes
IV_MSG_TYPE - Message type: S Success, E Error, W Warning, I Info, A Abort
Data type: BAPI_MTYPEOptional: No
Call by Reference: Yes
IV_MSG_V1 - Message Variable
Data type: ANYOptional: Yes
Call by Reference: Yes
IV_MSG_V2 - Message Variable
Data type: ANYOptional: Yes
Call by Reference: Yes
IV_MSG_V3 - Message Variable
Data type: ANYOptional: Yes
Call by Reference: Yes
IV_MSG_V4 - Message Variable
Data type: ANYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for VE_CREATE_MESSAGE
ES_MESSAGE - Return Parameter
Data type: BAPIRET1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for VE_CREATE_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_iv_msg_id | TYPE SYMSGID, " 'VEOBJ_MESSAGES' | |||
| lv_es_message | TYPE BAPIRET1, " | |||
| lv_iv_msg_number | TYPE SYMSGNO, " | |||
| lv_iv_msg_type | TYPE BAPI_MTYPE, " | |||
| lv_iv_msg_v1 | TYPE ANY, " | |||
| lv_iv_msg_v2 | TYPE ANY, " | |||
| lv_iv_msg_v3 | TYPE ANY, " | |||
| lv_iv_msg_v4 | TYPE ANY. " |
|   CALL FUNCTION 'VE_CREATE_MESSAGE' "VE Objects Message handling |
| EXPORTING | ||
| IV_MSG_ID | = lv_iv_msg_id | |
| IV_MSG_NUMBER | = lv_iv_msg_number | |
| IV_MSG_TYPE | = lv_iv_msg_type | |
| IV_MSG_V1 | = lv_iv_msg_v1 | |
| IV_MSG_V2 | = lv_iv_msg_v2 | |
| IV_MSG_V3 | = lv_iv_msg_v3 | |
| IV_MSG_V4 | = lv_iv_msg_v4 | |
| IMPORTING | ||
| ES_MESSAGE | = lv_es_message | |
| . " VE_CREATE_MESSAGE | ||
ABAP code using 7.40 inline data declarations to call FM VE_CREATE_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_iv_msg_id) | = 'VEOBJ_MESSAGES'. | |||
Search for further information about these or an SAP related objects