Ha100 notes units 1 and 2 sp08

Unit 1: Introduction and Positioning
Introduction to SAP HANA
Unit 2: SAP HANA Studio
SAP HANA Studio
Unit 3: Architecture
Architecture
Persistence Layer
Backup & Recovery
Unit 4: Data Provisioning
Uploading Data from Flat Files
SAP Data Services
SAP Landscape Transformation Replication Server (SLT)
SAP Direct Extractor Connection (DXC)
Unit 5: Modeling
Introduction to CO-PA Scenario
Introduction to Modeler Perspective
Levels of Modeling
Unit 6: Reporting
SAP HANA Database Connectivity Options
Microsoft Excel
SAP BusinessObjects
SAP BusinessObjects Analysis for Office
SAP BusinessObjects Analysis for OLAP
SAP BusinessObjects Explorer
SAP Crystal Reports for Enterprise, Dashboards and Web Intelligence

Introduction and Positioning of SAP HANA
Unit Overview
This unit provides an overview to SAP HANA positioning.
Unit Objectives
After completing this unit, you will be able to:
• Explain the current existing pain points in a system using a classic database
• Explain how SAP HANA can handle the pain points and help to improve profit
• Explain the architecture of SAP HANA as an accelerator in a side-car scenario
• Explain the architecture of SAP HANA as an In-Memory Database
• Understand, what is an RDS
• How you could get and use an RDS
• Explain SAP HANA deployment options
Unit Contents
Lesson: Introduction to SAP HANA
Lesson: SAP HANA Scenarios
Lesson: Rapid Deployment Solutions RDS
Lesson: Deployment Options

Introduction to SAP HANA
Lesson Overview
This lesson presents why SAP HANA has been deployed and how this new
technology can help increasing business opportunities.
Lesson Objectives
After completing this lesson, you will be able to:
• Explain the current existing pain points in a system using a classical
database
• Explain how SAP HANA can handle the pain points and can help to
improve profits
Business Example
Today, a lot of companies need to deal with an amazing amount of data and are
not able to report on them efficiently due to data volume
Information Explosion
Figure 1: Reality #1: Information Explosion
First, the information explosion. Massive amounts of data is being created every year,
and how fast your business reacts to it determines whether you succeed or fail. This is a
big problem and it is getting bigger.
• IDC estimates that worldwide digital content added up to 487 billion gigabytes in
2009.
• They predict this will double in 18 months, and every 18 months thereafter
• IDC, in its 2013 Top 10 predictions, estimates that the digital universe will reach
4 ZB (4 trillion GB).

• On the horizon of 2020, the digital universe will reach 40 ZB (40 trillion GB) of
data, which represents 50 times the volume of the digital universe in 2010.
So, how fast your business reacts to the massive data determines whether you succeed or
fail.
In a Sloan Management survey in 2010 60% of executives said their companies have
more data than they know how to use effectively. With data doubling every 18 months,
that percentage is going to keep growing.
According to EMC, by the end of 2011 there was 1.8 Zetabyte of digital data. 1 Zetabyte
is a trillion gigabytes.
Kilobyte>Megabyte>Gigabyte>Terabyte>Petabyte>Exabyte>Zetabyte>Yottabyte
Figure 2: Reality #2: Consumerization of IT
At the same time, the consumerization trend is driving up expectations as to what
enterprise IT can help the business to do. People want instant access to information at any
given moment, whether that is a moment of risk or a moment of opportunity. If the
moment has passed and your business has not taken the right action, it has failed.
People also expect their business experience to be as satisfying as their personal
experience, for example people are now used to getting instant search results from
Google, so expecting similar results.
People want instant and right answers, which they can access from anywhere, any time.

Figure 3: Reality #3: IT Cannot Deliver
IT cannot deliver what the business needs because the cost of managing that data
explosion is too high.
Factors such as cost-effective management of data of large volume, immediate answer to
any question, and current and complete information put IT in a tough place.
IT cannot deliver what the business needs. Why? Because the cost of managing that
data explosion is too high. Because there is no practical way to instantly analyze
everything that is going on relative to the business. IT can deliver some of the
information. The most critical slice of information can be delivered in near real time. But
its not enough. Data is growing. Demand is increasing. We must find a way to deal with
this – a way to process and analyze massive amounts of data in real time.

Figure 4: Your Reality with SAP HANA
That is the role of SAP HANA. Using groundbreaking in-memory hardware and software
we can manage data at massive scale, it helps you analyze it at amazing speed, and give
the business not only instant access to real time transactional information and analysis but
also more flexibility. Flexibility to analyze new types of data in different ways, without
creating custom data warehouses and data marts. Even the flexibility to build new
applications which were not possible before.
You need to find a way to resolve the difficult equation of data volume, speed, and
flexibility, which in fact is the role of SAP HANA.
You can use groundbreaking in-memory hardware and software to manage data at
massive scale. It helps you analyze data at amazing speed. It also gives the business not
only instant access to real-time transactional information and analysis but also more
flexibility to analyze new types of data in different ways and flexibility to build new
applications.

