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

Function GRFN_EVENT_RECEIVE 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 'GRFN_EVENT_RECEIVE'"Event receive.
EXPORTING
EVENT_TYPE = "Event Type
PARTNER = "Partner
VERSION = "Event Version
* ORIGINATING_SYSTEM = "Originating System
* OCCURRED_TIME = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
* ORIGINATING_EVENT_ID = "External Event ID
DETAIL = "value set
IMPORTING
RETURN_CODE = "Return Value of ABAP Statements
MESSAGE = "Message
IMPORTING Parameters details for GRFN_EVENT_RECEIVE
EVENT_TYPE - Event Type
Data type: GRFN_EVENTTYPEOptional: No
Call by Reference: No ( called with pass by value option)
PARTNER - Partner
Data type: GRFN_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
VERSION - Event Version
Data type: GRFN_EVENTVEROptional: No
Call by Reference: No ( called with pass by value option)
ORIGINATING_SYSTEM - Originating System
Data type: GRFN_SYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
OCCURRED_TIME - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TIMESTAMPOptional: Yes
Call by Reference: No ( called with pass by value option)
ORIGINATING_EVENT_ID - External Event ID
Data type: GRFN_EXTERNALEVENTIDOptional: Yes
Call by Reference: No ( called with pass by value option)
DETAIL - value set
Data type: GRFN_T_NAMEVALUEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRFN_EVENT_RECEIVE
RETURN_CODE - Return Value of ABAP Statements
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE - Message
Data type: GRFN_T_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRFN_EVENT_RECEIVE 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_event_type | TYPE GRFN_EVENTTYPE, " | |||
| lv_return_code | TYPE SYSUBRC, " | |||
| lv_message | TYPE GRFN_T_MESSAGE, " | |||
| lv_partner | TYPE GRFN_PARTNER, " | |||
| lv_version | TYPE GRFN_EVENTVER, " | |||
| lv_originating_system | TYPE GRFN_SYSTEM, " | |||
| lv_occurred_time | TYPE TIMESTAMP, " | |||
| lv_originating_event_id | TYPE GRFN_EXTERNALEVENTID, " | |||
| lv_detail | TYPE GRFN_T_NAMEVALUE. " |
|   CALL FUNCTION 'GRFN_EVENT_RECEIVE' "Event receive |
| EXPORTING | ||
| EVENT_TYPE | = lv_event_type | |
| PARTNER | = lv_partner | |
| VERSION | = lv_version | |
| ORIGINATING_SYSTEM | = lv_originating_system | |
| OCCURRED_TIME | = lv_occurred_time | |
| ORIGINATING_EVENT_ID | = lv_originating_event_id | |
| DETAIL | = lv_detail | |
| IMPORTING | ||
| RETURN_CODE | = lv_return_code | |
| MESSAGE | = lv_message | |
| . " GRFN_EVENT_RECEIVE | ||
ABAP code using 7.40 inline data declarations to call FM GRFN_EVENT_RECEIVE
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