SAP RH_TASK_CUSTOMIZE Function Module for









RH_TASK_CUSTOMIZE is a standard rh task customize 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 rh task customize FM, simply by entering the name RH_TASK_CUSTOMIZE into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_TASK_CUSTOMIZE 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_CUSTOMIZE'"
EXPORTING
* ACT_COMPONENT_NAME = "
* ACT_FUNCTION_AREA = "
* ACT_TASKGROUP = "
* ACT_PLVAR = "
* ACT_BEGDA = SY-DATUM "
* ACT_ENDDA = '99991231' "

EXCEPTIONS
NO_ACTIVE_PLVAR = 1 NO_FUNCTION_AREA_GIVEN = 2
.



IMPORTING Parameters details for RH_TASK_CUSTOMIZE

ACT_COMPONENT_NAME -

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

ACT_FUNCTION_AREA -

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

ACT_TASKGROUP -

Data type: OBJEC-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_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)

EXCEPTIONS details

NO_ACTIVE_PLVAR -

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

NO_FUNCTION_AREA_GIVEN -

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

Copy and paste ABAP code example for RH_TASK_CUSTOMIZE 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_no_active_plvar  TYPE STRING, "   
lv_act_component_name  TYPE DF14L-PS_POSID, "   
lv_act_function_area  TYPE DF14L-FCTR_ID, "   
lv_no_function_area_given  TYPE DF14L, "   
lv_act_taskgroup  TYPE OBJEC-OBJID, "   
lv_act_plvar  TYPE OBJEC-PLVAR, "   
lv_act_begda  TYPE OBJEC-BEGDA, "   SY-DATUM
lv_act_endda  TYPE OBJEC-ENDDA. "   '99991231'

  CALL FUNCTION 'RH_TASK_CUSTOMIZE'  "
    EXPORTING
         ACT_COMPONENT_NAME = lv_act_component_name
         ACT_FUNCTION_AREA = lv_act_function_area
         ACT_TASKGROUP = lv_act_taskgroup
         ACT_PLVAR = lv_act_plvar
         ACT_BEGDA = lv_act_begda
         ACT_ENDDA = lv_act_endda
    EXCEPTIONS
        NO_ACTIVE_PLVAR = 1
        NO_FUNCTION_AREA_GIVEN = 2
. " RH_TASK_CUSTOMIZE




ABAP code using 7.40 inline data declarations to call FM RH_TASK_CUSTOMIZE

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 PS_POSID FROM DF14L INTO @DATA(ld_act_component_name).
 
"SELECT single FCTR_ID FROM DF14L INTO @DATA(ld_act_function_area).
 
 
"SELECT single OBJID FROM OBJEC INTO @DATA(ld_act_taskgroup).
 
"SELECT single PLVAR FROM OBJEC INTO @DATA(ld_act_plvar).
 
"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'.
 


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!