Hierarchy
SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management⤷
FIN-SEM-BCS (Application Component) Business Consolidation⤷
UCT2 (Package) SEM-BCS: Single Field Selection
Basic Data
| Data Element | UC_SISEL |
| Short Description | Single Selection |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | UC_SISEL | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | UCT200C |
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 | Selection |
| Medium | 20 | Single Selection |
| Long | 25 | Single Selection |
| Heading | 10 | Sel. |
Documentation
Definition
Defines a selection condition for a characteristic. You can define a single selection so that it can be reused in Customizing for consolidation functions.
Note that reuse is not possible in the context of SEM-BPS planning functions.
Use
You can define a single selection as reusable. Then you can reuse this single selection when defining selection conditions in function-specific Customizing (for example, in a reclassification method as well as in an allocation method). For the single selection to be reusable, you have to assign it a technical ID. This ID can have a maximum of 10 characters.
If you only use a selection condition once, then you do not need a reusable single selection. Instead, you can create a non-reusable single selection in the definition of the selection conditions by not entering anything in the technical ID field.
You can use various selection conditions within a single selection:
- Inclusive and exclusive selection of single values and ranges (including use of 'greater than' and 'less than')
- Inclusive and exclusive selection of hierarchies and hierarchy nodes (as long as the characteristic supports hierarchies)
- Selections across characteristics (if there are other characteristics that refer to the same basic characteristic)
Example: In a single selection for the characteristic with the consolidation unit role, you can define the 'Consolidation Unit = Partner Unit' selection condition.
- Selections using attributes of the characteristic. You can define the selection conditions described above for an attribute.
The values of the superordinate fields have to be unique for the single selection. If a superordinate field is one of the permanent parameters, then it is not available as an entry when you define the single selection.
Dependencies
Example
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 320 |
