Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSDA (Package) BW Data Archiving and Near-line Storage. Core Functions
Basic Data
| Data Element | RSDA_RB_DATA_TIM_WITH_CREL_KEY |
| Short Description | Time Characteristic with Time-Correlated Key Characteristic |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RS_BOOL | |
| 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 | Time-Corr. |
| Medium | 20 | Time-Corr. Key Char. |
| Long | 40 | Time Char. with Time-Corr. Key Char. |
| Heading | 55 | Time Characteristic with Time-Correlated Key Char. |
Documentation
Definition
The selected time characteristic is not part of the key, but it can be linked with a time-correlated characteristic of the key.
Use
The time characteristic is used to create time slices. The time-correlated characteristic of the key is used to partition the archive.
Dependencies
This selection is only useful if the relationship between the time characteristic and the key characteristic is mostly a monotonously increasing relationship.
Example
A sequential document number in the key can be linked, for example, with a posting date in the data part in order to represent time slices on the posting date at document number intervals. An upper limit for the posting date is represented on the upper limit for the document number by determining the minimum document number whose corresponding posting date is larger than the upper limit for the posting date from the current dataset. All the data records whose document numbers are smaller than the minimum thus computed are archived and protected against overwriting. This ensures that all the data records selected in this way fulfill the time slice condition for the posting date. The reverse, however, is not normally true. There are data records that satisfy the time slice condition for the posting date, but that are not (yet) archived.
Disjunct document number areas for archiving are formed by 'subtracting' all the archived or defined document number areas from the document number areas described above.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
