ADSO compression vs reporting capabilities
As we have started to engulf into the world of SAP BW 7.5 and starting to use the new Data targets , mostly Advance Data Store Objects (ADSOs) that has now replaced the Classic datatargets like DSOs, cubes; it is really important to understand the different templates that is provided.
Below are the different ADSOs that you can create.
Data acquisition layer (including corporate memory)
Corporate memory – compression capabilities
Corporate memory – reporting capabilities
Data warehouse layer – delta calculation
Data warehouse layer – data mart
SAP has come up with 2 additional corporate memory ADSOs as below in addition to a ADSO similar to write optimized DSO (Data acquisition layer (including corporate memory)), a Standard DSO (Data warehouse layer – delta calculation) and an Infocube (Data warehouse layer – data mart).
Corporate memory – compression capabilities : not similar to any classic object
Corporate memory – reporting capabilities : not similar to any classic object
Before using these Corporate moemory DSOs, it will be helpful to understand the differences between them in a nutshell
|Compression capabilities||Reporting capabilities|
|Corporate memory||Corporate memory|
|Cannot be used in CPRO||Can be used in CPRO|
|Inbound table empty after activation||Inbound available after activation|
|“Selective deletion” removes data from the Active table. It cannot be done on Inbound table||“Selective deletion” removes data from both the tables – Inbound and active|
|Remove Inbound Table (1) and Delete active data (2) options not available||Remove Inbound Table and Delete active data options available|
|Activated requests cannot be deleted||Activated requests cannot be deleted. But “Delete active data” option can be used and then request can be deleted|
|Space conscious (3)||No Space constraint|
|Cannot track back loaded requests||Possible to track back|
|Precautions needed for propagation as extraction view is union of inbound and active||Good for propagation because extraction is always from Inbound table|
1. Remove Inbound Table: Deletes the Inbound table data upto the selected request, but the request stays in the Monitor with the “Status removed”
2. Delete Active Data: This option gives a chance to delete activated requests. When you use this option, all activated requests in the ADSO gets deactivated and still available in Manage screen. You can then delete the deactivated requests that are not needed anymore, and then you activate other requests again
3. Space conscious: I mean this when it comes to disk space. Compression capability ADSO at any time has only data in one table, i.e. Inbound table (before activation) OR active table (after activation). But the reporting capabilities ADSO has data in both, i.e. Inbound table (before and after activation) AND active table (after activation). So more space is needed when same data is in both tables
When you want to convert the classic datatargets (DSOs and Infocubes) to Advanced DSOs, you can straightway use
- “ADSO – Data acquisition layer (including corporate memory)’ for replacing an existing write optimized DSO,
- “ADSO – Data warehouse layer – delta calculation ” for replacing a Standard DSO
- “ADSO – Data warehouse layer – data mart” for replacing an Infocube
But for Corporate memory, if you decide to use te other 2 new templates provided, then you can check these differences, understand which one will suit your business requirement and then choose the right template.
Please share your ideas based on your expereince as well.