Figure 5: SAP In-Memory Appliance (SAP HANA)
We keep throwing around words like massive amounts of data and amazing speed. What
kinds of scale, speed and improvement are customers seeing ?
So, what is inside HANA. The architecture diagram in this slide explains the main
components and capabilities of SAP HANA.
SAP HANA includes these components:
• SAP HANA database software and hardware from HP, IBM, Fujitsu, Cisco, Dell,
Hitachi, NEC, and other certified partners
• SAP HANA Studio for Data Modeling and Data Management
• Real-time Data Replication
• SAP Data Services for ETL capabilities from SAP Business Suite, SAP
NetWeaver Business Warehouse (or SAP NetWeaver BW), and 3rd Party
Systems
These are the main keywords for the capabilities of SAP HANA:
• Real-time data replication
• Unprecedented speed for data analysis on large data volumes
• Create flexible analytic models based on real-time and historic business data
• Development platform for new category of applications, for example, planning,
simulation, to enhance performance
• Minimizing data redundancy

Figure 6: SAP HANA Proof Points
Here are some proof points:
• First, amazing speed. To give you an idea of the faster reporting speed, one of our
pilot customers reduced the time it took to run a report from one hour to one
second. That is 3600 times faster. Lets put that in perspective. SAP talks about
helping you to “run better”, so lets use that as an example. When an average
person runs, they move at about 7 miles per hour. 3600 times faster would be
about 25,000 miles per hour. That is the fastest any human being has ever
travelled, and it was only done once - by the astronauts on Apollo 10, on their
return from the moon in 1969.
• Amazing amounts of data. During proof of concept testing for HANA we
executed queries against 460 billion rows of data in less than one second. That is
like being able to analyze every repair and service visit for every car on earth in
the last 12 months, in one second. Or to process every address that everyone alive
today has ever lived at, in one second. Or to calculate the amount of taxes paid, by
everyone on the planet, since 1950, in one second.
• And finally, amazing value. Having the ability to create new real-time processes
and simplify your IT landscape has a big impact. According to a study by Oxford
Economics, companies that implement real-time systems see an average 21%
revenue growth, and a 19% reduction in IT cost.
Here is an example from a real customer. You can see data compression and the query
performance gain by using SAP HANA vs. RDBMS.

Figure 7: Query Acceleration Example – Large Bank – 1 Month of Customer
Information
Why wait for data?
• All customers want to see their current business data immediately in real-time.
Nobody wants to wait until data is uploaded into BW.
Why wait for new systems?
• Latest hardware and latest database technology already now support real-time
reporting on massive amount of data.

Figure 8: SAP Naming Update: SAP HANA
SAP HANA
• Above slide shows the official names used for SAP HANA components.
• SAP HANA is a flexible, data-source-agnostic appliance that enables customers
to analyze large volumes of SAP ERP at non SAP Systems data in real-time,
avoiding the need to materialize transformations.
• SAP HANA appliance software is a hardware and software combination that
integrates a number of SAP components including the SAP HANA database, and
several data replication systems such as SAP Landscape Transformation
Replication Server, SAP HANA Direct Extractor Connection (DXC) and SAP
Data Services or Sybase Replication technology.
• The SAP HANA database is a hybrid in-memory database that combines row-
based, column-based, and object-based database technology. It is optimized to
exploit the parallel processing capabilities of modern multi-core CPU
architectures. With this architecture, SAP applications can benefit from current
hardware technologies.

Figure 9: DAILY CHALLENGES
These are the various challenges that SAP customers come across daily:
• Complex system landscapes, that is, disparate silos and different types of
databases spread out in the organization
• Immediate results, such as old or stale results in analytics
• Massive growth of data volume
• Skilled workforce, that is, new workforce expecting better, faster experience.
• High flexibility

Figure 10: CONSEQUENCES
These are the consequences of traditional data warehouse analytics:
• Sub-optimal execution speed that results in lack of responsiveness, user
frustration, and unsupportable business processes
• Lack of transparency as a result of need for aggregation, outdated figures, and
guessing current situation
• Reactive business model that occurs because of missing opportunities and
competitive disadvantage
Figure 11: HARDWARE INNOVATIONS
With innovations in the hardware technology, the computer architecture has changed in
recent years. The multi-core CPUs are widely used and enable parallel processing with

fast communication between processor cores. The modern servers having up to 2TB of
system memory allows complete databases to be held in RAM.
SAP HANA software can make use of this new hardware technology for massive parallel
processing and faster response speeds.
Moore's law was initially forumulated in 1965. According to this law, "the number of
transistors in a chip doubles every year". However, in 1975 this was adjusted by David
House who said it will double every two years. A widespread variant of Moore's law
states that the transistors will double every 18 months.
Figure 12: Improvements in Technology
Historically database systems were designed to perform well on computer systems with
limited RAM, this had the effect that slow disk I/O was the main bottleneck in data
throughput. Consequently the architecture of those systems was designed with a focus on
optimizing disk access, e. g. by minimizing the number of disk blocks (or pages) to be
read into main memory when processing a query.

