MESSAGE_SET_ACTIVE SAP Function module

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

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

Pattern for FM MESSAGE_SET_ACTIVE - MESSAGE SET ACTIVE

CALL FUNCTION 'MESSAGE_SET_ACTIVE' "
  EXPORTING
    msg_class =                 " sy-msgid
    msg_type =                  " sy-msgty
    msg_number =                " sy-msgno
*   msg_parm1 =                 "
*   msg_parm2 =                 "
*   msg_parm3 =                 "
*   msg_parm4 =                 "
    .  "  MESSAGE_SET_ACTIVE

ABAP code example for Function Module MESSAGE_SET_ACTIVE

The ABAP code below is a full code listing to execute function module MESSAGE_SET_ACTIVE 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_msg_class) = 'some text here'.

DATA(ld_msg_type) = 'some text here'.

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

DATA(ld_msg_parm1) = 'some text here'.

DATA(ld_msg_parm2) = 'some text here'.

DATA(ld_msg_parm3) = 'some text here'.

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

CALL FUNCTION 'MESSAGE_SET_ACTIVE'
  EXPORTING
    msg_class =                  ld_msg_class
    msg_type =                   ld_msg_type
    msg_number =                 ld_msg_number
*   msg_parm1 =                  ld_msg_parm1
*   msg_parm2 =                  ld_msg_parm2
*   msg_parm3 =                  ld_msg_parm3
*   msg_parm4 =                  ld_msg_parm4
    .  "  MESSAGE_SET_ACTIVE

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_msg_class
 
 TYPE SY-MSGID ,
ld_msg_type
 
 TYPE SY-MSGTY ,
ld_msg_number
 
 TYPE SY-MSGNO ,
ld_msg_parm1
 
 TYPE STRING ,
ld_msg_parm2
 
 TYPE STRING ,
ld_msg_parm3
 
 TYPE STRING ,
ld_msg_parm4
 
 TYPE STRING .


ld_msg_class = 'some text here'.
ld_msg_type = 'some text here'.
ld_msg_number = 'Check type of data required'.
ld_msg_parm1 = 'some text here'.
ld_msg_parm2 = 'some text here'.
ld_msg_parm3 = 'some text here'.
ld_msg_parm4 = 'some text here'.