SAP HRHAP_C_VB_COPY Function Module for









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

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



Function HRHAP_C_VB_COPY 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_C_VB_COPY'"
  EXPORTING
   PLVAR =  "Plan Version
   COPIED_OBJID =  "Object ID
*  S_PARENT =  "Parent Information of Element
*  VA_OBJID =  "Object ID
   S_PARENT_TARGET =  "Parent Information of objects
*  PARENT_SUBTY = 'B605' "B605 or B606
*  COPY_WITH_REFERENCES = ' ' "
*  VTASK = 'D' "Type of Update

 IMPORTING
   NEW_OBJID =  "Object ID
   S_RETURN =  "Return Parameter

CHANGING
*  T_ELEMENT_PAIR =  "Appraisal Element Pairs
.



IMPORTING Parameters details for HRHAP_C_VB_COPY

PLVAR - Plan Version

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

COPIED_OBJID - Object ID

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

S_PARENT - Parent Information of Element

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

VA_OBJID - Object ID

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

S_PARENT_TARGET - Parent Information of objects

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

PARENT_SUBTY - B605 or B606

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

COPY_WITH_REFERENCES -

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

VTASK - Type of Update

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

EXPORTING Parameters details for HRHAP_C_VB_COPY

NEW_OBJID - Object ID

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

S_RETURN - Return Parameter

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

CHANGING Parameters details for HRHAP_C_VB_COPY

T_ELEMENT_PAIR - Appraisal Element Pairs

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

Copy and paste ABAP code example for HRHAP_C_VB_COPY 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 HAP_PLAN_VERSION, "   
lv_new_objid  TYPE HROBJID, "   
lv_t_element_pair  TYPE HAP_T_ELEMENT_PAIR, "   
lv_s_return  TYPE BAL_S_MSG, "   
lv_copied_objid  TYPE HROBJID, "   
lv_s_parent  TYPE HAP_S_PARENT, "   
lv_va_objid  TYPE HROBJID, "   
lv_s_parent_target  TYPE HAP_S_PARENT, "   
lv_parent_subty  TYPE SUBTY, "   'B605'
lv_copy_with_references  TYPE CHAR1, "   ' '
lv_vtask  TYPE VTASK. "   'D'

  CALL FUNCTION 'HRHAP_C_VB_COPY'  "
    EXPORTING
         PLVAR = lv_plvar
         COPIED_OBJID = lv_copied_objid
         S_PARENT = lv_s_parent
         VA_OBJID = lv_va_objid
         S_PARENT_TARGET = lv_s_parent_target
         PARENT_SUBTY = lv_parent_subty
         COPY_WITH_REFERENCES = lv_copy_with_references
         VTASK = lv_vtask
    IMPORTING
         NEW_OBJID = lv_new_objid
         S_RETURN = lv_s_return
    CHANGING
         T_ELEMENT_PAIR = lv_t_element_pair
. " HRHAP_C_VB_COPY




ABAP code using 7.40 inline data declarations to call FM HRHAP_C_VB_COPY

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_parent_subty) = 'B605'.
 
DATA(ld_copy_with_references) = ' '.
 
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!