Figure 13: Computer Architecture is Changing
Computer architecture has changed in recent years. Now multi-core CPUs (multiple
CPUs on one chip or in one package) are standard, with fast communication between
processor cores enabling parallel processing. Main memory is no-longer a limited
resource, modern servers can have 2TB of system memory and this allows complete
databases to be held in RAM. Currently server processors have up to 64 cores, and 128
cores will soon be available. With the increasing number of cores, CPUs are able to
process increased data per time interval. This shifts the performance bottleneck from disk
I/O to the data transfer between CPU cache and main memory.

Figure 14: UNDERSTAND Column Data Storage
The concept of column data storage has been used for quite some time. Historically it was
mainly used for analytics and data warehousing where aggregate functions play an
important role. Using column stores in OLTP applications requires a balanced approach
to insertion and indexing of column data to minimize cache misses.
The SAP HANA database allows the developer to specify whether a table is to be stored
column-wise or row-wise. It is also possible to alter an existing table from columnar to
row-based and vice versa.
Figure 15: Fast – SW Side Optimization for Memory
Conceptually, a database table is a two-dimensional data structure with cells organized in
rows and columns. Computer memory however is organized as a linear structure. To store
a table in linear memory, two options exist, a row-oriented storage stores a table as a
sequence of records, each of which contain the fields of one row. On the other hand, in a
column store the entries of a column are stored in contiguous memory locations. It
enables faster in-memory processing of operations such as aggregates. Columnar layout
supports sequential memory access, and a simple aggregate can be processed in one
linear scan. Massive Parallel Processing (MPP) is possible per column.

Figure 16: Key Facts: When to Use Row Store, when Column Store?
Figure 16a: Classic and New approach to move data into database
Row Store
• If you want to report on all the columns then the row store is more suitable
because reconstructing the complete row is one of the most expensive column
store operations.
• Mainly distinct values in the source database lead to low compression rate.
• All the columns of the table are relevant.
• No aggregation or search is required.
• Table has a minor number of records, for example, some system tables are stored
in the row-store.
Column Store

• If you want to fill the table with huge amounts of data that should be aggregated
and analyzed, then a column-based store is more suitable.
• Handle large number of columns
• Suitable for analytical application
Figure 17: Partitioning
You can avoid the bottlenecks in partitioning by spreading table contents across blades
and working on smaller sets of data in parallel.

Figure 18: Parallel Processing
The above figure shows an example of parallel processing by different cores when you
have two columns and one column which has been partitioned. Data is only partially
blocked, so parallel processing is possible. Therefore, individual columns can be
processed by different cores.
Figure 19: SAP HANA Database Performance

The reason SAP HANA is fast is because of the hardware and software innovations. This
figure 19 summarizes the reasons behind the massive performance gain. Our hardware
partners are the experts in hardware and chipsets, while SAP is an expert in business
application integration. Therefore, SAP could deliver on its vision of the real-time
enterprise with in-memory business applications.
Figure 20: COMBINE BUSINESS & TECHNOLOGY
The figure 20 shows some of our certified hardware partners. The list is growing because
more vendors want to come onboard. Note, SAP HANA is not the only in-memory
offering by SAP but includes BWA, Live Cache as well. With strong partnership with
such hardware vendors, SAP HANA successfully combines its business with technology.

Figure 21: CLASSIC EDW (Enterprise Data Warehouse)
Figure 21 depicts a traditional enterprise IT organization with two SAP ERP systems and
a third-party ERP. Each ERP has its own database and there are as many Data Marts to
support local Business Intelligence needs. An additional EDW with its own database
supports corporate BI needs.

Figure 22: SAP HANA Appliance
You can see the intermediary stages where SAP HANA is used as the technology layer
for all the Data Marts and central EDW.
Figure 23: PLANNED – SAP HANA PLATFORM 2.0 +
The figure 23 depicts the final implementation stage where HANA is the foundation for
all the applications, such as ERP, data warehouse, and new applications.

Figure 24: How Does SAP HANA Compare to BWA?
SAP HANA database has components from various other software applications.
For example:
• Row Store and SQL Parser has some code from P&time database (acquired by
SAP in 2005)
• SAP HANA has standard interfaces and real persistence layer
• Column Store has code from BWA Trex Engine
• Persistence Layer (Data and log volumes) has code from MAX DB
These are the various features related to Data Models or Content in SAP HANA and
BWA:
• BWA relies completely on SAP BW.
• You can only load InfoCubes into BWA.
• BWA has BW on top.
• SAP HANA 1.0 is intended as a Data Mart but BWA is not.

Figure 25: Rapid Deployment Solutions
Rapid Deployment Solution (RDS) allow you to implement a predefined and
preconditioned content on several different functional or technical perimeter. They
permits to respond quickly to expectations through SAP delivered content.

Lesson Summary
You should now be able to:

SAP HANA Scenarios
Lesson Overview
• This lesson discusses about the different system configuration and possible SAP
HANA scenarios.
Lesson Objectives
Business Example

