Hierarchy
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSSM (Package) BW: General monitoring and scheduling
Basic Data
Data Element | RSBOOK66 |
Short Description | Checking period in request being checked in data target |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TZNTSTMPS | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 15 | |
Decimal Places | 0 | |
Output Length | 19 | |
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 | Check.perd |
Medium | 15 | Checking period |
Long | 20 | Checking period |
Heading | 20 | Checking period |
Documentation
Definition
Before data is loaded into an ODS object, the system checks whether or not this data is allowed to be loaded into this particular ODS object.
With delta-data, the system checks whether or not all of the deltas/repeats that have been loaded successfully from this source system to this DataSource have been updated in this ODS object, and whether the relevant inits are available in the ODS object.
If this test terminates, the new delta-data cannot be updated in the ODS object.
Since delta calculations are made in the ODS object, the sequence in which data in the DataSource is updated is often relevant for many DataSources, and this is the main purpose of this procedure.
In certain cases, it is necessary to reinitialize the delta extractor in the OLTP, or to construct an ODS object containing only those requests that are important to your business, but do not correspond to the test described above.
With this purpose in mind, you are able to determine for each ODS object a starting point from which the system starts to check the completeness and sequence of the requests that are available in the ODS object. The system also checks whether or not the relevant initialization requests have also been updated in the ODS object.
These checks are not applied to those requests from the source system for this DataSource that are older than this starting point (meaning that the request date is earlier than the starting point).
Caution:
Use this function ONLY if you are absolutely certain that the data is correct at this particular point in time, and does not need to be tested further.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 30A |