SAP HRHAP_RFC_C_VH_MODIFY Function Module for









HRHAP_RFC_C_VH_MODIFY is a standard hrhap rfc c vh modify 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 hrhap rfc c vh modify FM, simply by entering the name HRHAP_RFC_C_VH_MODIFY into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRHAP_IF_RFC
Program Name: SAPLHRHAP_IF_RFC
Main Program: SAPLHRHAP_IF_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function HRHAP_RFC_C_VH_MODIFY 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 'HRHAP_RFC_C_VH_MODIFY'"
EXPORTING
PLVAR = "
OBJID = "
* BEGDA = '19000101' "
* ENDDA = '99991231' "
STEXT = "
* S_LANGU = SY-LANGU "
S_PARENT = "
* S_HRI5028 = "
* VTASK = 'D' "

IMPORTING
S_RETURN = "

TABLES
* T_PT1002 = "
* T_PT5028 = "
.



IMPORTING Parameters details for HRHAP_RFC_C_VH_MODIFY

PLVAR -

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

OBJID -

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

BEGDA -

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

ENDDA -

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

STEXT -

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

S_LANGU -

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

S_PARENT -

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

S_HRI5028 -

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

VTASK -

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

EXPORTING Parameters details for HRHAP_RFC_C_VH_MODIFY

S_RETURN -

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

TABLES Parameters details for HRHAP_RFC_C_VH_MODIFY

T_PT1002 -

Data type: HAP_T_PT1002
Optional: Yes
Call by Reference: Yes

T_PT5028 -

Data type: HAP_T_PT5028
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for HRHAP_RFC_C_VH_MODIFY 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_plvar  TYPE PLVAR, "   
lv_s_return  TYPE BAPIRET2, "   
lt_t_pt1002  TYPE STANDARD TABLE OF HAP_T_PT1002, "   
lv_objid  TYPE HROBJID, "   
lt_t_pt5028  TYPE STANDARD TABLE OF HAP_T_PT5028, "   
lv_begda  TYPE BEGDATUM, "   '19000101'
lv_endda  TYPE ENDDATUM, "   '99991231'
lv_stext  TYPE STEXT, "   
lv_s_langu  TYPE SPRAS, "   SY-LANGU
lv_s_parent  TYPE HAP_S_PROCESS_ELEMENT_ID, "   
lv_s_hri5028  TYPE HRI5028, "   
lv_vtask  TYPE VTASK. "   'D'

  CALL FUNCTION 'HRHAP_RFC_C_VH_MODIFY'  "
    EXPORTING
         PLVAR = lv_plvar
         OBJID = lv_objid
         BEGDA = lv_begda
         ENDDA = lv_endda
         STEXT = lv_stext
         S_LANGU = lv_s_langu
         S_PARENT = lv_s_parent
         S_HRI5028 = lv_s_hri5028
         VTASK = lv_vtask
    IMPORTING
         S_RETURN = lv_s_return
    TABLES
         T_PT1002 = lt_t_pt1002
         T_PT5028 = lt_t_pt5028
. " HRHAP_RFC_C_VH_MODIFY




ABAP code using 7.40 inline data declarations to call FM HRHAP_RFC_C_VH_MODIFY

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_begda) = '19000101'.
 
DATA(ld_endda) = '99991231'.
 
 
DATA(ld_s_langu) = SY-LANGU.
 
 
 
DATA(ld_vtask) = 'D'.
 


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!