A migration from BW to BW powered by SAP HANA needs careful planning and
adherence technical requirements. A side-car scenario could be a first step to answer to
urgent and important business need. Then, once the BW migration is effective, the side-
car perimeter could be integrate to a schema of the SAP HANA Database used with BW.
CO-PA accelerator is an example of a side-car scenario. SAP HANA is used as a
secondary database where data is replicated in real-time. Information and results could be
consumed on an SAP Business Objects platform or directly in SAP ECC.
Figure 26: HANA Innovation Scenarios Overview
The above graphic gives a few examples of how SAP HANA can play a role in the
Enterprise Information System.
The innovation scenarios include HANA Accelerators, HANA Analytics, BW on HANA,
HANA Applications, and Business Suite on SAP HANA (now new version referred as
SAP S/4 HANA).
The integrated scenarios include Business Suite on HANA.

Figure 27: SAP In-Memory Strategy
The SAP in-memory strategy includes
• SAP HANA real-time operational analytics under side-car;
• SAP BW powered by SAP HANA under primary persistence; and
• SAP Business Suite powered by SAP HANA under platform.

Figure 28: SAP HANA Side Car Scenario
In figure 28 example of an SAP HANA sidecar scenario where the information views are
100% virtual. Without HANA, the data can be stored physically in a cube.

• In SAP HANA side car, no application server is involved.
• SAP HANA side car can be combined with SAP HANA as a modeling platform
or programming platform.
• It is used in new applications
Figure 29: SAP HANA Scenarios: Agile Data Marts
Data Warehouse environments are typically rigid against change. However, there may be
two or four times during a year, where models are allowed to be modified.
The data is transformed before loading into HANA. It is helpful to have an environment
in which the data models may adapt easily without impacting the data in tables in the
production environment.
The level of change depends on the business problem in which sales regions, product
bundling, and cost centers are subjected to constant changes. It also helps business to load
external data and combine it with internal data sources.
Agile data marts typically utilize traditional ETL as it does not contain any time-critical
data.
In benchmarking scenarios, the internal data (like sales data) is benchmarked against
market indices obtained from external agencies. Such data is not loaded into the central
data warehouse, but rather it is used by analysts or managers in local environments.
The core value proposition for agile data marts is that it has more flexibility compared to
EDW environment.
Businesses are exposed to constant change. Sales regions change, product bundling may
change, and cost centers are subject to almost constant change. Sometimes it may be
interesting to simulate these changes before they take place. In these cases it is helpful to

have an environment in which models may be adapted easily without impacting the data
models in production.
It may as well be interesting for business to load external data and combine it with
internal data sources. These may be benchmarking scenarios in which internal data (like
sales data) is benchmarked against market indices obtained from external agencies. Such
data is typically not loaded into the central data warehouse, but rather gets used by
analysts or managers in local environments.
SAP HANA provides a kind of sandbox environment for rapid prototyping of new models.
Example for Agile Data Mats
SAP HANA can host standard analytic models, typically implemented as a star or snow-
flake-schema. A star schema consists of one fact table, and a set of dimension tables
(currently SAP HANA can not support versioned master data that would require a
temporal join).
STEP 1
Load the tables into SAP HANA. All transformations take place before loading the data
into SAP HANA.
STEP 2
Create attribute views for the different dimension tables.
STEP 3
Create an analytic view by selecting the fact table as data foundation (currently SAP
HANA supports only those models which host all key figures in one fact table), and join
the attribute views to the data foundation.
RESULT
The resulting data mart is very easy to consume.

Figure 30: SAP HANA Scenarios: Operational Data Marts
In operational Data Marts, data model reflects the level of detail in data that the actual
application contains. Data transformation does not occur during the loading step. Real-
time replication of time-critical data utilizes SLT. Data that are not time critical, such as
standard load routines, utilizes ETL. Views calculate results for reports in real time on the
actual operational data.
The real-time reporting on operational data, is the core value proposition of SAP HANA.
SAP HANA is perfectly suited to host operational data marts. In contrast to previous
examples, operational data marts are not based on analytic (de-normalized) data models,
but rather run directly on top of the operational data. The operational data gets
transformed in a way that is suitable to answer a query, right when that query hits the
system. The transformed data never gets persisted.
STEP 1
Load the needed tables into SAP HANA. There are four options for loading the data:
1. SLT provides real-time replication, where changes in the original table get
propagated to SAP HANA instantaneously.
2. Data Services provide standard ETL for loading the tables at defined moments
in time
3. Load data by using the SAP Direct Extractor Connection
4. Load data from Flat Files
STEP 2

Create attribute views for the different dimension tables.
STEP 3
Create an analytic views incorporating the attribute views.
RESULT
The resulting data mart is very easy to consume.
Why would you want an operational data mart?
• Most of the technologies currently used for operational reporting are not really
suitable for the task at hand. Classic DWH environments are complex and may
require significant effort to model operational data marts.
• If operational reports hit the database directly, which run the core business
applications, reduced performance may be the experience for all people working
on the system. This performance hit is caused by the heavy workload from joins
on many small tables, like it is the standard in highly normalized data models.
• SAP HANA based operational data marts take the workload of such reports away
from the main database. The replication guarantees that the data in memory
reflects on the last transactions which took place. And finally, the in memory
computing provides very fast results even on high volumes of detailed data, still
providing the option to touch on every detail which is contained in the data.
• SAP HANA can provide real time insights into what is going on in business.

