Corporate scale SAP Business Warehouse powered by SAP HANA
That’s the mission: We run a transformational program intending to provide a single source of truth Business Intelligence environment and self-service capabilities in an integrated platform based on proliferation of Business Objects tools for SAP; all built on the latest architectural set-up with an early adoption of HANA In-Memory database and consistent data governance in conjunction with an enterprise-wide data layer (EDL).
Only one of the very exciting pieces for the infrastructure work stream within this program are the ‘latest architectural set-up’ and ‘early adoption of HANA’. Two of our deliverables are the latest SAP Business Objects 4.x platform fully integrated with an SAP Netweaver BW 7.3 powered by SAP HANA – including all operational concepts to run all kind of business-critical reporting and planning on this BI platform.
Our HANA infrastructure setup as of today:
- 1 TB Main Memory
- SSD 4x 320 GB for log files
- 6.5 TB direct attached storage
- 300 GB internal storage for OS
0.1. SAP Business Objects 4.0 SP2.3
0.2. SAP Netweaver BW 7.30 SP5
0.3. SAP HANA SP3
As first system in our 3-tier (Dev, Test, Prod) BW environment we migrated the test system BWV and it is up and running since three weeks now. The migration for the production system is in process and we will have the entire system landscape ready before November.
<picture: DB02 screenshot shows SAP HANA database>
This BW landscape is a new environment, which will be filled with business content in the next months. As of today we have a handpicked number of data loads and business scenarios on the system.
Some more hard facts:
- The DB import on HANA was completed in 3.5 hours
Our HANA environment does not only act as database for BW, but powers also ECC and CRM as by-side solution. In this architecture the BW can read per second connection data from the by-side area (e.g. sales pipeline) and other data per classic extraction (e.g. currency conversion data) to join this in a Transient InfoProvider. (Comment: This needs SLES 11 on the application sever).