SAP HRIQ_APPEND_MESSAGE_TABLE Function Module for Fill error message to BAPIRET2 internal table

Search SAP Function Modules

HRIQ_APPEND_MESSAGE_TABLE is a standard hriq append message table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill error message to BAPIRET2 internal table processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for hriq append message table FM, simply by entering the name HRIQ_APPEND_MESSAGE_TABLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRPIQ00ERRORHANDLER
Program Name: SAPLHRPIQ00ERRORHANDLER
Main Program: SAPLHRPIQ00ERRORHANDLER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQ_APPEND_MESSAGE_TABLE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'HRIQ_APPEND_MESSAGE_TABLE'"Fill error message to BAPIRET2 internal table
  EXPORTING
   IV_MSGTYPE =  "Messages, message type
*  IV_PARAMETER =  "Parameter name
*  IV_ROW = 0 "Lines in parameter
*  IV_FIELD =  "Field in parameter
   IV_MSGCLASS =  "Messages, message number
   IV_MSGNUMBER =  "Messages, message number
*  IV_MSGV1 =  "Messages, message variables
*  IV_MSGV2 =  "Messages, message variables
*  IV_MSGV3 =  "Messages, message variables
*  IV_MSGV4 =  "Messages, message variables
*  IV_LOG_NO = ' ' "Application log: log number
*  IV_LOG_MSG_NO = ' ' "Application log: Internal message serial number

CHANGING
   CT_RETURN =  "Return parameter

.

IMPORTING Parameters details for HRIQ_APPEND_MESSAGE_TABLE

IV_MSGTYPE - Messages, message type

Data type: SY-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

IV_PARAMETER - Parameter name

Data type: BAPIRET2-PARAMETER
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ROW - Lines in parameter

Data type: BAPIRET2-ROW
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FIELD - Field in parameter

Data type: BAPIRET2-FIELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MSGCLASS - Messages, message number

Data type: SY-MSGID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_MSGNUMBER - Messages, message number

Data type: SY-MSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

IV_MSGV1 - Messages, message variables

Data type: SY-MSGV1
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MSGV2 - Messages, message variables

Data type: SY-MSGV2
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MSGV3 - Messages, message variables

Data type: SY-MSGV3
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MSGV4 - Messages, message variables

Data type: SY-MSGV4
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_NO - Application log: log number

Data type: BAPIRETURN-LOG_NO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_MSG_NO - Application log: Internal message serial number

Data type: BAPIRETURN-LOG_MSG_NO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for HRIQ_APPEND_MESSAGE_TABLE

CT_RETURN - Return parameter

Data type: BAPIRET2_T
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRIQ_APPEND_MESSAGE_TABLE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM HRIQ_APPEND_MESSAGE_TABLE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects