SAP RH_TASK_TYPE_DETERMINE Function Module for Determine Task Type
RH_TASK_TYPE_DETERMINE is a standard rh task type determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Task Type 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 type determine FM, simply by entering the name RH_TASK_TYPE_DETERMINE 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_TYPE_DETERMINE 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_TYPE_DETERMINE'"Determine Task Type.
EXPORTING
* ACT_OTYPE = "
* MULTTASK_HIDE = "
IMPORTING
ACT_OTYPE = "
EXCEPTIONS
TYPE_NOT_SELECTED = 1
IMPORTING Parameters details for RH_TASK_TYPE_DETERMINE
ACT_OTYPE -
Data type: PDTASK-OTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
MULTTASK_HIDE -
Data type: HRI1205-ACTIVEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RH_TASK_TYPE_DETERMINE
ACT_OTYPE -
Data type: PDTASK-OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
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_TYPE_DETERMINE 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_type_not_selected | TYPE PDTASK, " | |||
| lv_multtask_hide | TYPE HRI1205-ACTIVE. " |
|   CALL FUNCTION 'RH_TASK_TYPE_DETERMINE' "Determine Task Type |
| EXPORTING | ||
| ACT_OTYPE | = lv_act_otype | |
| MULTTASK_HIDE | = lv_multtask_hide | |
| IMPORTING | ||
| ACT_OTYPE | = lv_act_otype | |
| EXCEPTIONS | ||
| TYPE_NOT_SELECTED = 1 | ||
| . " RH_TASK_TYPE_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM RH_TASK_TYPE_DETERMINE
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 ACTIVE FROM HRI1205 INTO @DATA(ld_multtask_hide). | ||||
Search for further information about these or an SAP related objects