HR_BR_APPEND_MESSAGE SAP Function module

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

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

Pattern for FM HR_BR_APPEND_MESSAGE - HR BR APPEND MESSAGE

CALL FUNCTION 'HR_BR_APPEND_MESSAGE' "
  EXPORTING
*   message_id = PBR99_ERRID    " sy-msgid
    message_type =              " sy-msgty
    message_number =            " sy-msgno
    message_var1 =              "
    message_var2 =              "
    message_var3 =              "
    message_var4 =              "
    node_type = GC_NODETYPE_MESSAGE  " snodetext-type
*   message_tlevel =            " snodetext-tlevel
    .  "  HR_BR_APPEND_MESSAGE

ABAP code example for Function Module HR_BR_APPEND_MESSAGE

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

DATA(ld_message_type) = 'some text here'.

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

DATA(ld_message_var1) = 'some text here'.

DATA(ld_message_var2) = 'some text here'.

DATA(ld_message_var3) = 'some text here'.

DATA(ld_message_var4) = 'some text here'.


DATA(ld_node_type) = some text here


DATA(ld_message_tlevel) = Check type of data required
.

CALL FUNCTION 'HR_BR_APPEND_MESSAGE'
  EXPORTING
*   message_id =                 ld_message_id
    message_type =               ld_message_type
    message_number =             ld_message_number
    message_var1 =               ld_message_var1
    message_var2 =               ld_message_var2
    message_var3 =               ld_message_var3
    message_var4 =               ld_message_var4
    node_type =                  ld_node_type
*   message_tlevel =             ld_message_tlevel
    .  "  HR_BR_APPEND_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_message_id
 
 TYPE SY-MSGID ,
ld_message_type
 
 TYPE SY-MSGTY ,
ld_message_number
 
 TYPE SY-MSGNO ,
ld_message_var1
 
 TYPE STRING ,
ld_message_var2
 
 TYPE STRING ,
ld_message_var3
 
 TYPE STRING ,
ld_message_var4
 
 TYPE STRING ,
ld_node_type
 
 TYPE SNODETEXT-TYPE ,
ld_message_tlevel
 
 TYPE SNODETEXT-TLEVEL .


ld_message_id = 'some text here'.
ld_message_type = 'some text here'.
ld_message_number = 'Check type of data required'.
ld_message_var1 = 'some text here'.
ld_message_var2 = 'some text here'.
ld_message_var3 = 'some text here'.
ld_message_var4 = 'some text here'.

ld_node_type = some text here

ld_message_tlevel = Check type of data required