HRHAP_C_MESSAGE_RANGE_FILL SAP Function module

HRHAP_C_MESSAGE_RANGE_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_RANGE_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_RANGE_FILL - HRHAP C MESSAGE RANGE FILL

CALL FUNCTION 'HRHAP_C_MESSAGE_RANGE_FILL' "
* EXPORTING
*   msg_type_s = ' '            " char1         Message Type S
*   msg_type_w = ' '            " char1         Message Type W
*   msg_type_i = ' '            " char1         Message Type I
*   msg_type_e = ' '            " char1         Message Type E
*   msg_type_a = ' '            " char1         Message Type A
  IMPORTING
    t_message_range =           " hap_t_range   Range Table
    .  "  HRHAP_C_MESSAGE_RANGE_FILL

ABAP code example for Function Module HRHAP_C_MESSAGE_RANGE_FILL

The ABAP code below is a full code listing to execute function module HRHAP_C_MESSAGE_RANGE_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_t_message_range  
 
 TYPE HAP_T_RANGE
.


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

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

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

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

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

CALL FUNCTION 'HRHAP_C_MESSAGE_RANGE_FILL'
* EXPORTING
*   msg_type_s =                 ld_msg_type_s
*   msg_type_w =                 ld_msg_type_w
*   msg_type_i =                 ld_msg_type_i
*   msg_type_e =                 ld_msg_type_e
*   msg_type_a =                 ld_msg_type_a
  IMPORTING
    t_message_range =            ld_t_message_range
    .  "  HRHAP_C_MESSAGE_RANGE_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_t_message_range
 
 TYPE HAP_T_RANGE ,
ld_msg_type_s
 
 TYPE CHAR1 ,
ld_msg_type_w
 
 TYPE CHAR1 ,
ld_msg_type_i
 
 TYPE CHAR1 ,
ld_msg_type_e
 
 TYPE CHAR1 ,
ld_msg_type_a
 
 TYPE CHAR1 .


ld_msg_type_s = 'Check type of data required'.
ld_msg_type_w = 'Check type of data required'.
ld_msg_type_i = 'Check type of data required'.
ld_msg_type_e = 'Check type of data required'.
ld_msg_type_a = 'Check type of data required'.