SAP BRF_RAISE_EVENT_SIMPLE_CONTEXT Function Module for
BRF_RAISE_EVENT_SIMPLE_CONTEXT is a standard brf raise event simple context 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 brf raise event simple context FM, simply by entering the name BRF_RAISE_EVENT_SIMPLE_CONTEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BRF_AUX
Program Name: SAPLBRF_AUX
Main Program: SAPLBRF_AUX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BRF_RAISE_EVENT_SIMPLE_CONTEXT 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 'BRF_RAISE_EVENT_SIMPLE_CONTEXT'".
EXPORTING
IV_APPLCLASS = "
IV_EVENT = "
IS_CONTEXT_DATA = "
* IT_TESTVALUES = "
IMPORTING
ET_MESSAGE = "
ET_BRF210 = "
EXCEPTIONS
APPLICATION_CLASS_MISSING = 1 APPLICATION_CLASS_NOT_EXISTING = 2 GENERAL_GET_CONTROLLER_ERROR = 3 EVENT_MISSING = 4 GENERAL_GET_EVENT_ERROR = 5 SET_CONTEXT_ERROR = 6 TESTVALUE_MISSING = 7
IMPORTING Parameters details for BRF_RAISE_EVENT_SIMPLE_CONTEXT
IV_APPLCLASS -
Data type: BRF_APPLCLASSOptional: No
Call by Reference: Yes
IV_EVENT -
Data type: BRF_EVENTOptional: No
Call by Reference: Yes
IS_CONTEXT_DATA -
Data type: ANYOptional: No
Call by Reference: Yes
IT_TESTVALUES -
Data type: CL_EVENT_TEST_BRF=>TY_T_TESTVALUESOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BRF_RAISE_EVENT_SIMPLE_CONTEXT
ET_MESSAGE -
Data type: BRF_MESSAGE_TOptional: No
Call by Reference: Yes
ET_BRF210 -
Data type: SBRF210A_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
APPLICATION_CLASS_MISSING -
Data type:Optional: No
Call by Reference: Yes
APPLICATION_CLASS_NOT_EXISTING -
Data type:Optional: No
Call by Reference: Yes
GENERAL_GET_CONTROLLER_ERROR -
Data type:Optional: No
Call by Reference: Yes
EVENT_MISSING -
Data type:Optional: No
Call by Reference: Yes
GENERAL_GET_EVENT_ERROR -
Data type:Optional: No
Call by Reference: Yes
SET_CONTEXT_ERROR -
Data type:Optional: No
Call by Reference: Yes
TESTVALUE_MISSING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BRF_RAISE_EVENT_SIMPLE_CONTEXT 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_et_message | TYPE BRF_MESSAGE_T, " | |||
| lv_iv_applclass | TYPE BRF_APPLCLASS, " | |||
| lv_application_class_missing | TYPE BRF_APPLCLASS, " | |||
| lv_iv_event | TYPE BRF_EVENT, " | |||
| lv_et_brf210 | TYPE SBRF210A_T, " | |||
| lv_application_class_not_existing | TYPE SBRF210A_T, " | |||
| lv_is_context_data | TYPE ANY, " | |||
| lv_general_get_controller_error | TYPE ANY, " | |||
| lv_event_missing | TYPE ANY, " | |||
| lv_it_testvalues | TYPE CL_EVENT_TEST_BRF=>TY_T_TESTVALUES, " | |||
| lv_general_get_event_error | TYPE CL_EVENT_TEST_BRF=>TY_T_TESTVALUES, " | |||
| lv_set_context_error | TYPE CL_EVENT_TEST_BRF=>TY_T_TESTVALUES, " | |||
| lv_testvalue_missing | TYPE CL_EVENT_TEST_BRF=>TY_T_TESTVALUES. " |
|   CALL FUNCTION 'BRF_RAISE_EVENT_SIMPLE_CONTEXT' " |
| EXPORTING | ||
| IV_APPLCLASS | = lv_iv_applclass | |
| IV_EVENT | = lv_iv_event | |
| IS_CONTEXT_DATA | = lv_is_context_data | |
| IT_TESTVALUES | = lv_it_testvalues | |
| IMPORTING | ||
| ET_MESSAGE | = lv_et_message | |
| ET_BRF210 | = lv_et_brf210 | |
| EXCEPTIONS | ||
| APPLICATION_CLASS_MISSING = 1 | ||
| APPLICATION_CLASS_NOT_EXISTING = 2 | ||
| GENERAL_GET_CONTROLLER_ERROR = 3 | ||
| EVENT_MISSING = 4 | ||
| GENERAL_GET_EVENT_ERROR = 5 | ||
| SET_CONTEXT_ERROR = 6 | ||
| TESTVALUE_MISSING = 7 | ||
| . " BRF_RAISE_EVENT_SIMPLE_CONTEXT | ||
ABAP code using 7.40 inline data declarations to call FM BRF_RAISE_EVENT_SIMPLE_CONTEXT
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