SAP EHHSS_RFC_RAS_REQUEST Function Module for Risk Assessment Request
EHHSS_RFC_RAS_REQUEST is a standard ehhss rfc ras request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Risk Assessment Request 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 ehhss rfc ras request FM, simply by entering the name EHHSS_RFC_RAS_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHHSS_EXT_RAS
Program Name: SAPLEHHSS_EXT_RAS
Main Program: SAPLEHHSS_EXT_RAS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EHHSS_RFC_RAS_REQUEST 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 'EHHSS_RFC_RAS_REQUEST'"Risk Assessment Request.
EXPORTING
IV_REQUESTER_TYPE_CODE = "Type of Requester for Risk Assessment Request
* IV_CONTEXT_OBJECT_ID = "Object ID of Risk-Relevant Object
* IV_PRIORITY_CODE = "Priority of Risk Assessment Request
* IV_DUE_DATE_TIME = "Due Date and Time for Risk Assessment Request (with time zone UTC)
IV_REQUESTER_REQUEST_ID = "Request ID of requester for Risk Assessment Request
* IV_REQUESTER_REQUEST_NAME = "Request Name of requester for Risk Assessment Request
* IV_REQUESTER_ID = "ID given by requester for Risk Assessment Request
IV_REQUEST_TRIGGER_EVENT = "Triggering Event for Risk Assessment Request
* IV_REQUEST_DESCRIPTION = "Description of Risk Assessment Request
* IV_REQUEST_DESCR_LANGU = "Language Key External (according to ISO 639)
* IV_PROPOSED_PROCESSOR = "Proposed Processor for Risk Assessment Request
* IV_CONTEXT_OBJECT_TYPE = "Object Type of Risk-Relevant Object
IMPORTING
EV_RAS_REQUEST_WF_REF_ID = "Reference ID of workflow for risk assessment request
TABLES
* ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for EHHSS_RFC_RAS_REQUEST
IV_REQUESTER_TYPE_CODE - Type of Requester for Risk Assessment Request
Data type: EHHSS_RAS_REQ_TYPE_CODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_CONTEXT_OBJECT_ID - Object ID of Risk-Relevant Object
Data type: EHHSS_RAS_REQ_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PRIORITY_CODE - Priority of Risk Assessment Request
Data type: EHHSS_RAS_REQ_PRIO_CODEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DUE_DATE_TIME - Due Date and Time for Risk Assessment Request (with time zone UTC)
Data type: EHHSS_RAS_REQ_DUE_DATE_TIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REQUESTER_REQUEST_ID - Request ID of requester for Risk Assessment Request
Data type: EHHSS_RAS_REQ_REQUEST_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_REQUESTER_REQUEST_NAME - Request Name of requester for Risk Assessment Request
Data type: EHHSS_RAS_REQ_REQUEST_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REQUESTER_ID - ID given by requester for Risk Assessment Request
Data type: EHHSS_RAS_REQ_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REQUEST_TRIGGER_EVENT - Triggering Event for Risk Assessment Request
Data type: EHHSS_RAS_REQ_TRIGGER_EVENTOptional: No
Call by Reference: No ( called with pass by value option)
IV_REQUEST_DESCRIPTION - Description of Risk Assessment Request
Data type: EHHSS_RAS_REQ_DESCROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REQUEST_DESCR_LANGU - Language Key External (according to ISO 639)
Data type: EHFND_LANGU_EXTERN_ISOOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PROPOSED_PROCESSOR - Proposed Processor for Risk Assessment Request
Data type: EHHSS_RAS_REQ_PROCESSOROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONTEXT_OBJECT_TYPE - Object Type of Risk-Relevant Object
Data type: EHHSS_RAS_REQ_OBJECT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EHHSS_RFC_RAS_REQUEST
EV_RAS_REQUEST_WF_REF_ID - Reference ID of workflow for risk assessment request
Data type: EHHSS_RAS_REQ_WF_REF_IDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EHHSS_RFC_RAS_REQUEST
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EHHSS_RFC_RAS_REQUEST 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: | ||||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_requester_type_code | TYPE EHHSS_RAS_REQ_TYPE_CODE, " | |||
| lv_ev_ras_request_wf_ref_id | TYPE EHHSS_RAS_REQ_WF_REF_ID, " | |||
| lv_iv_context_object_id | TYPE EHHSS_RAS_REQ_OBJECT_ID, " | |||
| lv_iv_priority_code | TYPE EHHSS_RAS_REQ_PRIO_CODE, " | |||
| lv_iv_due_date_time | TYPE EHHSS_RAS_REQ_DUE_DATE_TIME, " | |||
| lv_iv_requester_request_id | TYPE EHHSS_RAS_REQ_REQUEST_ID, " | |||
| lv_iv_requester_request_name | TYPE EHHSS_RAS_REQ_REQUEST_NAME, " | |||
| lv_iv_requester_id | TYPE EHHSS_RAS_REQ_ID, " | |||
| lv_iv_request_trigger_event | TYPE EHHSS_RAS_REQ_TRIGGER_EVENT, " | |||
| lv_iv_request_description | TYPE EHHSS_RAS_REQ_DESCR, " | |||
| lv_iv_request_descr_langu | TYPE EHFND_LANGU_EXTERN_ISO, " | |||
| lv_iv_proposed_processor | TYPE EHHSS_RAS_REQ_PROCESSOR, " | |||
| lv_iv_context_object_type | TYPE EHHSS_RAS_REQ_OBJECT_TYPE. " |
|   CALL FUNCTION 'EHHSS_RFC_RAS_REQUEST' "Risk Assessment Request |
| EXPORTING | ||
| IV_REQUESTER_TYPE_CODE | = lv_iv_requester_type_code | |
| IV_CONTEXT_OBJECT_ID | = lv_iv_context_object_id | |
| IV_PRIORITY_CODE | = lv_iv_priority_code | |
| IV_DUE_DATE_TIME | = lv_iv_due_date_time | |
| IV_REQUESTER_REQUEST_ID | = lv_iv_requester_request_id | |
| IV_REQUESTER_REQUEST_NAME | = lv_iv_requester_request_name | |
| IV_REQUESTER_ID | = lv_iv_requester_id | |
| IV_REQUEST_TRIGGER_EVENT | = lv_iv_request_trigger_event | |
| IV_REQUEST_DESCRIPTION | = lv_iv_request_description | |
| IV_REQUEST_DESCR_LANGU | = lv_iv_request_descr_langu | |
| IV_PROPOSED_PROCESSOR | = lv_iv_proposed_processor | |
| IV_CONTEXT_OBJECT_TYPE | = lv_iv_context_object_type | |
| IMPORTING | ||
| EV_RAS_REQUEST_WF_REF_ID | = lv_ev_ras_request_wf_ref_id | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| . " EHHSS_RFC_RAS_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM EHHSS_RFC_RAS_REQUEST
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.Search for further information about these or an SAP related objects