SAP RH_EVENT_COUPLING_CHECK Function Module for









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

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



Function RH_EVENT_COUPLING_CHECK 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_EVENT_COUPLING_CHECK'"
EXPORTING
TASK_OTYPE = "
TASK_OBJID = "
* CLSTYPE = "Object Category
* EVENT_OBJTYP = "
* EVENT_CLSNAM = "Workflow: Type of Objects in Persistent Object References
EVENT_ID = "

IMPORTING
EVENT_ENABLED = "
ICON_NAME = "
ICON_QINFO = "Carrier field for icons
.



IMPORTING Parameters details for RH_EVENT_COUPLING_CHECK

TASK_OTYPE -

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

TASK_OBJID -

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

CLSTYPE - Object Category

Data type: HRS1212-CLSTYP
Optional: Yes
Call by Reference: Yes

EVENT_OBJTYP -

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

EVENT_CLSNAM - Workflow: Type of Objects in Persistent Object References

Data type: HRS1212-CLSNAM
Optional: Yes
Call by Reference: Yes

EVENT_ID -

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

EXPORTING Parameters details for RH_EVENT_COUPLING_CHECK

EVENT_ENABLED -

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

ICON_NAME -

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

ICON_QINFO - Carrier field for icons

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

Copy and paste ABAP code example for RH_EVENT_COUPLING_CHECK 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_task_otype  TYPE HRSOBJECT-OTYPE, "   
lv_event_enabled  TYPE SWETYPEENA-ENABLED, "   
lv_icon_name  TYPE ICON-NAME, "   
lv_task_objid  TYPE ICON, "   
lv_clstype  TYPE HRS1212-CLSTYP, "   
lv_icon_qinfo  TYPE ICONS-TEXT, "   
lv_event_objtyp  TYPE HRS1212-OBJTYP, "   
lv_event_clsnam  TYPE HRS1212-CLSNAM, "   
lv_event_id  TYPE HRS1212-EVENT. "   

  CALL FUNCTION 'RH_EVENT_COUPLING_CHECK'  "
    EXPORTING
         TASK_OTYPE = lv_task_otype
         TASK_OBJID = lv_task_objid
         CLSTYPE = lv_clstype
         EVENT_OBJTYP = lv_event_objtyp
         EVENT_CLSNAM = lv_event_clsnam
         EVENT_ID = lv_event_id
    IMPORTING
         EVENT_ENABLED = lv_event_enabled
         ICON_NAME = lv_icon_name
         ICON_QINFO = lv_icon_qinfo
. " RH_EVENT_COUPLING_CHECK




ABAP code using 7.40 inline data declarations to call FM RH_EVENT_COUPLING_CHECK

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 HRSOBJECT INTO @DATA(ld_task_otype).
 
"SELECT single ENABLED FROM SWETYPEENA INTO @DATA(ld_event_enabled).
 
"SELECT single NAME FROM ICON INTO @DATA(ld_icon_name).
 
 
"SELECT single CLSTYP FROM HRS1212 INTO @DATA(ld_clstype).
 
"SELECT single TEXT FROM ICONS INTO @DATA(ld_icon_qinfo).
 
"SELECT single OBJTYP FROM HRS1212 INTO @DATA(ld_event_objtyp).
 
"SELECT single CLSNAM FROM HRS1212 INTO @DATA(ld_event_clsnam).
 
"SELECT single EVENT FROM HRS1212 INTO @DATA(ld_event_id).
 


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!