BW on SAP HANA

BW Performance

These figures were reported by customers, which already have BW on HANA operating in their IT landscape.

1. Red Bull
Red Bull started to run its SAP NetWeaver 7.3. Business Warehouse on HANA in 2011.

The migration.
Non-disruptive fast migration.
Project completed in less than 2 weeks.
Database size before migration: 1.5 TB; reduced by 80% after migration.
The result:
Boost in load performance.
Simplified architecture: InfoCubes no longer required as an aggregation layer
Data can be read directly out of the DataStore Object (DSO).
Replication of data to InfoCubes and Business Warehouse Accelerator (BWA) Indexes no longer necessary.

2. Utilities industry representative
This utilities customer also upgraded to and operated its SAP Netweaver 7.3. BW on the latest HANA database release.

Data Load Performance
For DSO activation of 5.2 million records, performance improved by factor 32x. Before: 21 hours 40 minutes - After: 40 minutes.
Data load into write-optimized DSO write optimized and InfoCube Upload with 50K invoice header + 350K items. Load acceleration by factor 2.7x. Before: 1hour 30 minutes -  After: 30 minutes.
 Query Performance
Query with aggregated result set: Performance dramatically improved by factor 471x for queries on aggregated data. Before: 471 seconds - After: 1 second.
Performance acceleration by factor 5x on granular data sets. Before: 308 seconds - After: 64 seconds.
Massive Data Volume Reduction
From xRDBMS space of 4.3 TB reduced to 0.73 TB RAM on HANA
Average compression factor (column tables) 5.8x

3. Automotive industry representative:
This automotive customer upgraded and migrated their data on BW 7.3 on HANA.

Data Load Performance:
InfoCube loading speeds up about 1.39x.
DSO activation accelerated 4.15x
Query Performance
Compared to BW on a traditional relational Database Management System (DBMS)
BW queries were 8.5x faster
BO WebI execution, 11.6x faster
Response times with 40 millions data records in HANA-optimized InfoCube: 45 seconds; 26 times faster compared to the legacy DBMS.


Hope many of the BW clients will be soon Powered by HANA. Will enjoy the supersonic speed :)

Comments

Anonymous said…
Thanks for sharing this Information. Got to learn new things from your Blog on SAP HR.
SAP HR

September 14, 2016 at 9:49 PM
deeksha said…
very very amazing explaintion....many things gather about yourself...yes realy i enjoy it
Base SAS Training in Chennai
July 31, 2017 at 2:13 AM
Anonymous said…
Thanks for sharing this Information. Got to learn new things from your Blog on SAP HANA

http://thecreatingexperts.com/category/sap-hana-training-in-chennai/

contact 8122241286
August 2, 2017 at 4:43 AM
Post a Comment

Popular posts from this blog

One stage stop to know all about BW Extractors-Part1

Image
Types of Extractors:               Application specific BW content extractors: Lo Extraction: Logistics refers to the process of getting a product or service to its desired location upon request which involves transportation, purchasing, warehousing etc. Main areas in logistics are: Sales and Distribution (SD) : application 11, 13, 08 (in LBWE T-code) Materials Management (MM) : application 03, 02 Logistics Execution (LE) : application 12 Quality Management : application 05 Plant Maintenance (PM) : application 04, 17 Customer Service (CS) : application 18 Project System (PS) : application 20 SAP Retail : application 40,43,44,45 How the data extraction happens? Extraction can be done using either Full update/delta update. Full load: Incase of logistic application, Full/Initiali
Read more

Generic Extraction via Function Module

How does the extraction API work in case you are extracting data using a self defined function module with generic delta? Sometimes, if your application or requirement makes it necessary, you have to create your own function module to extract the data from whatever sap system to bw. Therefore you normally make a copy of the standard fm 'RSAX_BIW_GET_DATA_SIMPLE'. To make this new function work for you, you have to realize the following. 1) The FM gets called by the extraction API for at least 2 times. First time is for initialization and from the 2nd time on it is for data extraction. 2) Right after the last data package (somehow you need to make sure that it is the last one) you have to raise the exception no_more_data. Example with lots of comments FUNCTION RSAX_BIW_GET_DATA_SIMPLE. *"-------------------------------------------------------------------------- *"*"Local interface: *" IMPORTING *" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUN
Read more

COPA Extraction Step By Step in SAP BW

Image
COPA Extraction Step by Step: SAP R/3 or SAP ECC: 1. SAP R/3 or ECC goto T.Code KEB0 , In Function: Select Create  Control Parameters: Provide a New CO-PA DataSource Name:1_CO_PA%CL%ERK 2. Select your O perating C oncern, e.g.,IDES. 3. Select radio button Costing-based or Account-based as OC . 4.Select field names for partitioning.e.g. BUKRS (Company Code), Check 5.Click on Info Catalog (F7) 6. Select the Characteristics & Value fields & Keyfigures 7. Select the Package/Development Class for Workbench request 8. Edit your DataSource to select/Hide fields, Save. Datasource created successfully. 9. Extractor Checker or RSA3, extraction. SAP BW:   1. Replicate DataSource 2. Assign InfoSource 3. Transfer all the datasource elements to an InfoSource 4. Activate InfoSource 5. Create a InfoCube (Copy Str from InfoSource) 6. Create Dimension & Define and Assign it. 7. Check & Activate. 8. Create Transformation (Insert or Modify KF
Read more