Extending the Reach of LSA++ Using New SAP BW 7.40 Artifacts Pravin Gupta, TekLink International Inc. Bhanu Gupta, Molex SESSION CODE: BI2241 Agenda  What is Enterprise Data Warehousing (EDW)?  Introduction to Layered Scalable Architecture (LSA)  Migration from LSA to LSA++  New SAP BW 7.40 Modeling and Provisioning Artifacts  Operational Data Provisioning (ODP) and Operational Data Queue (ODQ)  Open ODS View  Advance DSO  Composite Provider  Automatic HANA View Generation  Conclusion Why Enterprise Data Warehousing (EDW)  Consolidate the data across the enterprise to get a consistent and agreed view on your data  "Having data is a waste of time when you can't agree on an interpretation.“  EDW requires a database + “X”  SAP BW (BW) is the “X” as EDW with BW provides a flexible and scalable EDW solution  Highly integrated tools for modeling, monitoring and managing the EDW  Open for SAP and non-SAP systems EDW vs. Datamarts Layered Scalable Architecture LSA is the accepted approach for building EDW guaranteeing a consistent, highly available and maintainable data foundation for an agreed interpretation of BI & Reporting.  Transparency  Flexibility  Scalability  Robustness Source: SAP In-Memory Evolution Data Data BW 7.0 BW 7.3 BW 7.4 from Modeling Persistency at DB + BWA 7.0 DB + BWA 7.2 SP5 on HANA DB Runtime tr Planning Engine In Memory aM planning engine aW taD dnarevaeB Analytic Engine sFciernsta rciaolsc uinla BtiWonA Additi oinn-aml ceamlcourlya tions eW Multi provider Consumption of suoh PteN Data Manager Filter + aggregation hflaenxdiblilne gj oainnds HANA model in BW eraW aAS htiw InfoCubes BWagAg irnesgteaateds of IBnWfoA C-uobnelys optimSizAePd HInAfNoA C ubes taD es gnile DataStore Objects BWfAor r eDpSoOrsti ng optimSiAzePd H DAaNtaAS tore irpdo Object rM e tnE EDW Processes HANA data for BW staging Source: SAP Journey From LSA to LSA++  Migrate to Hana- Optimized objects  Streamline EDW Core  Enhance Virtualization Layer  Introduce additional layers  Open Operational Data Store  Agile Data Mart Layer  Resulting LSA++ LSA vs. LSA++  LSA  No reporting on Propagator.  Result of transformations stored in additional persistent Layer, known as Architected Data Mart.  Virtualization Layer only on top of Architected Data Mart and only UNION (Multiproviders).  LSA++  Reporting on Propagator is allowed.  Consequently, necessary transformation are moved from the Business Transformation Layer into Query Design and are thus executed upon query execution.  Virtualization layer on top of both Architected Data Marts and Propagator and using UNION (Multiproviders) and JOIN (Composite Provider). LSA++ Holistic Framework BI Streamlined: On EDW, Operational BI, Agile BI, Virtualization Source: SAP