Skip to Content

SAP HANA Advantages of In-Memory Computing with RDS: ASUG Webcast

Miklos Szorenyi, SAP, Solution Assembly & Packaging team, provided this webcast to ASUG last week.  He is on the team responsible for rollout of HANA related solutions.

How can you get started?  How can you get started on HANA solutions?  Miklos said SAP is developing solutions and packages, and available packages so you can real quickly get started with HANA; speed up processing power with HANA.



  • SAP HANA™ Overview
  • Solution portfolio currently available:
  1. SAP ERP rapid-deployment solution for operational reporting with SAP HANA
  2. SAP ERP rapid-deployment solution for profitability analysis with SAP HANA
  3. SAP CRM rapid-deployment solution for customer segmentation with SAP HANA
  • Customer Testimonials and Outlook


Figure 1: Source: SAP

Figure 1 shows information explosion of data volume; business needs, why making life easier.


Figure 2: Source: SAP


Today, in our private lives we run searches on Google we get results in seconds.  “Make decisions at the moment of risk” – stock markets, inventory issues, we want to see that in our ERP system. 


Three bottlenecks:

1)      Hard disk storage – we need to replicate the data.  For example, SAP ERP we need to have a business warehouse where we duplicate our data

2)      Want immediate answers to questions – operational and business decisions taken immediately

3)      We want current and complete information.  We do not want a lag or replication issue


In response to this, the speaker said in-memory computing is the answer.  It changes the speed and capacity of data.  Data is compressed.  The applications are about 100X faster.  Real time access.


Critical industries can benefit from SAP HANA.  One example is a chemical customer with 8TB ERP CO-PA data; through HANA access data faster.

Another is a large Pharma customer with 600 GB ERP + 3.5 TB BW data.  Next year this customer will be able to take advantage using HANA as a database to BW.


Figure 3, Source: SAP


Figure 3 shows real-life customer data and analytical results.  Running reports took 77 minutes before HANA and then 13 seconds. 

A customer with 70 retail stores, multiple sources of data, 50TB of data; the analysis response time was reduced to .04 seconds.


Figure 4, Source: SAP


SAP HANA is an appliance and comes bundled with software and hardware.  SAP ensures through certification of the vendors that it runs as designed.  HANA appliance consists of SAP HANA database which is running in memory.  The SAP HANA studio is used to create models and therefore only replicate data you want analyzed.   

One of the Rapid Deployment Solutions has predefined models. Calculation and planning engine is part of the architecture.  The real-time replication can be Sybase Replication Server or System Landscape tool (SLT).

The backend can be SAP Business Suite or BW.


Figure 5, Source: SAP

**Correction – see comments below by Marc Bernard, SAP

“Just one correction to figure 5: There is no ramp-up for HANA 1.0 SPS 3. It is available to all HANA customers already.

