SAP ABAP Data Element MLT_USE (Multiple Usability for BADI Definitions)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-CEX (Application Component) Customer Enhancements
⤷
SECE (Package) Enhancement concept
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-CEX (Application Component) Customer Enhancements⤷
SECE (Package) Enhancement concept
Basic Data
| Data Element | MLT_USE |
| Short Description | Multiple Usability 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 | Multiple |
| Medium | 16 | Multi.Usability |
| Long | 20 | Multi.Usability |
| Heading | 16 | Multi.Usability |
Documentation
Definition
Multiple use for BADI definitions means that there can be several active BADI implementations. When there is a call, they are all called up - however, in an unpredictable sequence.
If you have multiple-use BADI definitions, the sequence must not play any role therefore. A typical example is the execution of checks before a save.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in | 620 |
