SAP RH_CHECK_FORWARDING Function Module for









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

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



Function RH_CHECK_FORWARDING 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_CHECK_FORWARDING'"
  EXPORTING
*  ACT_WI_ID =  "
   ACT_AGENT_OTYPE =  "
   ACT_AGENT_OBJID =  "
   ACT_TASK_OTYPE =  "
   ACT_TASK_OBJID =  "
*  ACT_DATE = SY-DATUM "
*  SEND_MESSAGE =  "
*  UPDATE_INDEX =  "

 IMPORTING
   FORWARDING_WITHOUT_TASK =  "

TABLES
*  EXCLUDED_AGENTS =  "

EXCEPTIONS
   FORWARD_NOT_POSSIBLE = 1    EXCLUDED_AGENT = 2
.



IMPORTING Parameters details for RH_CHECK_FORWARDING

ACT_WI_ID -

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

ACT_AGENT_OTYPE -

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

ACT_AGENT_OBJID -

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

ACT_TASK_OTYPE -

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

ACT_TASK_OBJID -

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

ACT_DATE -

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

SEND_MESSAGE -

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

UPDATE_INDEX -

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

EXPORTING Parameters details for RH_CHECK_FORWARDING

FORWARDING_WITHOUT_TASK -

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

TABLES Parameters details for RH_CHECK_FORWARDING

EXCLUDED_AGENTS -

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

EXCEPTIONS details

FORWARD_NOT_POSSIBLE -

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

EXCLUDED_AGENT -

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

Copy and paste ABAP code example for RH_CHECK_FORWARDING 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_wi_id  TYPE SWWWIHEAD-WI_ID, "   
lt_excluded_agents  TYPE STANDARD TABLE OF SWHACTOR, "   
lv_forward_not_possible  TYPE SWHACTOR, "   
lv_forwarding_without_task  TYPE HRPP0C-TEST, "   
lv_excluded_agent  TYPE HRPP0C, "   
lv_act_agent_otype  TYPE SWHACTOR-OTYPE, "   
lv_act_agent_objid  TYPE SWHACTOR, "   
lv_act_task_otype  TYPE SWHACTOR-OTYPE, "   
lv_act_task_objid  TYPE SWHACTOR, "   
lv_act_date  TYPE SY-DATUM, "   SY-DATUM
lv_send_message  TYPE HRPP0C-TEST, "   
lv_update_index  TYPE HRPP0C-TEST. "   

  CALL FUNCTION 'RH_CHECK_FORWARDING'  "
    EXPORTING
         ACT_WI_ID = lv_act_wi_id
         ACT_AGENT_OTYPE = lv_act_agent_otype
         ACT_AGENT_OBJID = lv_act_agent_objid
         ACT_TASK_OTYPE = lv_act_task_otype
         ACT_TASK_OBJID = lv_act_task_objid
         ACT_DATE = lv_act_date
         SEND_MESSAGE = lv_send_message
         UPDATE_INDEX = lv_update_index
    IMPORTING
         FORWARDING_WITHOUT_TASK = lv_forwarding_without_task
    TABLES
         EXCLUDED_AGENTS = lt_excluded_agents
    EXCEPTIONS
        FORWARD_NOT_POSSIBLE = 1
        EXCLUDED_AGENT = 2
. " RH_CHECK_FORWARDING




ABAP code using 7.40 inline data declarations to call FM RH_CHECK_FORWARDING

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 WI_ID FROM SWWWIHEAD INTO @DATA(ld_act_wi_id).
 
 
 
"SELECT single TEST FROM HRPP0C INTO @DATA(ld_forwarding_without_task).
 
 
"SELECT single OTYPE FROM SWHACTOR INTO @DATA(ld_act_agent_otype).
 
 
"SELECT single OTYPE FROM SWHACTOR INTO @DATA(ld_act_task_otype).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_act_date).
DATA(ld_act_date) = SY-DATUM.
 
"SELECT single TEST FROM HRPP0C INTO @DATA(ld_send_message).
 
"SELECT single TEST FROM HRPP0C INTO @DATA(ld_update_index).
 


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!