RH_WF_COPY SAP Function module

RH_WF_COPY 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 RH_WF_COPY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RHTS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RH_WF_COPY - RH WF COPY

CALL FUNCTION 'RH_WF_COPY' "
  EXPORTING
    plvar =                     " objec-plvar   Plan Version
    ref_object =                " hrhctobjc     Reference Object (Object Type/ID)
*   parent =                    " hrhctobjc
*   relation =                  " hrp1001-subty
*   begda = SY-DATUM            " hrp1001-begda  Valid from date
*   endda = '99991231'          " hrp1001-endda  Valid To Date
  IMPORTING
    new_object =                " hrhctextd
  EXCEPTIONS
    OBJECT_NOT_COPIED = 1       "
    RELATION_FAILED = 2         "               Error when creating relationship
    CANCELED = 3                "               Action canceled
    .  "  RH_WF_COPY

ABAP code example for Function Module RH_WF_COPY

The ABAP code below is a full code listing to execute function module RH_WF_COPY 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_new_object  
 
 TYPE HRHCTEXTD
.



DATA(ld_plvar) = some text here

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

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

SELECT single SUBTY 
  FROM HRP1001 
  INTO @DATA(ld_relation).

 

SELECT single BEGDA 
  FROM HRP1001 
  INTO @DATA(ld_begda).

 

SELECT single ENDDA 
  FROM HRP1001 
  INTO @DATA(ld_endda).

.

CALL FUNCTION 'RH_WF_COPY'
  EXPORTING
    plvar =                      ld_plvar
    ref_object =                 ld_ref_object
*   parent =                     ld_parent
*   relation =                   ld_relation
*   begda =                      ld_begda
*   endda =                      ld_endda
  IMPORTING
    new_object =                 ld_new_object
  EXCEPTIONS
    OBJECT_NOT_COPIED =          1
    RELATION_FAILED =            2
    CANCELED =                   3
    .  "  RH_WF_COPY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_new_object
 
 TYPE HRHCTEXTD ,
ld_plvar
 
 TYPE OBJEC-PLVAR ,
ld_ref_object
 
 TYPE HRHCTOBJC ,
ld_parent
 
 TYPE HRHCTOBJC ,
ld_relation
 
 TYPE HRP1001-SUBTY ,
ld_begda
 
 TYPE HRP1001-BEGDA ,
ld_endda
 
 TYPE HRP1001-ENDDA .



ld_plvar = some text here
ld_ref_object = 'Check type of data required'.
ld_parent = 'Check type of data required'.

SELECT single SUBTY 
  FROM HRP1001 
  INTO ld_relation.


SELECT single BEGDA 
  FROM HRP1001 
  INTO ld_begda.


SELECT single ENDDA 
  FROM HRP1001 
  INTO ld_endda.