Hierarchy

⤷

⤷

Basic Data
Data Element | O2GENCLASS |
Short Description | BSP Element: Name of Generated Basis 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 | Bas. Class |
Medium | 19 | Gener. Basis Class |
Long | 32 | Name of Generated Basis Class |
Heading | 0 |
Documentation
Definition
When the BSP extension is activated, the system automatically creates a basis class for every BSP element if no basis class exists or generation-relevant changes were made to the BSP element. For this reason you should never manually change basis classes.
The basis class follows the naming convention CLG_<BSP-Extension>_<BSP-Element>
. (If this name exceeds the maximum of 30 characters, the name is made up of CLG_
followed by a hash value.)
Use
The basis class contains all attributes, defined in the BSP Extension Editor, as class attributes. The option "User-Defined Validation" affects the generation of the class.
It is recommended that you derive the element handler class from the basis class because otherwise changes in the BSP Extension Editor have to be made manually (for example, adding a new attribute).
To avoid inconsistencies in the target system, a transportable BSP extension should always be transported together with all changed basis classes. This means that the basis classes are assigned to the same transport request as the BSP extension by default.
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 620 |