Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-MTD (Application Component) Metadata (Repository)⤷
RSD (Package) BW: Data Basis InfoObjects and Core Services
Basic Data
| Data Element | RSCHACONST60 |
| Short Description | Character. Constant (Max. Length) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSCHAVL60 | |
| Data Type | CHAR | Character String |
| Length | 60 | |
| Decimal Places | 0 | |
| Output Length | 60 | |
| 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 | Constant |
| Medium | 15 | Constant |
| Long | 20 | Character. Constant |
| Heading | 18 | Constant |
Documentation
Definition
By assigning a constant, a fixed value is assigned to a characteristic. The characteristic therefore exists on the database (for validations for example), but is no longer relevant for reporting (no aggregation or drilldown possible for this characteristic).
The internal value of the characteristic should be entered. Thi s can be found in input help.
Assigning a constant is mainly of use when working with compound characteristics.
Example: The Storage Location characteristic is compounded with the Plant characteristic. If just one plant is always used in the application, a constant can be assigned to this plant. Validation against the storage location master table should then be performed using this value for the plant. In the report however, only the storage location is offered as a characteristic.
Exception: If constant SPACE (type CHAR) or 00..0 (type NUMC) is to be assigned to the characteristic, a # (hash) must be entered at the start.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 740 |
