SAP CRM_IST_BRF_EVENT Function Module for
CRM_IST_BRF_EVENT is a standard crm ist brf event 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 crm ist brf event FM, simply by entering the name CRM_IST_BRF_EVENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_BRF
Program Name: SAPLCRM_IST_BRF
Main Program: SAPLCRM_IST_BRF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_BRF_EVENT 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 'CRM_IST_BRF_EVENT'".
EXPORTING
* IV_APPL_CLASS = 'CRM_CFG_SC' "BRF: Application Class
IV_EVENT = "BRF: Event
* IS_CONTEXT = "Structure for Event Context (BRF Flight Demo)
IV_ITEM_GUID = "GUID of a CRM Order Object
* IS_CFG_CONFIG = "
IMPORTING
EV_RESULT_VALUE = "BRF: Result
EV_RESULT_TYPE = "BRF: Result Type
EV_RESULT_CURRENCY = "BRF: Currency Key
EV_RESULT_LENGTH = "BRF: Field Length/Structure Length
EV_RESULT_DECIMALS = "BRF: Decimal Places for Category P
ET_MESSAGE = "BRF: Message - Table Category
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CRM_IST_BRF_EVENT
IV_APPL_CLASS - BRF: Application Class
Data type: BRF_APPLCLASSDefault: 'CRM_CFG_SC'
Optional: Yes
Call by Reference: Yes
IV_EVENT - BRF: Event
Data type: BRF_EVENTOptional: No
Call by Reference: Yes
IS_CONTEXT - Structure for Event Context (BRF Flight Demo)
Data type: CRMT_BRF_EVENT_CONTEXTOptional: Yes
Call by Reference: Yes
IV_ITEM_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IS_CFG_CONFIG -
Data type: COMT_CFGM_CONFIGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_IST_BRF_EVENT
EV_RESULT_VALUE - BRF: Result
Data type: BRF_RESULT_VALUEOptional: No
Call by Reference: Yes
EV_RESULT_TYPE - BRF: Result Type
Data type: BRF_RESULT_TYPEOptional: No
Call by Reference: Yes
EV_RESULT_CURRENCY - BRF: Currency Key
Data type: BRF_CURRENCYOptional: No
Call by Reference: Yes
EV_RESULT_LENGTH - BRF: Field Length/Structure Length
Data type: BRF_RESULT_LENGTHOptional: No
Call by Reference: Yes
EV_RESULT_DECIMALS - BRF: Decimal Places for Category P
Data type: BRF_RESULT_DECIMALSOptional: No
Call by Reference: Yes
ET_MESSAGE - BRF: Message - Table Category
Data type: BRF_MESSAGE_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_BRF_EVENT 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_iv_appl_class | TYPE BRF_APPLCLASS, " 'CRM_CFG_SC' | |||
lv_error_occurred | TYPE BRF_APPLCLASS, " | |||
lv_ev_result_value | TYPE BRF_RESULT_VALUE, " | |||
lv_iv_event | TYPE BRF_EVENT, " | |||
lv_ev_result_type | TYPE BRF_RESULT_TYPE, " | |||
lv_is_context | TYPE CRMT_BRF_EVENT_CONTEXT, " | |||
lv_ev_result_currency | TYPE BRF_CURRENCY, " | |||
lv_iv_item_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_ev_result_length | TYPE BRF_RESULT_LENGTH, " | |||
lv_is_cfg_config | TYPE COMT_CFGM_CONFIG, " | |||
lv_ev_result_decimals | TYPE BRF_RESULT_DECIMALS, " | |||
lv_et_message | TYPE BRF_MESSAGE_T. " |
  CALL FUNCTION 'CRM_IST_BRF_EVENT' " |
EXPORTING | ||
IV_APPL_CLASS | = lv_iv_appl_class | |
IV_EVENT | = lv_iv_event | |
IS_CONTEXT | = lv_is_context | |
IV_ITEM_GUID | = lv_iv_item_guid | |
IS_CFG_CONFIG | = lv_is_cfg_config | |
IMPORTING | ||
EV_RESULT_VALUE | = lv_ev_result_value | |
EV_RESULT_TYPE | = lv_ev_result_type | |
EV_RESULT_CURRENCY | = lv_ev_result_currency | |
EV_RESULT_LENGTH | = lv_ev_result_length | |
EV_RESULT_DECIMALS | = lv_ev_result_decimals | |
ET_MESSAGE | = lv_et_message | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " CRM_IST_BRF_EVENT |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_BRF_EVENT
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.DATA(ld_iv_appl_class) | = 'CRM_CFG_SC'. | |||
Search for further information about these or an SAP related objects