In
my other post, I introduced different flavors
of an aDSO objects. In this post, I want to go deeper with one of them –
cube-like aDSO object.
Aim
of the cube-like aDSO object is to replicate behavior of infocube object that
we know from classic (NetWeaver based) releases of SAP BW. It is used to model data
warehouse layer – data mart according LSA++
architecture. The object does not have change log (CL) table. There are
only two tables underneath:
1 Inbound data
(AQ or AX for a cold storage) - stores newly loaded data identified by data
load requests, similar to F-table in classic cube.
2 Active data
(AT) – stores compressed data by activation requests, similar to E-table in
classic cube.
Data
is moved from inbound table to active one upon its activation (also known as aggregation).
Once all data is activated, there is no data in the inbound table.
The
cube-like aDSO object setup is following. "Active data" and "All
Characteristics are Key" check boxes are checked.
BW4/HANA
BW75
Reporting on the cube-like ADSOs is performed as a union of inbound and active tables. This behavior is referred as stable navigation. There is no need to activate the data as both tables are used for the querying the data.
There
are few remarks with regard to a deletion of the cube-like aDSO object. Request
based deletion works if the data is only available in the inbound/new (AQ, e.g.
/BIC/A*1 Inbound Table) table. Once the data is
activated it is not possible to delete the request in the aDSO. There is only
possibility to complete content deletion or a selective deletion. If a
possibility to delete the requests is needed the data must not be activated.
More
information:
Onlinedocu
– datawarehouse layer – delta calculation
3102582 - Request
Based Deletion does not work as expected
3116509 - Deletion
of overlapping request for ADSO is not working in case if the request is activated
in target of ADSO type cube
No comments:
Post a Comment