Hierarchy
⤷ BC-SRV-BRF (Application Component) Business Rule Framework
⤷ SBRF (Package) Business Rule Framework
Basic Data
Data Element | BRF_EVENT |
Short Description | Name of Event |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BRF_EVENT | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
Value Table | TBRF110 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | BRF_EVENT | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Event |
Medium | 15 | Event |
Long | 20 | Event |
Heading | 8 | Event |
Documentation
Definition
Point in the application from which the Business Rule Framework (BRF) is called. The call is synchronous. The linkage is fixed. For this reason, BRF events should not be viewed like ABAP objects or the Observer Pattern where an event only represents a loose linkage between two software components.
Use
BRF events are the central point of entry for using the BRF.
You can implement an event at a technical or business event in every application. If such a technical or business event is reached during the program flow in the relevant application, the event is triggeredalong with processing of the associated rules.
You can define any number of rules for each event. You can use these rules to evaluate thecurrent data and make any changes if necessary.
BRF events often bear the context.
Dependencies
Implementation of Events in the Application
You must implement a BRF event in the coding as a method call.
Registration of Events in the BRF
You must register all BRF events in the BRF.Ensure that you only register those events that are actually called.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 464 |