Client is multinational enterprise information technology company that provides products and services geared toward the data center such as servers, enterprise storage, networking, and enterprise software. Purpose of the project was to move existing Classical BW reports that shows near real time data to real time data reporting using SLT and BW4HANA inbuilt capabilities. This is one of the best approaches to use BW Query and composite provider (BW4HANA objects) as BW shell will add flexibility to do more things.
With Classical BW systems, Business needs to wait at least half a day for BW reports to get refreshed. However, SLT with BW4HANA system capabilities data get refreshed as soon as data enters Transactional systems and available for reporting. Thereby, supports your business users from Finance, Order Management and Delivery to make their tactical decisions on a day-by-day basis
For any SAP development, we follow a 3-tier architecture (presentation layer, application layer, and database layer), where complex formulas or logic are executed in the application layer rather than the database layer. BW developers didn’t have the option to run their report logics directly on the database and were reliant on BW modelling, where data needs to persist (physically store) at many layers before being exposed to BW queries. This caused a lot of performance issues and data redundancy in the past hence we need an alternate BW approach that not only help us reduce physical storage but also ensure better performance
Classical BW Architecture
Hybrid Modelling Architecture
Calculation Views and Composite provider helps us implement Mixed modelling in BW4HANA where a model from Native HANA (Calculation views) is exposed to BW object (Composite provider).
Calculation views aids in implementing logic directly on data base layer, thereby reducing execution time by eliminating the need to push the data to application layer. It helps calculate data on the fly to cut down unload and reload phases to zero when it comes to business-related changes in data staging or extension/reduction in a data model. Unlike Classical BW systems there is no need to clear delta queues whenever there is a change in logic which facilitates zero downtimes during go live.
Composite Provider helps us combines data from several analytic indexes (Calculation Views in our Scenario) or from other Info Providers (by Join or Union – Info objects in our Scenario) and makes this data available for reporting and analysis. UNION and JOIN operations are executed in HANA and not on application server. CP also help us implement complex logic such as Key and Text display for field, Attributes of Info object.
Comparison of Persistent objects in Classical BW vs Hybrid Modelling: We have compared the persistent objects below data based on 30 BW objects implemented so far.
Comparison of Data storage levels in Classical BW vs Hybrid Modelling: We have compared the layers difference below data based on 30 BW objects implemented so far.
Accomplishments and Lessons Learnt