Figure 31: SAP BW on HANA
Figure 31 shows integration of SAP BW on SAP HANA through SQL and MDX.

Figure 32: Consequences on Existing Landscape when Migrating to SAP HANA
Figure 32 describes the consequences for the existing landscape when SAP NetWeaver
BW is deployed on HANA or Suite on HANA:
• BW on HANA was originally delivered with SPS04 in 2012.
• Before database migration to HANA DB the BW application has to be updated to
7.31 (as a minimum but now preferably version 7.4)
• The system usage is the same like BW 7.31 on non SAP databases.
• Migration of the database to SAP HANA that only runs on SUSE Linux (SLES) is
required
• It is not possible to co-deploy the application servers, for example, central
instances, on database hardware
There are also some minor changes reported:
• The available application servers are reused.
• The sizing of current application servers remains valid.

Figure 33: SAP HANA as a Primary Database – Business Suite on SAP HANA
These are the various characteristics of SAP HANA as a primary database:
• SAP HANA as a primary database is a three-tier architecture.
• It is not necessary to change the familiar frontend, although it is possible to do.
• Data intensive logic can be pushed to the database.
• The applications of SAP HANA as a primary database include SAP Business
Suite powered by SAP HANA and SAP Netweaver BW powered by SAP HANA.

Figure 34: SAP HANA as an Application Platform
These are the next generation HANA applications:
• NetWeaver Application Server ABAP that leverages HANA
• iOS applications that run against HANA
• Java applications that run against HANA
• The core value proposition for SAP HANA is simplification

Lesson Summary

Rapid Deployment Solutions RDS
Lesson Overview
In this lesson you will learn about what an RDS means and how you can use it.
Lesson Objectives
Business Example
You want to quickly gain business value from your SAP HANA deployment by
implementing a Rapid Deployment Solution.
Figure 35: SAP and a Global Partner Ecosystem Offer Rapid Deployment Solutions to Meet Specific
Business Needs
SAP Software and SAP Predefined services combined with pre-configured content and
enablement content
With SAP Software, SAP Rapid Deployment solutions (or RDS) are a (ready-to-consume)
combination of SAP Predefined services, pre-configured content, and enablement content
to accelerate the implementation and lower risk.
Implementation is supported by standardized methodology and best practices, honed over
decades. An optimized mix of global resources, remote support, and onsite consulting
give you access to experts who can help you implement your solution on time and on
budget.

Each of these solutions include educational material and training scripts for the
functionality that matter most users start right away, without the delays associated with
customized training.
SAP Rapid Deployment solutions bring it all together preconfigured software, fixed-
scope implementation services, and the materials you need for a successful
implementation... all at a predictable price, effectively eliminating cost overruns and
project delays.
With these solutions, you receive the best of traditional and subscription licensing
models, so you will know the cost and scope of your solution up front. These complete
solutions enable the flexibility to accommodate future growth.
Because SAP Consulting uses preconfigured content, you as a business get what you
need to run your business out of the box, delivered quickly. This preconfigured content is
value adding because it gives you powerful functionality based on the leading SAP ERP
rapid-deployment solution for operational reporting with SAP HANA.
SAP consultants only install what you need so that you can start faster with what's more
important and expand as you need later. And the biggest benefit to our customers is that
SAP Consulting can provide seamless access to SAP ERP back office information.
The preconfigured content allows the project to be quick and lean because of the clearly
defined scope, the knowledge transfer to users and the fast-track methodology. Finally,
the flexible software pricing and fixed priced, low cost services, ensures that your SAP
ERP rapid-deployment solution for operational reporting with SAP HANA project will be
cost effective, both monetarily as well as in terms of Business and IT resources.
Figure 36: SAP HANA – Time Becomes Your Competitive Advantage
Time becomes your competitive advantage
• Analyze information in real-time at unprecedented speeds on large volumes of
non-aggregated data
• Create flexible analytic models based on real-time and historic business data

• Minimizes data duplication, and
• Lay foundation for new category of applications
Figure 37: To be so Fast Like a Cheetah you Have to Know How is the Shortest Way to Your Prey
(the Data)
Figure 37 shows the model structure of CA_STOCK_OVERVIEW in HANA ERP V2.
Joins inside calculation view cost performance, thus all the joins of attribute views to
analytic views are removed into analytic views directly in SAP HANA ERP V3.

