VEG_SRV_CREATE_MESSAGE SAP Function module - Error Message Handling

VEG_SRV_CREATE_MESSAGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name VEG_SRV_CREATE_MESSAGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: VEG_SRV
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM VEG_SRV_CREATE_MESSAGE - VEG SRV CREATE MESSAGE

CALL FUNCTION 'VEG_SRV_CREATE_MESSAGE' "Error Message Handling
  EXPORTING
    iv_msg_id =                 " symsgid       Message Class
    iv_msg_number =             " symsgno       Message Number
    iv_msg_type =               " bapi_mtype    Message type: S Success, E Error, W Warning, I Info, A Abort
*   iv_msg_v1 =                 " any           Message Variable
*   iv_msg_v2 =                 " any           Message Variable
*   iv_msg_v3 =                 " any           Message Variable
*   iv_msg_v4 =                 " any           Message Variable
  IMPORTING
    es_message =                " bapiret1      Message
    .  "  VEG_SRV_CREATE_MESSAGE

ABAP code example for Function Module VEG_SRV_CREATE_MESSAGE

The ABAP code below is a full code listing to execute function module VEG_SRV_CREATE_MESSAGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_es_message  
 
 TYPE BAPIRET1
.


DATA(ld_iv_msg_id) = 'some text here'.

DATA(ld_iv_msg_number) = 'Check type of data required'.

DATA(ld_iv_msg_type) = 'some text here'.

DATA(ld_iv_msg_v1) = 'some text here'.

DATA(ld_iv_msg_v2) = 'some text here'.

DATA(ld_iv_msg_v3) = 'some text here'.

DATA(ld_iv_msg_v4) = 'some text here'.
.

CALL FUNCTION 'VEG_SRV_CREATE_MESSAGE'
  EXPORTING
    iv_msg_id =                  ld_iv_msg_id
    iv_msg_number =              ld_iv_msg_number
    iv_msg_type =                ld_iv_msg_type
*   iv_msg_v1 =                  ld_iv_msg_v1
*   iv_msg_v2 =                  ld_iv_msg_v2
*   iv_msg_v3 =                  ld_iv_msg_v3
*   iv_msg_v4 =                  ld_iv_msg_v4
  IMPORTING
    es_message =                 ld_es_message
    .  "  VEG_SRV_CREATE_MESSAGE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_es_message
 
 TYPE BAPIRET1 ,
ld_iv_msg_id
 
 TYPE SYMSGID ,
ld_iv_msg_number
 
 TYPE SYMSGNO ,
ld_iv_msg_type
 
 TYPE BAPI_MTYPE ,
ld_iv_msg_v1
 
 TYPE ANY ,
ld_iv_msg_v2
 
 TYPE ANY ,
ld_iv_msg_v3
 
 TYPE ANY ,
ld_iv_msg_v4
 
 TYPE ANY .


ld_iv_msg_id = 'some text here'.
ld_iv_msg_number = 'Check type of data required'.
ld_iv_msg_type = 'some text here'.
ld_iv_msg_v1 = 'some text here'.
ld_iv_msg_v2 = 'some text here'.
ld_iv_msg_v3 = 'some text here'.
ld_iv_msg_v4 = 'some text here'.