Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
BC-BW (Application Component) BW Service API⤷
RSUM (Package) BW Service API: Metadata
Basic Data
| Data Element | RSDLTASAF1 |
| Short Description | Safety Interval Lower Limit |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSLOW | |
| Data Type | CHAR | Character String |
| Length | 45 | |
| Decimal Places | 0 | |
| Output Length | 45 | |
| 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 | Interval |
| Medium | 20 | Safety Interval |
| Long | 39 | Safety Interval Lower Limit |
| Heading | 55 | Safety Intervall for Delta Selection Lower Limit |
Documentation
Definition
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
