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

Function DFM_CHECK_EVENTS_NEEDED 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 'DFM_CHECK_EVENTS_NEEDED'"Check if event registration is required.
EXPORTING
IS_SOURCE_OBJECT_CONTEXT = "Context of INM object
IMPORTING
EV_RETURN = "Boolean Variable
IMPORTING Parameters details for DFM_CHECK_EVENTS_NEEDED
IS_SOURCE_OBJECT_CONTEXT - Context of INM object
Data type: INM_OBJECT_CONTEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DFM_CHECK_EVENTS_NEEDED
EV_RETURN - Boolean Variable
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DFM_CHECK_EVENTS_NEEDED 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_ev_return | TYPE CHAR1, " | |||
| lv_is_source_object_context | TYPE INM_OBJECT_CONTEXT. " |
|   CALL FUNCTION 'DFM_CHECK_EVENTS_NEEDED' "Check if event registration is required |
| EXPORTING | ||
| IS_SOURCE_OBJECT_CONTEXT | = lv_is_source_object_context | |
| IMPORTING | ||
| EV_RETURN | = lv_ev_return | |
| . " DFM_CHECK_EVENTS_NEEDED | ||
ABAP code using 7.40 inline data declarations to call FM DFM_CHECK_EVENTS_NEEDED
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