BRF_MESSAGE_ADD SAP Function module

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

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

Pattern for FM BRF_MESSAGE_ADD - BRF MESSAGE ADD

CALL FUNCTION 'BRF_MESSAGE_ADD' "
* EXPORTING
*   msgid = SY-MSGID            " symsgid       Messages, Message Class
*   msgty = SY-MSGTY            " symsgty       Messages, Message Type
*   msgnr = SY-MSGNO            " symsgno       Messages, Message Number
*   msgv1 = SY-MSGV1            "               Messages, Message Variable
*   msgv2 = SY-MSGV2            "               Messages, Message Variable
*   msgv3 = SY-MSGV3            "               Messages, Message Variable
*   msgv4 = SY-MSGV4            "               Messages, Message Variable
*   fieldname =                 " scrfname      Name of a Screen Element
*   line =                      " sytabix       Internal Tables; Current Line Index
    .  "  BRF_MESSAGE_ADD

ABAP code example for Function Module BRF_MESSAGE_ADD

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

DATA(ld_msgty) = 'some text here'.

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

DATA(ld_msgv1) = 'some text here'.

DATA(ld_msgv2) = 'some text here'.

DATA(ld_msgv3) = 'some text here'.

DATA(ld_msgv4) = 'some text here'.

DATA(ld_fieldname) = 'some text here'.

DATA(ld_line) = '123 '.
.

CALL FUNCTION 'BRF_MESSAGE_ADD'
* EXPORTING
*   msgid =                      ld_msgid
*   msgty =                      ld_msgty
*   msgnr =                      ld_msgnr
*   msgv1 =                      ld_msgv1
*   msgv2 =                      ld_msgv2
*   msgv3 =                      ld_msgv3
*   msgv4 =                      ld_msgv4
*   fieldname =                  ld_fieldname
*   line =                       ld_line
    .  "  BRF_MESSAGE_ADD

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_msgid
 
 TYPE SYMSGID ,
ld_msgty
 
 TYPE SYMSGTY ,
ld_msgnr
 
 TYPE SYMSGNO ,
ld_msgv1
 
 TYPE STRING ,
ld_msgv2
 
 TYPE STRING ,
ld_msgv3
 
 TYPE STRING ,
ld_msgv4
 
 TYPE STRING ,
ld_fieldname
 
 TYPE SCRFNAME ,
ld_line
 
 TYPE SYTABIX .


ld_msgid = 'some text here'.
ld_msgty = 'some text here'.
ld_msgnr = 'Check type of data required'.
ld_msgv1 = 'some text here'.
ld_msgv2 = 'some text here'.
ld_msgv3 = 'some text here'.
ld_msgv4 = 'some text here'.
ld_fieldname = 'some text here'.
ld_line = '123 '.