Hierarchy

⤷

⤷

Basic Data
Data Element | O2TAGCLASS |
Short Description | BSP Element: Name of Element Handler 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 | Handler |
Medium | 20 | Element Handler Cl. |
Long | 30 | Name of Element Handler Class |
Heading | 0 |
Documentation
Definition
The element handler class is the central class of a BSP element. It contains the entire flow logic and controls whether (and if so, what) the BSP element writes to the HTML stream, or whether the content of the BSP element is processed or discarded.
While a BSP page is being processed, the element handler classes are instantiated and specific class methods are called at specified times (see below).
Use
A valid element handler class must implement the interface IF_BSP_ELEMENT
. However, it is recommended that you derive the class from the generated basis class CLG_
..., which contains default implementations of the interface methods and is updated automatically in the case of changes in the BSP Extension Editor.
To implement your own logic you can redefine the interface methods DO_AT_BEGINNING
(call at beginning of element), DO_AT_ITERATION
(call at end of iteration of an element defined correspondingly), or DO_AT_END
(call at end of element).
To execute a user-defined validation the interface methods COMPILE_TIME_IS_VALID
and RUNTIME_IS_VALID
are available. These must be redefined.
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 620 |