Getting Started Community WIKI Spaces SAP Community Welcome, Guest Login Register Store Search the Community Browse SAP NetWeaver Business Warehouse / … / DataStore Object (advanced) in BW Modeling Tools ADSO Scenario Description Created by Attila Giesz, last modified by Janette Koppensteiner on May 30, 2018 Acquisition Layer Data Acquisition Layer (including corporate memory) Corporate memory with compression feature Corporate memory with reporting option Propagation Layer Reporting Layer Planning (BW 7.50 only) Acquisition Layer With the DataStore object (advanced) (also known as ADSO), you can create objects that cover the "write­optimized" use cases for classic DataStore objects (ODSOs). Data Acquisition Layer (including corporate memory) The first figure shows a typical corporate memory. Requests will be loaded into and extracted from the inbound table. The data doesn't get aggregated, neither by the transformation nor by the ADSO. Test Example Corporate memory with compression feature The second figure shows a corporate memory with compression feature. Requests will still be loaded into the inbound table. Old requests that are no longer needed on detailed level can be compressed (aggregated according to the semantical key) into the active data table. Test Example Corporate memory with reporting option The third picture shows an corporate memory with reporting option. The loaded requests can be activated but will remain in the inbound table on detailed level. Extraction will be done from the inbound table (detailed information). Reporting on the active table. Test Example Propagation Layer The following figure shows an ADSO covering the "Standard" use­case of ODSOs. Requests will be loaded into the inbound table. To report on the data, the user has to activate the loaded requests. The data is then transferred into the active data table and the history (delta) is stored in the change log. The change log is also used to rollback already activated request (recovery of the active data table). Test Example Reporting Layer The next figure shows an ADSO covering use­cases where InfoCubes were used before. The inbound table acts as "F"­table and the active data table as "E"­table. Before compressing the request it is necessary to upload all new deltas to further targets. The user reports on a union of (a part of) the inbound table and the active data table. Test Example Planning (BW 7.50 only) The next figure shows an aDSO for direct update. This is the only aDSO representation which can be used to load into the active data table via DTP or API. In contrast to the DSO, all consistency checks like SID handling or time consistency check will be applied. No labels 6 Child Pages ADSO InfoCube aDSO with Changelog Corporate memory with compression feature Corporate memory with reporting option Direct Update DSO Typical corporate memory Contact Us Privacy SAP Help Portal Terms of Use Legal Disclosure Copyright Cookie Preferences Follow SCN
