SAP RH_SUGGESTION_MATCHUP Function Module for









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

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



Function RH_SUGGESTION_MATCHUP 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_SUGGESTION_MATCHUP'"
EXPORTING
* BEGIN_DATE = SY-DATUM "
* END_DATE = SY-DATUM "
* SEL_REQ_OBJID = "
* SEL_PERNR = "
* NO_MESSAGE_OUTPUT = "
* AUTO_ASSIGN_FLAG = "
* RULE_ASSIGNMENT = "

TABLES
* ASSIGNMENTS = "
* PTIMEINFO = "
P_PARAM_TAB = "
* REQUEST_TAB = "
.



IMPORTING Parameters details for RH_SUGGESTION_MATCHUP

BEGIN_DATE -

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

END_DATE -

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

SEL_REQ_OBJID -

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

SEL_PERNR -

Data type: OBJEC-OBJID
Optional: Yes
Call by Reference: Yes

NO_MESSAGE_OUTPUT -

Data type:
Optional: Yes
Call by Reference: Yes

AUTO_ASSIGN_FLAG -

Data type:
Optional: Yes
Call by Reference: Yes

RULE_ASSIGNMENT -

Data type: HRSP_RULE_ASSIGNMENT
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for RH_SUGGESTION_MATCHUP

ASSIGNMENTS -

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

PTIMEINFO -

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

P_PARAM_TAB -

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

REQUEST_TAB -

Data type: HRSP_OBJECT_DATE_TAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for RH_SUGGESTION_MATCHUP 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_begin_date  TYPE SY-DATUM, "   SY-DATUM
lt_assignments  TYPE STANDARD TABLE OF SY, "   
lv_end_date  TYPE SY-DATUM, "   SY-DATUM
lt_ptimeinfo  TYPE STANDARD TABLE OF SY, "   
lt_p_param_tab  TYPE STANDARD TABLE OF SY, "   
lv_sel_req_objid  TYPE HRSP_REQ_ASSIGN-REQ_OBJID, "   
lv_sel_pernr  TYPE OBJEC-OBJID, "   
lt_request_tab  TYPE STANDARD TABLE OF HRSP_OBJECT_DATE_TAB, "   
lv_no_message_output  TYPE HRSP_OBJECT_DATE_TAB, "   
lv_auto_assign_flag  TYPE HRSP_OBJECT_DATE_TAB, "   
lv_rule_assignment  TYPE HRSP_RULE_ASSIGNMENT. "   

  CALL FUNCTION 'RH_SUGGESTION_MATCHUP'  "
    EXPORTING
         BEGIN_DATE = lv_begin_date
         END_DATE = lv_end_date
         SEL_REQ_OBJID = lv_sel_req_objid
         SEL_PERNR = lv_sel_pernr
         NO_MESSAGE_OUTPUT = lv_no_message_output
         AUTO_ASSIGN_FLAG = lv_auto_assign_flag
         RULE_ASSIGNMENT = lv_rule_assignment
    TABLES
         ASSIGNMENTS = lt_assignments
         PTIMEINFO = lt_ptimeinfo
         P_PARAM_TAB = lt_p_param_tab
         REQUEST_TAB = lt_request_tab
. " RH_SUGGESTION_MATCHUP




ABAP code using 7.40 inline data declarations to call FM RH_SUGGESTION_MATCHUP

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 DATUM FROM SY INTO @DATA(ld_begin_date).
DATA(ld_begin_date) = SY-DATUM.
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_end_date).
DATA(ld_end_date) = SY-DATUM.
 
 
 
"SELECT single REQ_OBJID FROM HRSP_REQ_ASSIGN INTO @DATA(ld_sel_req_objid).
 
"SELECT single OBJID FROM OBJEC INTO @DATA(ld_sel_pernr).
 
 
 
 
 


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!