SAP HR_INDVAL_MESSAGE_HANDLE Function Module for









HR_INDVAL_MESSAGE_HANDLE is a standard hr indval message handle SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr indval message handle FM, simply by entering the name HR_INDVAL_MESSAGE_HANDLE into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_INDVAL_MESSAGE_HANDLE 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 'HR_INDVAL_MESSAGE_HANDLE'"
  EXPORTING
*  MOLGA = '' "
   MSGNO =  "
*  MSGV1 = '' "
*  MSGV2 = '' "
*  MSGV3 = '' "
*  MSGV4 = '' "
*  ACTION = '' "
*  TCLAS = 'A' "
*  PERNR = '00000000' "
*  MODUL = '' "
*  MODSP = '' "
*  LGART = '' "
*  VDATE = '00000000' "
   MSGTY =  "
   MSGID =  "
.



IMPORTING Parameters details for HR_INDVAL_MESSAGE_HANDLE

MOLGA -

Data type: MOLGA
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGNO -

Data type: SYMSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV1 -

Data type:
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV2 -

Data type:
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV3 -

Data type:
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV4 -

Data type:
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACTION -

Data type:
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCLAS -

Data type: TCLAS
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PERNR -

Data type: PERNR_D
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODUL -

Data type: PADIV_MODULE
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODSP -

Data type: PADIV_MODULE_SPEC
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

LGART -

Data type: LGART
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

VDATE -

Data type: DATUM
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGTY -

Data type: SYMSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

MSGID -

Data type: SYMSGID
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HR_INDVAL_MESSAGE_HANDLE 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.

DATA:
lv_molga  TYPE MOLGA, "   ''
lv_msgno  TYPE SYMSGNO, "   
lv_msgv1  TYPE SYMSGNO, "   ''
lv_msgv2  TYPE SYMSGNO, "   ''
lv_msgv3  TYPE SYMSGNO, "   ''
lv_msgv4  TYPE SYMSGNO, "   ''
lv_action  TYPE SYMSGNO, "   ''
lv_tclas  TYPE TCLAS, "   'A'
lv_pernr  TYPE PERNR_D, "   '00000000'
lv_modul  TYPE PADIV_MODULE, "   ''
lv_modsp  TYPE PADIV_MODULE_SPEC, "   ''
lv_lgart  TYPE LGART, "   ''
lv_vdate  TYPE DATUM, "   '00000000'
lv_msgty  TYPE SYMSGTY, "   
lv_msgid  TYPE SYMSGID. "   

  CALL FUNCTION 'HR_INDVAL_MESSAGE_HANDLE'  "
    EXPORTING
         MOLGA = lv_molga
         MSGNO = lv_msgno
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
         ACTION = lv_action
         TCLAS = lv_tclas
         PERNR = lv_pernr
         MODUL = lv_modul
         MODSP = lv_modsp
         LGART = lv_lgart
         VDATE = lv_vdate
         MSGTY = lv_msgty
         MSGID = lv_msgid
. " HR_INDVAL_MESSAGE_HANDLE




ABAP code using 7.40 inline data declarations to call FM HR_INDVAL_MESSAGE_HANDLE

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.

DATA(ld_molga) = ''.
 
 
DATA(ld_msgv1) = ''.
 
DATA(ld_msgv2) = ''.
 
DATA(ld_msgv3) = ''.
 
DATA(ld_msgv4) = ''.
 
DATA(ld_action) = ''.
 
DATA(ld_tclas) = 'A'.
 
DATA(ld_pernr) = '00000000'.
 
DATA(ld_modul) = ''.
 
DATA(ld_modsp) = ''.
 
DATA(ld_lgart) = ''.
 
DATA(ld_vdate) = '00000000'.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!