Definition
A DataStore object
serves as a storage location for consolidated and cleansed transaction data or
master data on a document (atomic) level.
This data can be
evaluated using a BEx query.
A DataStore object
contains key fields (such as document number, document item) and data fields
that, in addition to key figures, can also contain character fields (such as
order status, customer). The data from a DataStore object can be updated with
a delta update into InfoCubes (standard) and/or other DataStore objects or
master data tables (attributes or texts) in the same system or across
different systems.
Unlike
multidimensional data storage using InfoCubes, the data in DataStore objects
is stored in transparent, flat database tables. The system does not create
fact tables or dimension tables.
Use
Overview of
DataStore Object Types
|
Type
|
Structure
|
Data
Supply
|
SID
Generation
|
Details
|
Example
|
|
Standard DataStore
Object
|
Consists of three
tables: activation queue, table of active data, change log
|
From data transfer
process
|
Yes
|
||
|
Write-Optimized
DataStore Objects
|
Consists of the
table of active data only
|
From data transfer
process
|
No
|
||
|
DataStore Objects
for Direct Update
|
Consists of the
table of active data only
|
From
APIs
|
No
|
|
Management of DataStore Objects
Features
The DataStore
object is displayed in the top table. You only have to select a DataStore
object from the DataStore objects available if you called DataStore object
administration from the monitor.
In the top toolbar,
choose Contents to display the contents of the table of active data
for the DataStore object you have selected. With Delete Contents, you
can delete the contents of the DataStore object. You can also display an
application log and a process overview.
Tab Page: Contents
You can display the
content of the change log table, the newly loaded data table (activation
queue), or the active data (A table). You can also selectively delete requests
from the DataStore object.
Tab Page: Requests
This tab page
provides information about all requests that have run in the DataStore object.
You can also delete requests here or schedule an update.
Tab Page: Reconstruction
You use this
function to fill a DataStore object with requests that have already been
loaded into the BI system or into another DataStore object. This function is
only necessary for DataStore objects that obtained their data from
InfoPackages.
Tab Page: Archiving
If you have created
a data archiving process, you see this additional tab page.
Automatic Further Processing
If you still use a
3.x InfoPackage to load data, you can activate several automatisms to further
process the data in the DataStore object. If you use the data transfer process
and process chains that SAP recommends you use, you cannot however use these
automatisms.
We recommend that
you always use process chains.
If you choose the
main menu path Environment → Automatic Request Processing, you can
specify that the system automatically sets the quality status of the
data to OK after the data has been loaded into the DataStore
object. You can also activate and update DataStore data automatically. Data
that has the quality status OK is transferred from the activation queue into the
table of active data, and the change log is updated. The data is then updated
to other InfoProviders.
You can also make
these settings when you create DataStore objects.
*****************************************************************************
Only switch on
automatic activation and automatic update if you are sure that these processes
do not overlap.
****************************************************************************
Delete Change Log Data
You can delete data
from the change log. To do this, choose Environment → Delete Change Log Data in the main menu.
No comments:
Post a Comment