Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-CEX (Application Component) Customer Enhancements⤷
SECE (Package) Enhancement concept
Basic Data
| Data Element | FLT_EXT |
| Short Description | Enhanceability of a Filter Type for BADI Definitions |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ALTERN | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Enhanceab. |
| Medium | 15 | Enhanceable |
| Long | 21 | Filter Ty.Enhanceable |
| Heading | 21 | Filter Ty.Enhanceable |
Documentation
Definition
The enhanceability of filter types can only be specified for filter-dependent BADI definitions under very special conditions. For example, the doman belonging to the filter type must be linked with a value table that is of the type E or G.
A BADI implementation can then be created in one step by creating a new filter value that is automatically entered into the value table at save and also copied into the transport order of the BADI implementation. In addition, it is also possible to create a new filter value and, at the sam e time, a BADI implementation with the same name. Naturally, you can also specify existing filter values.
You shoud select this feature if there is a prerequisite that a new filter value is created together with a new BADI implementation - that is, that BADI implementations are not created solely with existing filter values, although this, too, is possible.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in | 620 |
