Hierarchy
⤷ BC-SRV-BRF (Application Component) Business Rule Framework
⤷ SBRF (Package) Business Rule Framework
Basic Data
Data Element | BRF_MNT_CLASS |
Short Description | Maintenance Class for Current BRF Object |
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 | Mnt Class |
Medium | 15 | Mainten. Class |
Long | 20 | Maintenance Class |
Heading | 30 | Maintenance Class |
Documentation
Definition
Name of the maintenance class for the current BRF object (event, expression, action, rule, or rule set).
Use
Enter the key of the maintenance class to register this in the BRF.
For general usage, the maintenance class must implement interface IF_MAINTENANCE_BRF.
If you want to differentiate between individual BRF objects, you can also derive the corresponding basis classes:
BRF objects to maintain Basis class
Expressions CL_EXPRESSION_BASE_MNT_BRF
Actions CL_ACTION_BASE_MNT_BRF
Ereignisse CL_EVENT_BASE_MNT_BRF
Rules CL_RULES_BASE_MNT_BRF
Rule Sets CL_RULESET_BASE_MNT_BRF
Dependencies
A runtime class is also needed for most maintenance classes.
Example
You can find implementing classes for interface IF_MAINTENANCE_BRF or for the specified basis classes in the packages BRF and BRF_EXAMPLES.
They mainly observe the following naming convention: CL_<name>_MNT_<project>. In all BRF objects, the abbreviation "BRF" stands for <project>; in the flight database example, this is FLIGHT.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 464 |