ISU_MSG_PUT SAP Function module

ISU_MSG_PUT 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 ISU_MSG_PUT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISU_MSG_PUT - ISU MSG PUT

CALL FUNCTION 'ISU_MSG_PUT' "
  EXPORTING
*   x_handle =                  " emsg_handl
    x_msg_typ = CO_MSG_ERROR    " emsg_typ
    x_msg_id =                  " symsgid
    x_msg_no =                  " symsgno
    x_msg_v1 =                  "
    x_msg_v2 =                  "
    x_msg_v3 =                  "
    x_msg_v4 =                  "
*   x_log_only =                " kennzx
*   x_raise = SPACE             " kennzx
  EXCEPTIONS
    DUMMY_EXCEPTION = 1         "
    .  "  ISU_MSG_PUT

ABAP code example for Function Module ISU_MSG_PUT

The ABAP code below is a full code listing to execute function module ISU_MSG_PUT 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_x_handle) = 'Check type of data required'.

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

DATA(ld_x_msg_id) = 'some text here'.

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

DATA(ld_x_msg_v1) = 'some text here'.

DATA(ld_x_msg_v2) = 'some text here'.

DATA(ld_x_msg_v3) = 'some text here'.

DATA(ld_x_msg_v4) = 'some text here'.

DATA(ld_x_log_only) = 'some text here'.

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

CALL FUNCTION 'ISU_MSG_PUT'
  EXPORTING
*   x_handle =                   ld_x_handle
    x_msg_typ =                  ld_x_msg_typ
    x_msg_id =                   ld_x_msg_id
    x_msg_no =                   ld_x_msg_no
    x_msg_v1 =                   ld_x_msg_v1
    x_msg_v2 =                   ld_x_msg_v2
    x_msg_v3 =                   ld_x_msg_v3
    x_msg_v4 =                   ld_x_msg_v4
*   x_log_only =                 ld_x_log_only
*   x_raise =                    ld_x_raise
  EXCEPTIONS
    DUMMY_EXCEPTION =            1
    .  "  ISU_MSG_PUT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_x_handle
 
 TYPE EMSG_HANDL ,
ld_x_msg_typ
 
 TYPE EMSG_TYP ,
ld_x_msg_id
 
 TYPE SYMSGID ,
ld_x_msg_no
 
 TYPE SYMSGNO ,
ld_x_msg_v1
 
 TYPE STRING ,
ld_x_msg_v2
 
 TYPE STRING ,
ld_x_msg_v3
 
 TYPE STRING ,
ld_x_msg_v4
 
 TYPE STRING ,
ld_x_log_only
 
 TYPE KENNZX ,
ld_x_raise
 
 TYPE KENNZX .


ld_x_handle = 'some text here'.
ld_x_msg_typ = 'some text here'.
ld_x_msg_id = 'some text here'.
ld_x_msg_no = 'Check type of data required'.
ld_x_msg_v1 = 'some text here'.
ld_x_msg_v2 = 'some text here'.
ld_x_msg_v3 = 'some text here'.
ld_x_msg_v4 = 'some text here'.
ld_x_log_only = 'some text here'.
ld_x_raise = 'some text here'.