HRHAP_C_MESSAGE_FILL SAP Function module

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

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

Pattern for FM HRHAP_C_MESSAGE_FILL - HRHAP C MESSAGE FILL

CALL FUNCTION 'HRHAP_C_MESSAGE_FILL' "
  EXPORTING
    msgno =                     " char03        Message Number
*   msgv1 =                     " any           Message variable 01
*   msgv2 =                     " any           Message variable 02
*   msgv3 =                     " any           Message variable 03
*   msgv4 =                     " any           Message variable 04
*   fill_variables = ' '        " char1         'X' to use the S_MSG_FIELDS
*   s_msg_fields =              " hap_s_c_ret_struc  Additional Parameters for a Message (e.g. to read Names)
  IMPORTING
    s_return =                  " bal_s_msg     Message Parameters
    .  "  HRHAP_C_MESSAGE_FILL

ABAP code example for Function Module HRHAP_C_MESSAGE_FILL

The ABAP code below is a full code listing to execute function module HRHAP_C_MESSAGE_FILL 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_s_return  
 
 TYPE BAL_S_MSG
.


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

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

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

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

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

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

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

CALL FUNCTION 'HRHAP_C_MESSAGE_FILL'
  EXPORTING
    msgno =                      ld_msgno
*   msgv1 =                      ld_msgv1
*   msgv2 =                      ld_msgv2
*   msgv3 =                      ld_msgv3
*   msgv4 =                      ld_msgv4
*   fill_variables =             ld_fill_variables
*   s_msg_fields =               ld_s_msg_fields
  IMPORTING
    s_return =                   ld_s_return
    .  "  HRHAP_C_MESSAGE_FILL

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_s_return
 
 TYPE BAL_S_MSG ,
ld_msgno
 
 TYPE CHAR03 ,
ld_msgv1
 
 TYPE ANY ,
ld_msgv2
 
 TYPE ANY ,
ld_msgv3
 
 TYPE ANY ,
ld_msgv4
 
 TYPE ANY ,
ld_fill_variables
 
 TYPE CHAR1 ,
ld_s_msg_fields
 
 TYPE HAP_S_C_RET_STRUC .


ld_msgno = 'Check type of data required'.
ld_msgv1 = 'Check type of data required'.
ld_msgv2 = 'Check type of data required'.
ld_msgv3 = 'Check type of data required'.
ld_msgv4 = 'Check type of data required'.
ld_fill_variables = 'Check type of data required'.
ld_s_msg_fields = 'Check type of data required'.