Figure 38: The New Quite Faster Model
Figure 38 shows the model structure of CA_STOCK_OVERVIEW in HANA ERP V3.
SAP ERP rapid-deployment solution for accelerated finance and controlling with SAP
HANA is a combination of software with the rapid deployment solution consulting
deliverable to produce the overall solution:
There are the four individual accelerators:
• Financial Accounting Accelerator
• Controlling Accelerator
• Material Ledger Accelerator
• Production Cost Analysis
There is also specific content delivered, for example:
• Implementation content like configuration guide
• Service content like project plan, consultant guide, or kick off presentation
• Enablement content like customer facing material
The service has:
• Fixed-scope and fixed-price services for the individual implementation scenarios
The Service Delivery can be performed by SAP or qualified partner.

Figure 39: SAP ERP Rapid-Deployment Solution for Operational Reporting with SAP HANA
Implementation Content
To give our customers as much flexibility as possible we have redesigned our service
package by creating a modular offering. With the base package of this rapid deployment
solution you can choose up to 5 reports to be implemented. If you need additional reports
you can add as many as needed.
The SAP HANA business content for Sales and Distribution (SD) enables sales managers
and sales representatives to check basic key figures for sales in real-time. Whereas sales
managers use sales analytics to get instant overview information regarding the various
performance indicators for their sales teams, the sales representatives focus on detailed
checks of the results of their sales activities.

Figure 40: Flexible Reporting
The reporting templates are available for all models and are delivered using a
combination of
• SAP Explorer
• Web Intelligence
• Crystal Reports and
• Dashboards.
In addition, there are some delivery options which are documented in RDS which
include:
• analysis for Office,
• Mobile, and
• Exploration Views.

Figure 41: Information about RDS Packages
You can get information about RDS packages from the SAP portal mentioned from
http://service.sap.com/SOLUTIONPACKAGES
Figure 42: The Way to Get an RDS (1/4)
Figure 42 shows the first step to get an RDS. In SAP Service Marketplace, under Home tab, choose Sales,
Service, and Marketing.

Expand SAP ERP for Operational Reporting with HANA and select Solution Deployment. You can see
the initial screen for Operational Reporting with SAP HANA as in Figure 43. It helps you find all the
relevant information that you need to implement SAP ERP rapid deployment solution content, service
asset, and enablement material.

You can see the first step, Discover, of the step–by-step guide to implement an RDS,
which describes the value of RDS and the benefits of implementing it. It also defines the
role of SAP sales representatives in this phase.
The screenshot in Figure 45 shows the next step, Start, in obtaining RDS, which
confirms installation of the software. This step prepares the environment for the next step,
Deploy. It also defines the procedure that the SAP project lead and the customer project
team should follow.

Figure 46: Service Overview – Deploy (1/2)
You will quickly generate a meticulous project plan, including a detailed breakdown of
activities, deliverables, and timelines. When should you schedule the kickoff workshop –
and how much later should you plan scoping and refinement? What about user
acceptance testing? End-user training? These solutions include the content to take the
guesswork out of scheduling, substituting transparency and predictability that inspire key
stakeholders to get on board and put their support behind your project.
While planning a project, you need to generate a project plan and include details on
breakdown of activities, deliverables, and timelines. RDS helps you schedule the kickoff,
substitute transparency and predictability that inspire key stakeholders to get on-board
and put their support behind your project
To deploy solutions, you must follow these steps:
• Activate solution, where you need to check installation and landscape, replicate
tables, import data models and SAP BusinessObjects BI reports, and perform
initial data load
• Confirm activation where SAP performs functional test
• Knowledge transfer, where SAP imparts knowledge transfer to IT and key
business users
• Customer acceptance testing, where customer executes and performs acceptance
testing
Figure 47: Service Overview – Deploy (2/2)
After completing customer acceptance testing, you should switch to production where
you need to replicate tables and import data models, SAP BusinessObjectsBI reports, and
dashboards, and perform initial data load. Finally, you should create and execute cutover
plans.

Figure A: Customer Example Presentation
Here you see an example of a real life business case of HANA implementation leveraging
the SAP ERP RDS for operational reporting. For example' the company deals with
industrial machinery and components. It has a presence in 60 countries and its
headquarters in US. It has 15,000 employees worldwide and its annual revenue is 3
billion dollars.
Figure B: Project Context and Key Objectives

Figure C: Project Scope
Figure D: SAP ERP RDS for Operational Reporting

Figure E: SAP ERP, BW, and HANA Together in Planned Landscape
Figure F: Project Timeline

Figure G: Before and After SAP HANA Implementation
Figure H: Key Benefits of SAP HANA Rapid Deployment Solution

Lesson Summary
• How to deploy an RDS to speed up and secure an implementation of SAP HANA.

SAP HANA Deployment Options
Lesson Overview
This lesson discusses the different SAP HANA deployment options available.
Lesson Objectives
Business Example
You want to understand the different deployment options that are available.
SAP HANA Deployment Options
SAP HANA is available in several deployment options depending on scenarios and
business needs.
Figure 48: Overview of Deployment Options
SAP HANA is available in several deployment options depending on scenarios and
business needs.
One of the options is on-premise that includes bare metal or appliance, that is virtualized
with VMware vSphere 5.1 or HANA tailored datacenter integration.
Another option is on-demand or cloud that includes

