SAP RH_TASK_CREATE Function Module for Create Task









RH_TASK_CREATE is a standard rh task create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Task 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 rh task create FM, simply by entering the name RH_TASK_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_TASK_CREATE 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 'RH_TASK_CREATE'"Create Task
EXPORTING
* ACT_OTYPE = "
* ACT_OBJID = "
* ACT_PLVAR = "
* ACT_ISTAT = '1' "
* ACT_BEGDA = SY-DATUM "
* ACT_ENDDA = '99991231' "
* ACT_SHORT = "
* MULTTASK_HIDE = "

IMPORTING
ACT_OTYPE = "
ACT_OBJID = "

EXCEPTIONS
NO_ACTIVE_PLVAR = 1 TASK_NOT_CREATED = 2 TASK_TYPE_NOT_SELECTED = 3
.



IMPORTING Parameters details for RH_TASK_CREATE

ACT_OTYPE -

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

ACT_OBJID -

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

ACT_PLVAR -

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

ACT_ISTAT -

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

ACT_BEGDA -

Data type: OBJEC-BEGDA
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_ENDDA -

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

ACT_SHORT -

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

MULTTASK_HIDE -

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

EXPORTING Parameters details for RH_TASK_CREATE

ACT_OTYPE -

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

ACT_OBJID -

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

EXCEPTIONS details

NO_ACTIVE_PLVAR -

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

TASK_NOT_CREATED -

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

TASK_TYPE_NOT_SELECTED -

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

Copy and paste ABAP code example for RH_TASK_CREATE 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_act_otype  TYPE PDTASK-OTYPE, "   
lv_act_otype  TYPE PDTASK-OTYPE, "   
lv_no_active_plvar  TYPE PDTASK, "   
lv_act_objid  TYPE PDTASK-OBJID, "   
lv_act_objid  TYPE PDTASK-OBJID, "   
lv_task_not_created  TYPE PDTASK, "   
lv_act_plvar  TYPE OBJEC-PLVAR, "   
lv_task_type_not_selected  TYPE OBJEC, "   
lv_act_istat  TYPE OBJEC-ISTAT, "   '1'
lv_act_begda  TYPE OBJEC-BEGDA, "   SY-DATUM
lv_act_endda  TYPE OBJEC-ENDDA, "   '99991231'
lv_act_short  TYPE OBJEC-SHORT, "   
lv_multtask_hide  TYPE HRI1205-ACTIVE. "   

  CALL FUNCTION 'RH_TASK_CREATE'  "Create Task
    EXPORTING
         ACT_OTYPE = lv_act_otype
         ACT_OBJID = lv_act_objid
         ACT_PLVAR = lv_act_plvar
         ACT_ISTAT = lv_act_istat
         ACT_BEGDA = lv_act_begda
         ACT_ENDDA = lv_act_endda
         ACT_SHORT = lv_act_short
         MULTTASK_HIDE = lv_multtask_hide
    IMPORTING
         ACT_OTYPE = lv_act_otype
         ACT_OBJID = lv_act_objid
    EXCEPTIONS
        NO_ACTIVE_PLVAR = 1
        TASK_NOT_CREATED = 2
        TASK_TYPE_NOT_SELECTED = 3
. " RH_TASK_CREATE




ABAP code using 7.40 inline data declarations to call FM RH_TASK_CREATE

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.

"SELECT single OTYPE FROM PDTASK INTO @DATA(ld_act_otype).
 
"SELECT single OTYPE FROM PDTASK INTO @DATA(ld_act_otype).
 
 
"SELECT single OBJID FROM PDTASK INTO @DATA(ld_act_objid).
 
"SELECT single OBJID FROM PDTASK INTO @DATA(ld_act_objid).
 
 
"SELECT single PLVAR FROM OBJEC INTO @DATA(ld_act_plvar).
 
 
"SELECT single ISTAT FROM OBJEC INTO @DATA(ld_act_istat).
DATA(ld_act_istat) = '1'.
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_act_begda).
DATA(ld_act_begda) = SY-DATUM.
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_act_endda).
DATA(ld_act_endda) = '99991231'.
 
"SELECT single SHORT FROM OBJEC INTO @DATA(ld_act_short).
 
"SELECT single ACTIVE FROM HRI1205 INTO @DATA(ld_multtask_hide).
 


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!