On the other hand there is a ramp-up for SAP NetWeaver BW 7.3 powered by SAP HANA (see

**End of Correction

Figure 5 shows where SAP stands today.  Today is the renovation phase.   We have “in-memory” analytics using SAP HANA studio we create models where we replicate ERP data.  The complete BI suite runs on HANA. 

The next phase of strategy, labeled as “innovation”, SPS3, will have BW running on HANA.  SAP  will have industry and line of business solutions on HANA. 

Long-term, beyond 2012, “transformation”, where SAP the Business Suite will have one persistent layer – no more replication.


Figure 6, Source: SAP


Figure 6 shows the many aspects of HANA – database, appliance, replication server

HANA has 5 major types of the application which can be run completely in HANA

HANA is a technology platform for customer-specific development. 

HANA is content, using ERP backend, replicating data in HANA and using BI/BusinessObjects front ends to run reports.  RDS solution for ERP operational reporting is an example.

For use as an Accelerator – side by side with a traditional database and replicate the database.  RDS for CO-PA is an example. 

The two right-side blocks are the future- products in memory.  Applications completely running on HANA. 

Future vision is to move complete ERP suite into HANA, requiring development of new applications.


Solution Portfolio

Solution portfolio means create content. Three are released already.


Figure 7: Source: SAP – What is RDS?


RDS includes software, such has HANA.  Content includes back-end content, templates.   Services include consulting services at a fixed price, different per RDS solution.


Figure 8: Source: SAP


Figure 8 shows the services with RDS.

Phase 1 includes project management, system landscape check – if software installation was done properly.

Phase 2 is deploy, activating the solution, deploying the content

Post go live includes support (phase 3)

Depending on the package, the project lasts 3-6 weeks.


Figure 9, Source: SAP

Figure 9 shows the available HANA RDS solutions.

CRM segmentation supports targeted marketing.


Figure 10: Source: SAP


Figure 10 shows planned solutions – some very soon, including CRM pipeline solution in early 2012.


Figure 11: Source: SAP

Reports are really models and they are imported into SAP HANA studio.

22 reports are across the 5 areas listed in Figure 11.


Figure 12: Source: SAP


Figure 12 shows how this works and how the content is deployed

The reports are developed in HANA landscape, exported into XML files, the models are available for download, and then imported into Customer’s HANA studio

Some prerequisites:  Customers on ECC 6.0, documentation is in English, for all industries.


Figure 13, Source: SAP


The SAP speaker felt the CO-PA RDS was the most significant breakthrough.   The response time of the queries and speeding up the month-end close processes is a benefit.


Figure 14, Source: SAP


HANA with CO-PA versus HANA with operational reporting difference – in CO-PA replicating the CO-PA database from ERP into HANA – the application is still running in ERP.  The CO-PA reports are running against HANA and you can use BI 4.

Some prerequisites:  running cost-based CO-PA, ECC 6.0, and HANA.  It is a global cross-industry solution.


Figure 15, Source: SAP


The demo  shows transaction KE30, 5 year comparison using HANA and using the traditional ERP

HANA brought back result in 3 seconds versus SAP ERP report came back in 10 minutes


Figure 16 – CO-PA on BusinessObjects Explorer with HANA


Figure 16 shows a CO-PA report using BusinessObjects Explorer on HANA; you can slice, drilldown against 26 million records, drilling all the way down to the document number.


Figure 17: Source: SAP


Figure 17 shows CRM target marketing HANA solution, against millions of records, target groups based on customer segments.  It uses the delta replication within HANA.


  • SAP      CRM 7.01 EHP1 SP6 or higher
  •  SAP Target Marketing
  •  SAP HANA 1.0 SP2 or higher


Figure 18: Source: SAP

Figure 18 shows customer testimonials.  Colgate reduced process times from 77 minutes to 13 seconds with CO-PA.


The speaker provided these links:

Service Marketplace on the available RDS

Service Marketplace overview on available RDS solutions

General information on In-Memory


Question & Answer:

Q: How is CO-PA data replicated?

A: It is 1 to 1 everything it is replicated; only limitation is HANA is using costing-based CO-PA

Q: Is HANA database based on Oracle?

A: No; it is in-memory.  HANA is a database by itself.

Q: Can HANA help with posting the sales orders, transactions?

A: At the moment not running transactions in HANA


I always learn something new at every SAP HANA webcast and this one was no exception.  I hope we hear more at ASUG Annual Conference 2012.

You must be Logged on to comment or reply to a post.
  • Hi Tammy – great content – thanks for sharing.

    Whilst at SapphireNow in Madrid I was speaking with some of the HANA guys and talking about the different versions and upgrade paths.

    The RDS version of HANA as far I as got it was slightly different to the core HANA solution.

    If the core HANA solution was upgraded or a new version released, the RDS version would need to be re-implemented to make use of the new functionality.

    The RDS solution as far as I can see could solve a current problem with reporting – but it wont have all the bells and whistles the core product will have.

    Does this sound true to you – happy to be corrected.

    • Hi Mark,
      Thank you for taking the time to read and comment.

      I didn’t see enough during this webcast to make that determination – that would’ve been a great question to ask during the webcast.


  • Hello Tammy,

    just one correction to figure 5: There is no ramp-up for HANA 1.0 SPS 3. It is available to all HANA customers already.

    On the other hand there is a ramp-up for SAP NetWeaver BW 7.3 powered by SAP HANA (see

    SAP Customer Solution Adoption (CSA)