“Bypass Solution” – Road map to transition (power of HANA based future ERP systems)
Smooth Transition to Leverage the power of HANA without affecting existing infrastructure
This is just an extract from great lecture series (Chapter 05 – Foundation for New Enterprise Application Development Era) by Dr.-Ing. Jürgen Müller,
Chapter 5 is great initiative for HANA developers to quickly how HAN eliminates most of the tedious and time consuming processes we have been using.
This give great overview and explanation on how easy is to adapt power of HANA using
Different (before using HANA -In_Memory Database and After using HANA in-memory database)
Above illustration shows the conventional implementation of ERP systems which relies on 3rd party database systems. Key drawback of such architecture is being the presence of ETL and separation of OLAP engine , which handicaps the organizations real time reporting capability.
You could notice that HANA already helped to remove “Transformation” process of ETL activity by eliminating need for traditional info cubes. Bypass solution doesn’t interrupt the usual operation of ERP system. new HANA -database will be updated using triggers programmed on traditional database to enable updated state of data.
Above picture shows the final state after complete transition, you could notice that OLTP & OLAP process takes place simultaneously.It is clear that future ERP systems will be on top of HANA architecture to leverage the power of in-memory database technology
We could foresee promising future and demand for HANA Developers and they will be the game changers of Enterprise application era.
So Learn and develop our little girl HANA to reach her full potential
Warm-Up: In-Memory Data Management – Dr.-Ing. Jürgen Müller, OpenSAP.com (visit this for quick overview of HANA IMDB)
visit https://openhpi.de/ for complete lecture series on – SAP HANA – IMDB
sorry but don't confuse OLAP with DW. OLAP can serve both, operational reporting on OLTP data and analytics on multi-system harmonized, consolidated data in a DW. Performance is one of many problems to solve. Consistency is a major one which does not exist when reporting from one source where consistency is managed by the single app (e.g. ERP). Even in SAP's Bus Suite there is no harmonised notion of a customer (FIN), business partner (CRM) etc. Even inside that Bus Suite the above does not work. So it's nice ivory tower theory by some sciencists far away from reality. They'd need to do a real project first. Sorry to point that out that harshly.
I agree with Tim. It is quite possible to build HANA models to support certain use cases. However, it is a different ball game when you try to replace a data warehouse merely with HANA models.
To be fair, even I thought that HANA has some magic engine that could eliminate the transformation part of ETL. Just like you, I had proposed to replace traditional DW with HANA database models. Of course, reality brought me down to earth. As mentioned by Tim, harmonization will be a problem. Also, you cannot easily and efficiently perform data cleaning with calculated or restricted attributes. Furthermore, when you try to replicate the logic of a complex ABAP function to get data like variant configuration details of a sales order item, the analytic view or calculation view on HANA will appear like a weed. Finally, even when you stubbornly do all this to create a complex view, the query performance in HANA will be similar to or worse than any data warehouse as HANA has to do lot of work at runtime. I can continue to list host of other things that will force you to build a traditional data warehouse on HANA. Lastly, even when you are using BW on HANA as a data warehouse, you will notice that you still have to model. Replacing a cube with ODS will save space and time to load cubes. However, it cannot eliminate the need for modelling ( things like harmonization).
Unless some magic happens in future, your final state will contain OLTP, OLAP and a data warehouse built on single instance of HANA.