Hierarchy

⤷

⤷

Basic Data
Data Element | RSPLS_CR_DATETO |
Short Description | Characteristic Relationships: Validity Date |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATS | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | to |
Medium | 20 | Valid Until |
Long | 40 | Valid Until |
Heading | 10 | to |
Documentation
Definition
The default key date is a key date that is used in the entire planning model. You can specify a default key date for every real-time InfoCube.
Use
The following options are available for setting a key date:
- Unspecified (the system date is the default value, if all the relevant InfoCubes have the key date = unspecified)
- Fixed Date
- From Variable
All objects that depend on the key date - such as the filter, hierarchies used in the filter or hierarchies used in the 'from' and 'to' values of the copy/distribute functions - can be set to the default key date. When a planning function is executed, the system calculates the default key date as follows:
- If the aggregation level is created based directly on a real-time InfoCube, the default key date is the same key date that is set for the characteristic relationships of this InfoCube.
- If the aggregation level has been created on a MultiProvider, all the relevant real-time InfoCubes below the MultiProvider are checked. If all these InfoCubes have the setting 'unspecified', the default key date is the current system date. If one of the real-time enabled InfoCubes has a different setting for its key date, the first InfoCube that returns a specific value is the 'winner'. Variables are evaluated when they are returned.
You also have the option of using a different key date with every time-dependent object.
This can be useful in certain situations. For example: You want to use a specific hierarchy that is to be read with another key date than the master data attributes. Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 700 |