...
- Compared to classic DSO, the ADSO provides faster activation and load times.
- It can be deployed in various layers of the LSA++ architecture.
2. Composite Provider: Since the release of SP8 and BW 7.5 SP1, it has re-evolve completely to support the new modeling options. Composite Provider is an InfoProvider that combines data from both worlds (BW native models and HANA based views).
- Combine data from other HANA based applications on the same instance of HANA with data from BW
- Supports Unions and Joins
- Central interface for BW Queries
- Faster and simpler data modeling - successor to MultiProvider and InfoSet
- Reduce database size: virtual modelling capabilities as opposed to data flows
- Supports usage of inventory key figures and planning scenarios
...
3. Open ODS Views: it enables one to define BW models for objects like database tables, database views, or BW DataSources (for direct access). It provides flexible integration without the need to create InfoObjects. The biggest benefit is its ability to consume external data sources into BW without the need for a separate BW persistence for the data.
- Virtualized access to various sources through SAP HANA Smart Data Access
- Flexible and easy integration of external data models
- Ability to switch from virtual to persistent mode.
LSA ++ Detailed Implementation for Solvay
Big Picture of LSA ++ implementation: A mix Modelling HANA Studio Approach is implemented.
Golden rules for modeling and data lineage are:
- Acquisition Layer = Propagation Layer with Data Storage using ADSO : ADSO Field Based; write optimized option + cold zone (not in memory in SSD only) + no infoobject = field only (for example keep field coming datasouce werks and not BW infoobject C_PLANT) + need to data cleaning (recurrent mode) + source system management
- Corporate Memory (used only if source system is archived and if there is a need of strong data recovery capabilities : Use of ADSO image of Acquisition Layer.In this Layer, ADSO must be identical to ADSO of Acquisition Layer in terms of Keys. => No need for Solvay (WBP or WPX system)
- Enterprise Data Warehouse = Business Layer : Business Rules are Applied Here for storage part. Consist of ADSO Object for which and external SAP HANA View might be generated
- → Propagation 1-1 from acqusition, key data + infoobject in the ADSO (for the reporting) + general rules example K4 fiscal period + conversion of date → wait to take decision (only fields of key and infoobjects)
→ Business layer : + layers of Business as today, dedicated by application. - last level could be only the current & last year + another ADSO with all years (but need to put a limit max 5-8 years)
- → Propagation 1-1 from acqusition, key data + infoobject in the ADSO (for the reporting) + general rules example K4 fiscal period + conversion of date → wait to take decision (only fields of key and infoobjects)
- Virtual Datamart Layer: This Layer consist of SAP HANA Artifacts, based on generated SAP HANA Views for ADSO. SAP HANA Artifacts are consumed in SAP BW using Composite providers for which each HANA Field is mapped with an InfoobjectInfoobject
- SAP BW Queries are created on SAP Composite Providers. In some cases, a generated SAP HANA View bases on Query can be provided with some restrictions documented
...
Level 1 : RAW Data acquisition = Propagation layer
DSO and nothing are done on the transformation between Datasource and this DSO (1 to 1 and no business transformation rules) because it could be the source for several project
...
Level 2 : Enterprise datawarehouse = Business Layer
DSO or several level of DSO if the transformation are complex and if data is to be historised
Level 3 : Virtual layer – application datamarts & application reporting
Hana views / Open ODS view
Composite providers (based on union of DSO or Hana views)
...