6. 6
SAP in-memory innovations make
the “New Way” a reality
In-Memory
Row
+
Column
Database
Massively
Parallel
Processing
Calculation
Engine
Columnar storage increases the
amount of data that can be
stored in limited memory
(compared to disk)
Column databases enable
easier parallelization of
queries
Row database fast
transactional processing
In-memory processing
gives more time for
relatively slow updates
to column data
In-memory allows
sophisticated calculations
in real-time
MPP optimized software enables
linear performance scaling
making sophisticated calculations
like allocations possible
7. 8
Enabling IT Agility
How Fast Can IT React on Change? – Empower Business People
How can In-Memory help?
In-Database Analytics
No aggregates
No MOLAP cubes
External hierarchies
No re-alignment runs
Virtual structures only
Stable performance
traditional change management process
9. 10
In-Memory Analytics
SAP HANA real-time operational
analytics
Complete BI Suite with BI 4 runs
on SAP HANA
Begin delivery of Baseline
Reporting packages
One Store for Data and
Analytics
SAP HANA only persistence layer
for SAP Business Suite
SAP Business Suite optimized for in-
memory computing
Flexible real time analysis of
operations at non-aggregated
level
Real-Time operational planning
and simulation capabilities:
link to execution
Primary persistence and
optimized for SAP BW
Reduced landscape complexity
Value chain transformation
CapabilitiesBenefits
Next-gen Applications
SAP BW fully running on SAP HANA
SAP HANA platform for in-memory apps
■ Industry and LOB Analytic Apps
■ Other purpose built apps
Further optimization of BI 4 Suite for SAP
HANA
SAP Business Suite begins move to SAP
HANA
SAP HANA
1.0 sp3
Vision
Longer-Term
SAP HANA Development Roadmap
Product Strategy and Plan
SAP HANA 1.0
Dec 2010
SAP HANA
1.0 sp1, July 2011
sp2
General
Availability
RTC
(Ramp-up)
10. 11
Just Some of the New HANA-Enabled
Applications for 2011
SAP Cash and Liquidity Management: Allows companies to predict inbound and
outbound cash flows and risk management.
Sales and Operations Planning: This application will enable sales and marketing
departments to collaborate with operations and finance in order to evaluate the
impact of their strategies and make accurate predictions.
Intelligent Payment Broker: This application will calculate financing options on
open invoices and will help determine which discounting terms should be offered on
which invoices.
Smart Meter Analytics: The software for intelligent electricity meters: With this
application utility companies can analyze smart meter readings to forecast demand
and develop new products.
SAP Trade Promotion Management : Improves the planning process and helps
develop accurate strategies for particular customers.
11. 12
SAP
CRM Rapid
Deployment
Solution
SAP ERP rapid-deployment solution for operational
reporting with SAP HANA™ software
Business Models and Reports included:
Financial Reporting
Sales Reporting
Procurement Reporting
Shipping Reporting
Master Data Reporting
Solution to provide compelling SAP ERP operational analytics quickly and affordably
Description
An essential reporting software with fixed scope, predefined
services at a predictable price with the flexibility for future
extension. It provides a set of reports from the business area
of sales, financial, shipping, procurement, and master data.
Current situation
Reactive business model and lack of business transparency
due to sub-optimal execution speed of the current ERP
operational reporting solution
Value proposition
Provide flexible real time analytics, improve business
performance, strengthen competitive advantage, provide
quick wins for business.
Outcome opportunity
Sales people’s efficiency is increased, plans are more
accurate and reporting is more timely.
So, how is this possible? What gives us the opportunity to transform the way we think about enterprise software?In short – innovation. Innovation in hardware and in software.On the hardware side, processor, memory and server technologies have recently taken huge leaps forward. The number of processor cores we can use on a blade, the amount of addressable memory, and processor and memory speed are all increasing. Massive parallelism, scalability and throughput speed are now at our disposal. And the price/performance of this hardware is amazing.At the same time as these advances have been made, SAP has been developing software to take advantage of them. We use a unique combination of approaches including columnar databases, compression, and parallelization of queries to optimize data access and processing on this new hardware. We can perform complex calculations on real-time data, without pre-calculating aggregates or building custom reporting repositories. The raw speed of the hardware not only allows us to process massive quantities of data but also overcome historical issues with some earlier generations of these software approaches – such as the slow update cycles that prohibited use of columnar databases in disk-based systems.Our joint innovation with leading hardware vendors has made real-time business a reality.
(Optional slide)
5 day turnaround to 2 day turnaround.
Other applications such as BusinessOne are already running in-memory technology in the labs.
Of the components displayed on this slide, not all are part of HANA. BusinessObjects Enterprise, the ERP system, the clients etc. are optional components whose presence in the system landscape depends on the customer scenario.The components listed here are: The in-memory computing engine itself, which hosts the actual data stores, a persistence layer, a calculation/execution engine, interfaces and other components The in-memory computing studio which is a front-end delivered with HANA which enables administration of the in-memory computing engine and modeling for the engine. An ERP system in which a load controller and a replication engine are installed to enable data transfer from ERP to HANA Optional components are a NetWeaver BW system or third party systems which can be connected to HANA via SAP BusinessObjects Data Services A BusinessObjects Enterprise system with Data Services installed. Client tools for reporting off HANA. These tools might need components in a BusinessObjects Enterprise system (such as Information Design Tool) or database clients (JDBC, ODBC, ...)In the following slides we take a look at several usage aspects of HANA such as data loading, modeling and reporting and discuss which parts of this setup are important for these aspects.
Of the components displayed on this slide, not all are part of HANA. BusinessObjects Enterprise, the ERP system, the clients etc. are optional components whose presence in the system landscape depends on the customer scenario.The components listed here are: The in-memory computing engine itself, which hosts the actual data stores, a persistence layer, a calculation/execution engine, interfaces and other components The in-memory computing studio which is a front-end delivered with HANA which enables administration of the in-memory computing engine and modeling for the engine. An ERP system in which a load controller and a replication engine are installed to enable data transfer from ERP to HANA Optional components are a NetWeaver BW system or third party systems which can be connected to HANA via SAP BusinessObjects Data Services A BusinessObjects Enterprise system with Data Services installed. Client tools for reporting off HANA. These tools might need components in a BusinessObjects Enterprise system (such as Information Design Tool) or database clients (JDBC, ODBC, ...)In the following slides we take a look at several usage aspects of HANA such as data loading, modeling and reporting and discuss which parts of this setup are important for these aspects.
One of the promises of HANA is to deliver real-time analytic insight on vast data volumes.For the real-time aspect, data provisioning in real time is required. This is the task of Sybase Replication Server. Tables from the ERP system are initially loaded into HANA. All subsequent changes to these ERP tables are immediately replicated into the HANA server. To this end, replication server makes use of the database logs in the ERP system.There is a tool that helps selecting the tables to be loaded and replicated. This tool is integrated into the In-Memory Computing Studio (Modeling).Replication Server only allows connecting one SAP ERP system to HANA. Some additional requirements apply regarding the ERP system such as server OS, DBMS system, ERP version, SAP kernel and Unicode state (only Unicode is supported).Systems not fulfilling these requirements can be accessed via data services. This requires a BusinessObjects installation, with a data services server and data services designer on the client.Note: for practical purposes it will probably not be reasonable to connect to several ERP systems with one HANA box (one via replication, the other(s) via data services) for obvious reasons (same tables existing in all the ERP systems etc).Note: Loading from NetWeaver BW into HANA via data services technically is an application of OpenHub.
Once tables are created in HANA and loaded from the source system, the semantic relationships between the tables need to be modeled.In an ERP system, these relationships are modeled via database views and ABAP code. In HANA, these relations initially do not exist at all.Modeling can be done in several places (bottom-up description): If data services is used to create and fill the table, first modeling decisions can be made here. Data models can be created within the In-Memory Computing Engine. Models are stored in form of views and associated metadata in the engine. The front-end tool to create these models in the In-Memory computing Studio (Information Modeler within that tool). Depending on the front-end tool used to retrieve data from the In-Memory Computing Engine, further modeling decisions can be made in universes (SAP BusinessObjects Information Design Tool) or other semantic layers.
In reporting, client tools create queries against the database. Where the actual query is generated depends on the tool used. BusinessObjects Explorer will directly create a call against a HANA interface. Excel will also directly request data via MDX. Front-end tools which report against Universes will have the SQL request against HANA created in the universe layer. Please note that at the time of creating these slides, it is not yet decided which front-end tools will be supported in combination with HANA. The front-end tools listed in these slides are candidates.The following client side drivers are delivered with HANA: JDBC ( SQL) ODBC ( SQL) ODBO (short for OLEDB for OLAP MDX)Which of the drivers will be used depends on the front-end tool that's being used (and sometimes even the way in which the front-end tool is used).
For Administration of the HANA, the In-Memory Computing Studio has an administration component. Tasks offered by the studio include (but are not limited to): Starting/stopping the In-Memory Computing Engine (upon start, the in-memory stores are reconstructed from the persistence layer) User administration including creating/deleting users and authorizations Table administration, including creating indexes or some part of the configuration for data replication Creating or restoring a backup
You can browse and import extractors in an SAP application’s datastore and use them in an ABAP data flow. Optionally, you can combine the extractors with other extractors or ABAP tables.
Hot Tips:It is most likely that you will access an Analytical view.You can get the table structure by doing a data definition on column view for an Analytical view. You can also do a SQL select statement on column view for an Analytical view.
With the R integration project in SAP HANA, users can run R scripts transparently in the SAP HANA database environment. You can write R scripts yourself or invoke thousands of existing R external packages. There are two scenarios for R integration for two difference use cases. Scenario 1 is to leverage R to extend NewDB’s data mining and statistic analysis capability through the SQLScript interface in a stored procedure way. Scenario 2 is to provide the SAP HANA database as a data source for open source R. You can explore the SAP HANA data in a interactive way.The blue components are the core NewDB components. The green ones are the pure open source R. The orange ones are the components to achieve the seamless integration.
Just like R, BFL can be embedded into SQLScript and be called by an application easily through ODBC or JDBC. Since BFL are C++ components inside the SAP HANA database, it should deliver excellent performance.