Use
The standard
DataStore object is filled with data during the extraction and loading process
in the BI system.
Structure
A standard
DataStore object is represented on the database by three transparent
tables:
Activation
queue: Used to save DataStore
object data records that need to be updated, but that have not yet been
activated. After activation, this data is deleted if all requests in the
activation queue have been activated.
Active
data: A table containing the
active data (A table).
Change
log: Contains the change
history for the delta update from the DataStore object into other data
targets, such as DataStore objects or InfoCubes.
The tables of
active data are built according to the DataStore object definition. This means
that key fields and data fields are specified when the DataStore object is
defined.
The activation queue and the change log are almost identical in
structure: the activation queue has an SID as its key, the package ID and the
record number; the change log has the request ID as its key, the package ID,
and the record number.
This graphic shows
how the various tables of the DataStore object work together during the data
load.
Data can be loaded
from several source systems at the same time because a queuing mechanism
enables a parallel INSERT. The key allows records to be labeled consistently
in the activation queue.
The data arrives in
the change log from the activation queue and is written to the table for
active data upon activation. During activation, the requests are sorted
according to their logical keys. This ensures that the data is updated to the
table of active data in the correct request sequence.
DataStore Data and External Applications
The BAPI,
BAPI_ODSO_READ_DATA_UC, for reading data, enables you to make DataStore data
available to external systems.
In the
previous release, BAPI BAPI_ODSO_READ_DATA was used for this. This BAPI is now obsolete.
No comments:
Post a Comment