• HANA Enterprise Cloud,
• HANA Developer Edition,
• HANA One with community support or with premium SAP support, or
• HANA TEA appliance or SAP store.
Figure 49: SAP HANA Developer Edition
SAP HANA Developer Edition is used for product evaluation, trials, students, data
exploration projects, and so on.
The software is free, but the developers have to pay to the cloud provider for server
usage. This software is meant for small to mid-sized data footprint and for nonproductive
use.
SAP HANA Developer Edition provides community support through the website,
http://saphana.com/cloud.
• It is available on four public cloud providers.

Figure 50: SAP HANA One
SAP HANA One focuses on startups, Independent Software Vendors (ISVs), and native
cloud scenarios.
• It is certified for productive use.
Figure 51: SAP HANA Enterprise Cloud
SAP HANA Enterprise Cloud provides enterprise-class cloud offering for mission critical
and global 24 × 7 operation with these features:

Global availability, that is, four data centers in US and Europe with two more planned in
APJ
• Custom data center arrangements for compliance
• Advanced business continuity and support
• Standards-based cloud operation
• Monthly external penetration tests
• All HANA T-Shirt sizes are supported.

Lesson Summary

Unit Summary
• How you could get and use an RDS for SAP HANA

SAP HANA Studio
Unit Overview
This unit provides an overview to using SAP HANA Studio.
Unit Objectives
After completing this unit, you will be able to:
• Understand the structure of SAP HANA Studio
• Understand how to configure Perspectives
• Understand how to create a Delivery Unit and a Package
Unit Contents
Lesson: SAP HANA Studio
Procedure: Exercise 1: Look and Feel

SAP HANA Studio
Lesson Overview
Introduction to the SAP HANA graphical user interface SAP HANA Studio.
Lesson Objectives
• Understand the structure of SAP HANA Studio
• Understand how to configure Perspectives
• Understand how to create a Delivery Unit and a Package
Business Example
You are a consultant at a client site and need to launch SAP HANA Studio for the first
time.
You need to add the customer's SAP HANA instance to your Studio installation so that
you can work on the server and create a new Delivery Unit and Package for your
information Models.
Figure 52: SAP HANA Studio
The SAP HANA Studio is delivered as part of the SAP HANA installation package. The
SAP HANA Studio provides an environment for administration, modeling, development,

