SAP ABAP Data Element BRF_CLASS (Name of Implementing Class)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-SRV-BRF (Application Component) Business Rule Framework
     ⤷ SBRF (Package) Business Rule Framework
Basic Data
Data Element BRF_CLASS
Short Description Name of Implementing Class  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SEOCLSNAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Class 
Medium 15 Impl. Class 
Long 33 Name of Implementing Class 
Heading 33 Name of Implementing Class 
Documentation

Definition

Indicates the name of the runtime class for the current BRF object. With the BRF object, this might be an event, expression, action, rule, or rule set.

Use

To register the runtime class in the BRF, enter the key of the class. The interface that must implement the runtime class depends on the type of the BRF object.

BRF object     Interface

Expression     IF_EXPRESSION_BRF

Action     IF_ACTION_BRF

Event     IF_EVENT_BRF

Rule set     IF_RULESET_BRF

Alternatively, the corresponding basis classes can be derived:

  • CL_EXPRESSION_BASE_BRF
  • CL_ACTION_BASE_BRF,
  • CL_EVENT_BASE_BRF
  • CL_RULESET_BASE_BRF

Dependencies

A maintenance class is also required for every runtime class. In turn, this requires a function group to be able to define its maintenance subscreens.

Example

You can find implementing classes for the mentioned interfaces or basis classes in the packages BRF and BRF_EXAMPLES.

They mainly observe the following naming convention: CL_<name>_<project>. In all BRF objects, "BRF" stands for <project>; in the flight database, this is FLIGHT accordingly.

History
Last changed by/on SAP  20110908 
SAP Release Created in 464