and data provisioning; can be installed on any client PC that has a connection to the SAP
HANA system; and is a Java-based application that runs on the Eclipse platform. (More
information: http://www.eclipse.org).
When you start the SAP HANA studio for the first time, you must choose a perspective.
Predefined UI layouts with several views are referred to as perspectives. One or several
perspectives address the needs of a particular SAP HANA user role. For example, a
System Administrator may use the SAP HANA Administration Console perspective.
You can move each view using drag and drop option. You can also customize a
perspective by adding or removing views. Perspectives available in the SAP HANA
Studio include SAP HANA Modeler, Administration Console, Resources, and
Documentation Overview.
• The Modeler Perspective is used by Data Architects to create Information
Models.
• The Administration Console is used by SAP HANA administrators to
administrate and monitor the engine.
• The Documentation Overview links to the current available documentation.
• Additionally, you also have perspectives for Development (HANA Applications),
Java Development and Lifecycle Management
Figure 53: Look & Feel – Administration View
When you start the SAP HANA studio for the first time, you must choose a perspective.
Predefined UI layouts with several views are referred to as perspectives. One or several
perspectives address the needs of a particular SAP HANA user role. For example, a
System Administrator may use the SAP HANA Administration Console perspective.

You can move each view using drag and drop option. You can also customize a
perspective by adding or removing views. Perspectives available in the SAP HANA
Studio include SAP HANA Modeler, Administration Console, Ressources, and
Documentation Overview.
The Administration Perspective is used to administer and monitor SAP HANA instances.
When you start SAP HANA Studio for the first time, there will be no connection to a
SAP HANA system maintained yet.
Note: It is possible to integrate several systems into one Studio.
You can select a Cheat Sheet view via Window → Show view → Other.
Help → Cheat Sheets creates an additional view on the right side. Here you can choose
adding system and Folders. Reading the Cheat Sheets can provide you information on
how to create a new folder or add a new system into the navigator view.
To integrate a SAP HANA system into the studio you need to know the server where the
engine is running and the instance number. You need to know a user/password
combination to get a connection to the instance.
You can import (File → import → SAP HANA Studio → Landscape) a system
landscape which has been exported before from another or the same studio.
Note: To get the imported landscape working you need to insert the passwords for
all connections again. This can be done by right clicking on the instance, and
amending the password in Database Logon User
As in many database structures, the catalog contains tables, views, indexes, and so on. All
these objects are organized into schemas. Schemas help to categorize database content
according to customer defined groupings that have a particular meaning for users. They
also help to define access rights to the database objects.
The Content folder of the catalog enables you to store all the HANA-specific modeling
objects. In the Security folder, the System Administrators define users and roles.

Figure 54: Look & Feel – Navigator View – Default Catalog
On the left side you will find the navigator view. Here all the systems which have been
registered (manual, or via import) are listed. We will take a closer look to the tree
structure each system has.
The physical tables are located in the Navigation Tree under the Default Catalog node.
Expand this node and one will find a list of schemas. Schemas are used to categorize
tables according to customer defined groupings.
Note: During metadata import one defines which schema to hold created tables.
Different schemas can be useful for grouping tables into categories that have
meaning to users. This simplifies the process of identifying which tables to use
when defining Information Models. One model can incorporate tables from
multiple schemas. The schemas do not limit your modeling capabilities.
The created column views are always located in schema _SYS_BIC, their meta data in
schema _SYS_BI.
The physical tables are the only storage area for data within SAP HANA. All the
information models that will be created in the modeler will result in database views. As
such, SAP HANA does not persist redundant data for each model and does not create
materialized aggregates.

Figure 55: System Monitor
There is an integrated System Monitor which gives you an administration view about the
system landscape.
When you use the System Monitor button all systems which are listed in the navigator
tree are listed by default in the system monitor overview. You get the most important
information about your systems. Which information is shown can be configured by right
clicking in the System Monitor view selecting Configure Table.
It is also possible to configure which systems will be shown in system overview by right
clicking and selecting System Filter.
The System Monitor view provides a summarized view of the system landscape. By
default, all the systems that are listed in the Systems view appear in the System Monitor
view. The System Monitor view provides the most important information about system
status, alerts, disk space, memory, and CPU usage.
You can customize this view by adding or removing columns. To customize the System
Monitor view, choose the Configure Viewer button. Alternatively, right-click the System
Monitor view and choose Configure Table.
You can filter the list of systems that are shown in the view. To filter the systems, right-
click the System Monitor view and choose System Filter.
System Monitor View (under Administration Condole) provides information (tabs) on the
following:
1. Overview
2. Landscape
3. Alerts
4. Performance
5. Volumes
6. Configuration
7. System Information
8. Diagnosis Files

9. Trace Configuration
10. etc. etc......
Figure 56: Look & Feel – Pre-Delivered Administration Console
The Administration console is pre-delivered by SAP.
You can access the administration console by
• Selecting the Administration icon in the top right corner
• Double click on the system in the System Monitor
• Double click on the system in the Navigator view
In the administration console you are administrating HANA instances:
• Starting and stopping the instance
• Backup/recovery of the instance
• Monitor the system
• Configure the engine instance
• Doing the problem analysis

Figure 57: Look & Feel – Perspectives are Built up Based on Views
To open a perspective, first choose Windows → Open Perspective . Then, select a perspective from the list,
or choose Other... You can open several perspectives at the same time and switch from one perspective to
another. To switch from one perspective to another, in the Perspective Switcher in the upper-right corner of
the screen, choose the perspective you want to open.
Figure: Adding a view to a Perspective

You can add a view to a perspective. To add a view to a perspective, choose Windows → Show View. The
Show View window appears displaying a list of views. Select a view from the list, or choose Other....
Figure: Customize the System Views
You can customize some views. To customize views, choose the View Menu button and
then select Customize View...

Figure: Resetting a Perspective
To reset a perspective, choose Windows → Show View. The Show View window appears displaying a list
of views. Select Reset Perspective
The Systems View lists all the systems that have been registered manually, or by a
landscape import. In the SAP HANA Studio, the Systems View is the central point of
access. It is placed on the left side of the Navigator screen.
Figure 58: Modeler (Modeler Perspective)
Above is the modeling section of the SAP HANA Studio.
Note: The Quick launch of the modeler is open by default for the first instance in the
navigation tree.
If you want to change to another system, click on Select System.
In the center of the screen you see a quick launch tab that allows the user to quickly jump
to various sections including tools to:
• Create new Information Models
• Import and export source schemas, models, data
• Configure the server
• Access SAP HANA documentation
On the left of the screen you see the navigation tree. Note that there are two main
sections in the navigation tree. The Default Catalog node navigates to the physical

tables, views, etc. The Content node navigates to Attribute Views, Analytic
Views, Calculation Views, Analytic Priviliges, Procedures and Decision Tables.
Figure 59: Navigator View – Models
The Content node displays the data from a data modeling perspective.
Here the user will create:
• Attribute Views
• Analytic Views
• Calculation Views
• Analytic Privileges
• Procedures
• Decision Tables

Figure 60: Look & Feel – Perspectives are Built up Based on Views
Note:
• Views are the basic screen elements. A collection of displayed views combined
with their placement within the screen builds a perspective.
• Each view can be moved around via drag & drop.
Figure 61: Look & Feel – Tips & Tricks (Resetting a Perspective)

Note: Reset your perspectives will restore the screen to the default layout. SAP HANA
Studio also includes a development perspective with debugging functionality.
Figure 62: Development Perspective
From the development perspective it is possible to check in and out development objects,
connecting to a repository.
Figure 63: Development Repository Integration

Ha100 notes units 1 and 2 sp08

More Related Content

What's hot

Similar to Ha100 notes units 1 and 2 sp08

Recently uploaded

Ha100 notes units 1 and 2 sp08