SAP Business Suite powered by SAP HANA Cookbook

Transcription

2015-08-04
SAP Business Suite powered by SAP
HANA Cookbook
Content
1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1
Migration vs. Greenfield vs. Sidecar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
1.2
Migration Project Phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3
Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Value Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SAP Fiori. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
System Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Technical Landscape Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Project Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.4
Build. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Technical System Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
SAP HANA Live Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Code Migration and Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Test Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
1.5
Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Content
1
Introduction
Migrating to SAP Business Suite powered by SAP HANA is similar to any other migration project, but with a few
additional technical options and new tools. In this cookbook, we want to explore the typical phases of a SAP
Business Suite powered by SAP HANA migration project.
This cookbook focuses on the following aspects:
● What to bear in mind in each phase, and what the value and purpose of the activity are
● Which skills and resources you require
● How you can determine the costs and effort for each phase
● Which tools and services you can use to increase efficiency
● Which documents you can access to acquire a better understanding
Apart from the text content provided in this cookbook, you can also have a look at our comprehensive video
library that is accessible in the information section (
).
Table 1: Video Library
Video
Description
SAP Business Suite Innovation and Renovation
SAP Business Suite Innovation Road Map
This video is about highlights of recent achievements and
gives an outlook on new innovations to come for existing and
new customers.
SAP Business Suite powered by HANA - Renovation Strategy
This video gives an update of Business Suite on HANA strat
egy and roadmap.
and Roadmap
SAP HANA Live
SAP HANA Live Overview
This video gives an introduction to SAP HANA Live, SAP's new
operational reporting solution for SAP Business Suite pow
ered by SAP HANA.
SAP HANA Live Hands-On
This video demonstrates the solution in action by showing
views in the SAP HANA Studio, views for the business user,
and views in analysis clients and analytical apps.
SAP HANA Live RDS
This video gives an overview about the SAP HANA Live RDS
Package.
SAP HANA: Migration, Deployment, Optimization
Overview of Migration Options for ABAP-Based SAP Systems
to SAP HANA
Enabling and Optimizing ABAP Coding for SAP HANA
Introduction
This video gives a short overview of migration path options for
SAP ABAP systems to SAP HANA focusing only on on-prem
ise use cases.
This video explains how to enable and optimize existing ABAP
code for SAP HANA.
3
Video
Description
SAP Business Suite powered by SAP HANA –Landscape De
This video gives an overview about what needs to be done to
benefit from all the innovations embedded in the SAP Busi
ness Suite powered by SAP HANA, including UI innovations,
business processes optimizations and simplifications, and the
state of the art dabase SAP HANA.
ployment Options
Why and How to Use Deployment Best Practices for SAP
HANA
This video gives an overview about best practices for deploy
ing SAP HANA.
Database Migration Option of Software Update Manager
Introduction to Database Migration Option (DMO) of Software
Update Manager
Introduction to Database Migration Option (DMO) of Software
Update Manager – UI Demo
This video gives an introduction to the database migration op
tion that is available in Software Update Manager.
This video shows how to use the new DMO user interfaces as
part of Software Update Manager.
ABAP for SAP HANA
ABAP for SAP HANA – What Does It Offer for SAP Partners?
This video is about how SAP partners and customers can ben
efit from ABAP for SAP HANA in particular in the context of
SAP Business Suite powered by SAP HANA.
ABAP for SAP HANA - Advanced Database Programming in
This video gives an outlook on the new SAP HANA related fea
tures of Application Server ABAP 7.4 SP5.
ABAP 7.4 SP5
SAP Solution Manager
How Does Solution Manager Support Solutions Powered by
SAP HANA
Monitoring SAP HANA-Based Solutions with SAP Solution
Manager
This video shows how SAP Solution Manager can be used in
combination with systems based on SAP HANA.
This video shows how to use SAP Solution Manager to moni
tor SAP Business Suite powered by SAP HANA.
Application Lifecycle Manager, more about SAP HANA, SAP UX, Floorplan Manager, SAP Fiori
Application Lifecycle Manager for SAP Business Suite pow
ered by SAP HANA
This video shows how to use SAP Solution Manager for Appli
cation Lifecycle Management of SAP Business Suite powered
by SAP HANA.
SAP HANA Persistence
This video gives an overview about SAP HANA Persistence as
well as data management and log management.
SAP HANA High Availability
This video gives an overview about High Availability in the con
text of business continuity with SAP HANA.
SAP HANA Disaster Recovery
This video gives an overview of disaster recovery with SAP
HANA.
Understand the SAP UX portfolio with SAP UX Explorer
This video shows how you can use UX Explorer to answer your
questions about SAP user experience (UX) and UI technolo
gies.
Floorplan Manager
This video shows how to create attractive user interfaces with
Floorplan Manager (FPM).
SAP Fiori - Architecture & Extensibility Overview
This video provides an introduction to SAP Fiori and SAP Fiori
application types and an overview of the architecture and ex
tensibility concept.
4
Introduction
1.1
Migration vs. Greenfield vs. Sidecar
To work with SAP Business Suite powered by SAP HANA, customers can either migrate to SAP HANA, build up a
new system landscape, or use SAP HANA together with their existing core system.
Migration
Migration refers to the migration of an existing SAP Business Suite system on any DB to SAP Business Suite
powered by SAP HANA. This is normally a project combining the upgrade of the release and the migration of the
database.
This cookbook focuses primarily on migrating from SAP Business Suite on any DB to SAP Business Suite powered
by SAP HANA. It helps to clearly describe the delta between the SAP HANA database and any other database.
The migration process consists of specific tasks, for example downtime minimization and SAP HANA code
compliance.
If you run a Greenfield or Sidecar project, you might find that many of the topics are relevant for you as well
however.
Greenfield
Greenfield denotes the creation of a completely new business system landscape. It is normally a much larger
project.
Sidecar
Sidecar denotes the option of having a dedicated SAP Business Suite powered by SAP HANA system for a
selected business process next to your core SAP Business Suite system.
Introduction
5
1.2
Migration Project Phases
The migration project to SAP Business Suite powered by SAP HANA basically consists of three phases: Plan,
Build, and Run.
Plan
Based on an assessment of your business processes, you identify and validate the business benefits of SAP
Business Suite powered by SAP HANA and build your business case for the migration. Our innovation service
supports you with a tailored recommendation of functional and performance improvements. As part of the
discovery phase, you may also want to start exploring the tangible value of an SAP Business Suite powered by
SAP HANA system through a dedicated system in our SAP HANA Enterprise Cloud (HEC).
During this phase, you prepare the project plan by identifying the relevant activities, resources, and tools. You also
identify the technical prerequisites necessary for a migration and initiate the procurement process for the
required hardware and components. A rich set of tools supports you with the estimation and optimization of the
efforts involved in the system upgrade. To follow compliance rules regarding your data and to optimize your
database size, consider Information Lifecycle Management.
Build
If you chose to run SAP HANA yourself in your own landscape, you can practice the upgrade in a sandbox system.
Note
This step may not be relevant if SAP HANA is run in a hosted and managed environment.
After upgrading your development system, you adjust your custom code to ensure that you fully benefit from the
performance improvements of SAP HANA. To achieve the highest efficiency, you need to find out which code is
really relevant for the migration process. Smart analysis can save you up to 90% of the migration effort. SAP tools
provide you with the necessary functionality to focus on the relevant code objects, and a framework for the overall
change management. SAP can also provide you with services to execute the actual migration process.
After upgrading your quality system, you perform tests. SAP provides you with a new powerful tool set to
automate your tests, thereby increasing their quality and largely reducing manual test efforts for future upgrades.
To keep downtime as short as possible, Database Migration Option (DMO) of the Software Update Manager was
developed to significantly reduce the required downtime, thereby reducing business cost. In future, DMO tools will
be able to keep a downtime near to zero.
6
Introduction
Run
To further improve your system performance, monitor the usage and response times. Using our powerful tool set
you can monitor the system and set the focus of improvements to where most value is added to the business.
Monitor and back up your system.
The following figure illustrates the concept explained above:
1.3
Plan
Executive Summary and Key Takeaways
● Start preparing your SAP Business Suite powered by SAP HANA migration like a standard upgrade and
migration project
Introduction
7
● Specific key value topics: Generic value propositions of SAP HANA and SAP Business Suite powered by SAP
HANA, specific improvements for SAP ERP, SAP CRM, SAP SCM, SAP SRM; and your individual business
process potential
● Specific key technology topics: Sizing and hardware purchasing, system landscape optimization
possibilities, data volume management, add-on compatibility
● Specific key optimization topics: Custom code retirement; SAP HANA code compliance analysis,
prioritization of improvements, upkilling up of resources
1.3.1
Value Discovery
Executive Summary
● SAP Business Suite powered by SAP HANA: SAP ERP, SAP CRM, SAP SRM, SAP SCM are migrated and
optimized to run on the SAP HANA database
● Some of the key benefits: OLTP and OLAP in the same system, improved performance, improved SAP
applications and entirely new SAP applications
● SAP Business Suite powered by SAP HANA is the platform for your business innovation.
● Innovation Service of SAP to help you to identify and prequalify some of the value potential of SAP Business
Suite powered by SAP HANA
● The specific areas providing most benefit are organization specific. Tools give guidance, and you can receive
more information by contacting SAP directly
Overview: SAP Business Suite powered by SAP HANA
SAP Business Suite powered by SAP HANA refers to SAP Business Suite applications running on an SAP HANA
database. SAP ERP, SAP CRM, SAP SCM, and SAP SRM have been migrated and optimized to run on SAP HANA.
For each of these SAP Business Suite components, SAP provides dedicated optimizations and functional
innovations and improvements.
General Concepts and Benefits
● OLAP and OLTP are executed in one system. This increases the potential for innovative applications and
innovative business processes as well as introduces the possibility of consolidating multiple productive SAP
Business Suite systems into one system.
● Improved overall response times for existing transactions and entire business processes through general
performance improvement of the underlying HANA database
● Further improvements through embedded querying and processing capabilities on the database, referred to
as code-pushdown.
● Newly improved end-to-end scenarios that accelerate critical business processes, such as the Material
Requirements Planning (MRP) run in ERP.
● New applications can be used, which was not possible before, such as Predictive Maintenance and Service
8
Introduction
● New user experience, such as SAP Fiori Launchpad applications
● SAP HANA Live as an open foundation for SAP and non-SAP analytical clients
Further, like any existing SAP Business Suite offering, SAP Business Suite powered by SAP HANA provides the
capability to innovate your business through differentiating capabilities - with the addition of real-time reporting
over any data at the best possible performance. All this is provided in a well-known SAP system and tool
environment.
Note
To understand the documentation, consider the following regarding versions of the SAP Business Suite
powered by SAP HANA:
SAP originally released business application versions designed for SAP HANA separately from versions
designed for traditional databases. Specifically, SAP EhP 06 for SAP ERP 6.0, version for HANA; SAP EhP 2 for
CRM 7.0, version for HANA; and EhP 2 for SCM 3.0, version for HANA were designed for SAP HANA.
Subsequently, SAP released SAP Business Suite i2013 - Innovation 2013. This includes new enhancement
packages for the SAP Business Suite core applications (SAP ERP 6.0 EHP7, SAP CRM 7.0 EHP3, SAP SCM 7.0
EHP3, and SAP SRM 7.0 EHP3). These current enhancement packages are compatible with both traditional
certified databases as well as with the SAP HANA database, thus giving more choice to customers to continue
to innovate without disruption. Therefore, the naming distinction version for HANA is not necessary for current
releases. For more information, refer to SAP Business Suite 7 Innovations 2013 - Frequently Asked Questions
Document linked in the information section.
Related Information
SAP Business Suite 7 Innovations 2013 - Frequently Asked Questions Document
1.3.1.1
Value Discovery: Tools, Information, Assessment
To better understand how SAP Business Suite powered by SAP HANA can help your business, SAP provides a set
of tools, services, and documents to help you identify the specific functionality and business processes of SAP
Business Suite powered by SAP HANA that benefit your organization the most.
Self-Service Assets
SAP Solution
Explorer
● Focuses on end-to-end solutions.
● Content includes descriptions of solution capabilities, value maps that depict the most
strategic solutions aligned to your business priorities, and detailed descriptions of solution
capabilities, rapid deployment services available, licensing information, and additional
documentation.
Introduction
9
● Can be limited by industry, line of business, or technology.
● Access SAP Solution Explorer at https://rapid.sap.com/se/
SAP
Innovation
Discovery
.
● Focuses on products and product features to realize your solution.
● Content includes detailed descriptions of new innovations and features along with
implementation guidelines, licensing information, and prerequisites. You can opt to provide
usage data for individualized recommendations.
● Can be limited by industry, line of business, or technology.
● Allows easy viewing of SAP Fiori innovations (focus on new shipments) as well as viewing
innovations by application, delivery channel, or license requirement.
● Provides individualized recommendation and guidance should you opt to provide system
usage data.
● Access Innovation Discovery at https://apps.support.sap.com/innovation-discovery
SAP Business
Suite powered
by SAP HANA
Fact Book
.
● Outlines the innovations and business value in downloadable documents that describe
business practices and innovations to meet your challenges. This may include a list of the
optimized transactions and the SAP Fiori apps that simplify user experience.
● Chapters are focused on industries, line of business, or technology topics.
● Access the fact book at http://www.saphana.com/community/learn/solutions/sapbusiness-suite-on-hana/fact-book .
● Until the fact book contains all scenarios:
○ Access the former SAP Business Suite powered by SAP HANA - 26 Value Scenarios
document.
○ Access the former industry-specific value scenarios in the following table that contains
the links taken from the SAP Business Suite powered by SAP HANA Overview Brochure
.
Table 2: Industry-Specific Value Scenarios
Aerospace and Defense
Higher Education and Research
Oil and Gas
Automotive
High Tech
Professional Services
Banking
Industrial Machinery and Compo
Public Sector
nents
Chemicals
Insurance
Retail
Consumer Products
Life Sciences
Telecommunications
Defense and Security
Media
Transportation and Logistics
Engineering, Construction, and
MiIl Products
Utilities
Mining
Wholesale Distribution
Operations
Healthcare
10
Introduction
Individual Value Assessment
To further quantify the specific value potential for your individual business, we recommend that you contact SAP
for a value assessment for real-time business analysis and execution.
As part of the value assessment, you:
● Quantify the new business potential of a real-time data platform for your business
● Receive first-hand information about the current and future roadmap
● Evaluate the technology features for your specific business and IT requirements with SAP industry experts
● Receive a high-level business case as a decision basis to proceed to the next step
Apart from the above offerings, you can receive assistance with your SAP Business Suite powered by SAP HANA
business case through your SAP Account Executive, or by calling the phone number or using the chat function
provided at http://sap.com/hana .
1.3.1.2
SAP ERP on SAP HANA
SAP ERP has many single transactions and entire processes, such as the MRP run, optimized to benefit from the
power of SAP HANA. Using SAP HANA has accelerated routine and critical processes across SAP Business Suite,
such as the line item browser documents, profitability analysis reports, and intercompany reconciliation. Some
items formerly executed as batch jobs can now be run online.
The following table lists example value scenarios from SAP ERP 6.0 Enhancement Package 7 powered by SAP
HANA. For more information about business value, see Tools and Information for Value Discovery linked in the
information section.
Table 3:
Line of Business
Business Scenario
Enterprise Asset Management
Asset Planning and Scheduling
Finance
Entity Close
Finance
SAP CO-PA Accelerator
Finance
SAP Financial And Controlling Accelerator
Finance
Payables Management
Finance
Receivables Management
Finance
SAP ERP - For Operational Reporting for Finance
Finance
Access Control Role Analytics
Finance
Financial and Managerial Reporting
Finance
Planning, Budgeting and Forecasting
Finance
Profitability and Cost Analysis
Human Resources
HR Shared Services
Human Resources
Payroll Processing
Introduction
11
Line of Business
Business Scenario
Human Resources
Time and Absence Calculation
Human Resources
Transactional Analytics
Manufacturing
Global Plant Performance Management
Manufacturing
Material Requirement Planning
Procurement
Operational Procurement
Research & Development and Engineering
Portfolio Management (PPM)
Project Management (PPM)
Project Management (PS)
Sales, Service, Marketing
SAP ERP - For Operational Reporting for Marketing, Sales, Services
Asset Planning and Scheduling - Services
Supply Chain
SAP ERP - For Operational Reporting for Supply Chain & Procurement
Supply Chain
Demand Driven Supply Chain
Supply Chain
Warehouse Management
For more information, see the information section.
Business All-in-One
SAP has now released 52 country-specificly localized SAP BAiO baseline solutions on the latest SAP HANAenabled enhancement package 7, release of SAP ERP, which is part of the latest SAP Business Suite release. In
addition to this large-scale availability of new country baselines, first industry extensions, such as chemicals and
discrete manufacturing, are also now available with enhancement package 7. SAP continues this work of
delivering quality BAiO packages for our SAP ERP customers.
Related Information
Value Discovery: Tools, Information, Assessment [page 9]
SAP Business Suite powered by SAP HANA - Fact Book
SAP Note 1865866: SAP EHP 7 for SAP ERP 6.0 - Release Information
SAP Note 1820906: EHP7 for SAP ERP 6.0 - Compatible Add-ons
SAP Note 1761546: SAP ERP powered by SAP HANA - Optimizations
Links and Information About Optimization:
Optimizations for SAP Business Suite on HANA
Examples for SAP ERP on SAP HANA Optimization:
Suite Optimization: MM Purchasing - Purchase Order History
Suite Optimization: SD Rebate Processing
12
Introduction
Official Guides and Release Notes for the Current SAP ERP on SAP HANA Release:
http://help.sap.com/erp
1.3.1.3
SAP CRM on SAP HANA
SAP CRM on SAP HANA provides the following key features:
● A real-time view of your customers
● Capability to provide personalized offers based on needs, preferences, past interactions, and current context
● Improved operational efficiency and effectiveness to consistently deliver on promises
● Monitoring and analysis of social media sentiment – and proactive engagement with your customers
● Early discovery of emerging demands
● Improved search performance and flexibility
● OLTP Reporting on SAP HANA for Sales and Marketing
● Native SAP HANA accelerators
The following table lists example value scenarios from SAP CRM powered by SAP HANA. For more information
about business value, see Tools and Information for Value Discovery linked in the info section.
Table 4:
Line of Business
Business Scenario
Finance
Financial Shared Services
Marketing
Sales
Contact Management with Interaction Center
SAP CRM powered by SAP HANA is also part of the SAP 360 Customer solution that combines our market-proven
CRM software with the latest developments in analytics, cloud, enterprise mobility, collaboration, and social
media solutions, and is powered by SAP HANA to deliver real-time customer insight, real-time interactions, and
real-time execution.
Introduction
13
This concept is illustrated in the graphic below:
Case Study on SAP CRM on SAP HANA
SAP migrated its own CRM system to CRM powered by SAP HANA. This topic provides you with an overview of
some of the key results.
● Compressed data stores 60% - from 3 TB to 1.1 TB
● 30% reduction in costs for servers and storage over the previous CRM landscape even though SAP is using
a five-tier landscape rather than the less expensive three-tier landscape
● Gained ability to make better decisions and realign quickly with detailed segmentation of customers
● For lead and activity management, database search performance sped up by a factor of 250
● Increased productivity through:
○ Improved system response times
○ Complex sales reports generated in less than 1 minute versus 45 minutes, and in 30 seconds versus 5
minutes.
○ Transactional search sped up by a factor of 48
○ Service order processing improved by a factor of 4
Related Information
Value Discovery: Tools, Information, Assessment [page 9]
14
Introduction
SAP Note 1877529: SAP EhP 3 for SAP CRM 7.0 with SAP HANA
SAP Note 1820903: EHP3 for SAP CRM 7.0: Compatible Add-ons
Release Notes for SAP EHP3 (Including SP03) for SAP CRM 7.0
Official Guides and Release Notes for Other Releases:
http://help.sap.com/crm
1.3.1.4
SAP SCM on SAP HANA
The following modules of SCM were released as part of SAP Enhancement Pack 02 for SAP SCM 7.0, version for
SAP HANA 1.0:
● Advanced Planning and Optimization (APO)
● Service Parts Planning (SPP)
● Supply Network Collaboration (SNC)
As of SAP SCM 7.0 EhP 3, APO can be deployed in the following manners:
● On an SAP SCM server:
Generally more suitable for larger APO installations as it realizes the full APO functional scope with service
level agreements and sizing independent of ERP.
● As an add-on to SAP ERP:
Generally more suitable for small and midsize businesses as it provides a simplified system landscape and
reduced operational efforts since it shares hardware with the SAP ERP system. When deployed as an add-on,
the APO functionality includes the following main modules:
○ DP (Demand Planning)
○ SNP (Supply Network Planning)
○ PP and DS (Production Planning and Detailed Scheduling)
○ gATP (global Available to Promise)
However, SPP (Service Parts Planning), MSP (Maintenance and Service Planning), and planning with iPPE
(integrated Product and Process Engineering) data are not supported with SAP SCM as an SAP ERP add-on.
Related Information
Innovations and Business Value Scenarios:
SAP Notes:
SAP Note 1737723: EHP 3 for SAP SCM 7.0 SP Stacks – Release & Information Note
SAP Note 1821797: EHP 3 for SAPSCM 7.0: Compatible Add-ons
SAP Note 1825703: Migrating SCM to SAP HANA with integrated SAP HANA liveCache
SAP Note 1835496: Choosing an APO Deployment Option: SCM Server or Add-on?
SAP Note 1879566: APO 7.0 EHP 3 ON ERP 6.0 EHP 6 or EHP 7 regarding restrictions when APO is an ERP addon.
Introduction
15
Also see Related Notes regarding Implementation Recommendations for EHP 3 of specific APO 7.0 functionality.
SAP Note 1840102: SAP APO 7.0 EHP 3: Correction to Online Documentation
Official Guides and Release Notes on SAP SCM Help Portal Page:
http://help.sap.com/scm_703
1.3.1.5
SAP SRM on SAP HANA
SAP SRM on SAP HANA is part of the SAP Business Suite powered by SAP HANA offering. It is available as of SRM
7.0 EHP 3.
It is the base for all future optimization processes and performance improvements along with functional
enhancements.
Benefits:
● Up to 115x improved performance in the creation and display of objects such as RFx and Purchase Order
● Real-time operational reporting and monitoring for better insight into business operations
● Up to 50% decrease in database size because SAP HANA does not require database indices
● Re-vamped Shopping Cart Personalized Object Worklist (POWL) powered by SAP HANA for tremendous
improvement of response time in SP03 with other optimizations of POWL and Sourcing Cockpit planned for
future releases
● Delivery of customer-driven enhancements such as central point for substitution rule maintenance, handling
mandatory fields for free text shopping, and workload redistribution in Sourcing Cockpit application
Related Information
Innovations and business value scenarios in the SAP Business Suite powered by SAP HANA Fact Book
SAP Note 1820905 - EHP3 for SAP SRM 7.0: Compatible Add-ons
Official guides and Release Notes on the SAP SRM Help Portal page:
http://help.sap.com/srm
1.3.1.6
SAP HANA Live
SAP HANA Live is a strategic solution provided by SAP for operational real-time reporting on SAP HANA. It is
currently delivered with more than 2000 virtual data model views for SAP Business Suite applications, and more
content is planned. Business users acquire new ways of building their own reports and documents.
The SAP Business Suite application data models are optimized for data throughput and performance in
transactional scenarios. These data models are optimized for analytic purposes using views in the SAP HANA
database. Delivered reports are implemented quickly and easily and are also responsively designed for
presentation on mobile devices. Data provided by the virtual data model can also be presented through multipurpose analytic UIs, such as SAP BusinessObjects BI Suite UIs, and domain-specific Web applications. Additional
16
Introduction
functionality or data models can be created using the graphical tool or SQL script to reflect your business
requirements.
SAP HANA Live also serves as the foundation for new analytic applications developed specifically for HANA Live,
such as:
● SAP Working Capital Analytics, DSO Scope
● SAP Invoice and Goods Receipt Reconciliation
● SAP Supply Chain Info Center
● SAP Access Control Role Analytics
The technical landscape of SAP HANA Live is illustrated in the graphic below:
SAP HANA Live can be used for CRM Interactive Reporting, which enables SAP CRM users to define and deploy
embedded high-performance reports without additional tools, consultants, or IT support. More than 70 Virtual
Data Models (VDMs) in Sales and Marketing are used in interactive reports. This provides powerful ad-hoc
reporting integrated in the SAP CRM user interface.
Introduction
17
This concept is illustrated in the following figure:
In summary, SAP HANA Live provides the following advantages:
● Open - All access to the reporting framework is based on standard mechanisms such as SQL or MDX. No BW
modeling or ABAP programming are required.
● Uniform - One approach is chosen for all SAP Business Suite applications, enabling a common reporting
approach independent from application boundaries.
● Intuitive - The virtual data model hides the complexity and Customizing dependencies to make data available
without the need for detailed knowledge of SAP Business Suite data models.
● Fast - SAP HANA Live for SAP Business Suite features SAP HANA as the underlying computing engine to
enable fast analytics on high data volumes.
● Real-time - Since all reporting is executed on primary data or a real-time replication of primary data, there is
no need to wait for data warehousing loading jobs to finish. The time frame between recording and reporting
is dramatically reduced.
Note
Despite the benefits of SAP HANA Live, it is important to understand that it is not a substitute for an SAP
Enterprise Data Warehouse or SAP Business Warehouse solution. SAP HANA Live allows end users to build
operational reports, and offers SAP BusinessObjects tools and a third-party framework with which the data in
SAP Business Suite powered by SAP HANA can be accessed. Specific analytic scenarios still require the use of
SAP Business Warehouse however. It is a common approach to use the SAP Enterprise Data Warehouse
system for historical reporting or reporting of old data.
SAP HANA Live is available as a separate package for SAP Business Suite.
Related Information
Information bout SAP HANA Live real-time operation reporting, and a link to a free three-day trial using SAP Cloud
powered by HANA:
SAP HANA Live - Real-Time operational reporting
SAP HANA Live Documentation:
http://help.sap.com/hba
SAP HANA Developer Guide
18
Introduction
Application Examples:
SAP Working Capital Analytics, DSO Scope
SAP Invoice and Goods Receipt Reconciliation
SAP Supply Chain Info Center
Applications in SAP Solutions for GRC
SAP HANA Live Rapid Deployment Solution
SAP Notes
SAP Note 1778607: SAP HANA Live for SAP Business Suite
1.3.1.7
SAP Fiori on SAP HANA
SAP Fiori is a collection of applications that represent the new SAP user experience paradigm.
These applications speak a consistent design language and make use of a common technical infrastructure. By
blurring traditional computing boundaries and by using interactive and attractive UI elements, they provide a
consistent end-to-end user experience and can be used across all device types without creating additional
implementation effort. The SAP Fiori applications focus on the most critical and common activities and are
designed around how people work.
Note
SAP Fiori apps may require an additional license.
Related Information
What is SAP Fiori?
SAP Fiori [page 22]
1.3.1.8
Rapid Deployment Solutions
Overview of SAP Business Suite powered by SAP HANA RDS
Rapid deployment solutions are simple and affordable solutions that respond to customers' business needs and
are ready to consume, offering a jump start of projects and a fast go live, with the possibility to extend the scope
later on.
A rapid deployment solution has three key components:
Introduction
19
Software
The SAP Rapid Deployment Solutions portfolio covers a broad area of SAP software, from the
latest innovations from areas like SAP HANA and UX, to a large portfolio of mature SAP
products.
Best
Practices
Best practices provide a solid foundation for SAP Rapid Deployment solutions and consist of
tested configuration and implementation content, methodologies, and step-by-step approaches
to run specific key processes with minimal installation effort.
Every package has reusable documentation for the project team and end-user training.
Services
The services are predefined and can be delivered by SAP or qualified partners.
While rapid deployment solutions are traditionally available for on-premise deployment, they are now also
available to be deployed in SAP HANA Enterprise Cloud.
The Rapid deployment solutions portfolio for SAP Business Suite powered by SAP HANA includes solutions for
both new and existing customers, as well as two Analytic solutions.
For New Customers
Table 5:
CRM Rapid-Deployment Solution
Brings together software and services to offer essential mar
keting, sales and service functionality.
SAP ERP Foundation Rapid-Deployment Solution
Implement an ERP solution powered by SAP HANA that will
improve your most important business processes like procure
to pay, make to stock, order to cash, or service sales quickly
and affordably.
SAP ERP Foundation Extension: Pre-Assembled Rapid De
The pre-assembled rapid-deployment solution provides the
fastest way to benefit from SAP ERP powered by SAP HANA,
enhanced with real-time operational analytics, UX and more.
ployment Solution
SAP Rapid Data Migration to SAP ERP and CRM on HANA
Cleanses, validates, transforms and migrates data from any
system to SAP ERP and SAP CRM running on SAP HANA, pro
viding high quality legacy data in your SAP solution in only
weeks.
For Existing Customers
Table 6:
Rapid Database Migration of SAP Business Suite to SAP
HANA
Supports the migration of an existing SAP Business Suite in
stallation to the SAP HANA database system without disrup
tion of the existing Business Suite scenarios.
For more information, see the Rapid Database Migration of
SAP Business Suite to SAP HANA video linked in the informa
tion section.
20
Introduction
For Analytics
Table 7:
SAP HANA Live Rapid-Deployment Solution
Enables real-time reporting on operational data from SAP
Business Suite, providing prebuilt reporting content based on
virtual data models.
SAP HANA Analytics for Heterogeneous Data Rapid-Deploy
Consolidates the data from SAP, Oracle, and JDE business
systems for sales and purchasing transactions, leveraging the
SAP HANA Live solution and RapidDecision Data Mart Suite to
source the data into unified data views allowing for a single
point of accesses.
ment Solution
Related Information
Rapid Database Migration of SAP Business Suite to SAP HANA
SCN: SAP HANA Live Rapid Deployment Solution
1.3.1.9
Getting Started Easily
To try SAP HANA and see examples of how it can benefit your organization, you can take a test drive of SAP HANA
using the SAP CO-PA accelerator and see demonstrations of other SAP HANA solutions.
When you are ready to go further, you can explore implementing SAP Business Suite powered by SAP HANA onsite or using SAP HANA Enterprise Cloud. SAP HANA Enterprise Cloud delivers real-time in-memory technology
with Cloud simplicity. It provides the fastest time to value by overcoming the investment cost, complexity, and
skill challenges typical of an on-premise deployment. This gives you the following:
● Comprehensive cloud infrastructure combined with fully-managed services
● Fully scalable, mission critical 24x7 operation with advanced business continuity and support
● Enterprise grade security and sustainability combined with governance, risk, and compliance
Let's Go!
● Test drive HANA and see demonstrations at http://www.saphana.com/community/try
● SAP HANA Enterprise Cloud highlights
● Compare SAP HANA Cloud deployment options:http://www.saphana.com/community/learn/deploymentoptions
● Rapid Deployment Solution for database migration of SAP Business Suite to SAP HANA:
○ At the Service Marketplace: Rapid database migration of SAP Business Suite to SAP HANA
○ In SAP Note 1821999
: Rapid Database Migration of SAP Business Suite to SAP HANA
● Materials and updates: SAP HANA Cloud Platform Developer Center
Introduction
21
To learn more about solutions that harness the power of SAP HANA, contact your SAP Account Executive or
contact us by calling the phone number or using the chat function at http://sap.com/hana .
1.3.2
SAP Fiori
● Fiori apps decompose complex applications into a task-based experience with one central entry point for each
user.
● Fiori apps adapt to all sizes, devices, versions, and channels to provide a common user experience across all
channels.
● Fiori apps follow the 1-1-3 experience (1 user, 1 scenario, 3 screens). They know and provide the right context
and meaningful data integration.
● User experience with apps that speak the same design language. This implies coherence for common
activities as well as coherence for your brand.
● With a low barrier to adoption, enabling customers to adapt and users to personalize.
Keeping Simple Things Simple
The way people work, consume content, and experience technology to get things done is rapidly changing. There
are growing expectations and demands in the workplace for consumer-friendly interfaces. SAP is redefining how
business users perform daily tasks by creating a more intuitive format and user experience – similar to the way
they interact with technology in everyday life.The overall experience of consumer apps is quickly becoming the
new standard for enterprise applications and is rapidly redefining the business experience. Business users want
the same ease of use and convenience with their enterprise software that they experience with their consumer
apps. Addressing the needs of today’s business user, SAP Fiori apps help employees get their job done easily –
anytime, anywhere. This collection of apps provides a simple experience for SAP software functions that are
broadly and frequently used and work seamlessly across any device, including desktop, tablet, and smartphone.
What is SAP Fiori - Improving Productivity and Impacting Business Results
Companies that adopt SAP Fiori report business benefits including increased employee productivity and
satisfaction, reduced work completion time, and better adoption of business processes.
Benefits for the individual user:
● Simple user interface that makes the completion of tasks a pleasant experience
● Access to processes and information – anytime, anywhere, and from virtually any desktop or mobile device –
to get the job done with certainty
● Use of short downtimes to get daily tasks done
Benefits for the overall business:
● Lower travel and procurement costs by reducing delays in process approvals
22
Introduction
● Employees can complete more creative, high-value tasks
● Improved employee morale
Benefits for the IT function:
● Support of a consumer-style user experience desired by employees
● Better use of SAP software investments through easy-to-use common functions available anytime, anywhere,
on any device
● Reduced investment in custom user-experience projects, lowering total cost of ownership and development
of SAP software
What is SAP Fiori - Technical View
SAP Fiori is a collection of apps that represent the new SAP user experience paradigm. These apps speak a
consistent design language and make use of a common technical infrastructure. By blurring traditional
computing boundaries and by using interactive and attractive UI elements, they provide a consistent end-to-end
user experience and can be used across all device types without creating additional implementation effort.
Organized by user role, the SAP Fiori launchpad is the central entry hub to all Fiori apps, where users access apps
via tiles. Within the launchpad are services for navigation, personalization, single sign-on, and search. The
launchpad and the tiles are flexible and can be adapted to your needs. You can use the search in the SAP Fiori
launchpad to search for business objects and for apps. For more information, see SAP Fiori Search .
The Fiori apps focus on the most critical and common activities and are designed around how people work:
● Role-based: Fiori apps decompose complex applications into a task-based experience with one central entry
point for each user.
● Responsive: Fiori apps adapt to all sizes, devices, versions, and channels to provide a common user
experience across all channels.
● Simple: Fiori apps follow the 1-1-3 experience (1 user, 1 scenario, 3 screens). They know and provide the right
context and meaningful data integration.
● Coherent: user experience with apps that speak the same design language. This implies coherence for
common activities as well as coherence for your brand.
● Instant value: with a low barrier to adoption, enabling customers to adapt and users to personalize.
All UIs are built using state-of-the-art technology such as HTML5 and SAP UI5 mobile. Fiori apps allow you to
access the most recent version of your back-end data via OData services. Through previously defined roles and
authorizations you can specify which apps and data a user is allowed to access. In this case SAP Fiori apps
provide a simple, easy-to-use consumer-grade user experience that works seamlessly across devices – desktop,
tablet, or smartphone.
Note
You might need additional licences to run SAP Fiori apps.
For more information about SAP Fiori for SAP Business Suite releases, see the information section.
Related Information
SAP Fiori for Releases prior to SAP Business Suite 7 Innovations 2013
SAP Fiori App List (Prior to SAP Business Suite 7 Innovations 2013)
Introduction
23
SAP Fiori transactional apps for SAP CRM 1.0
SAP Fiori transactional apps for SAP ERP 1.0
SAP Fiori principal apps for SAP ERP 1.0
SAP Fiori principal apps for SAP SRM 1.0
SAP Fiori 1.0 (Based on SAP Fiori Launch Page)
SAP Fiori for SAP Business Suite 7 Innovations 2013
SAP Fiori Apps - Overview
SAP Fiori for SAP ERP 1.0
SAP Fiori principal apps for SAP ERP 1.0
SAP Fiori for SAP SRM 1.0
SAP Fiori principal apps for SAP SRM 1.0
SAP Fiori for SAP CRM 1.0
SAP Fiori for SAP Portfolio and Project Management 1.0
SAP Supply Network Collaboration, User Interface Add-On for Purchase Order Collaboration 1.0
SAP Fiori for SAP Access Control 1.0
SAP Fiori for SAP Customer Engagement Intelligence 1.0
SAP Fiori for SAP ILM 1.0
1.3.2.1
SAP Rapid Deployment Solutions for SAP Fiori
With this service, companies running SAP enterprise software can deploy apps that simplify the user experience
to support business tasks across desktop and mobile devices. Using best practices, service providers install,
configure, and optimize SAP Fiori apps and mobile infrastructure. Quickly and predictably, companies can
improve productivity and reduce total cost of ownership.
Business Needs
● Deliver frequently used software functions across multiple device types with a limited budget
● Provide an intuitive, role-based user experience
● Lower total cost of ownership while improving employee productivity
Delivery Approach
● Use a proven methodology and best practices to plan, deploy, and run proof-of-concept and production
environments
● Conduct a planning workshop, check prerequisite enterprise software, and install and configure SAP Fiori
apps and infrastructure
● Train key users, handle defect resolution, and provide going-live assistance
● Pricing and scheduling depend on the SAP Fiori apps and deployment options that are chosen by the
customer
Value and Benefits
● Increased employee satisfaction with consumer-quality experience
● More productive use of SAP software investments
● Complete environment to run apps with existing SAP software systems
● Rapid time to value with proven setup processes, preconfigured software functionality, and enablement tools
24
Introduction
Related Information
SAP Rapid Deployment Solutions for SAP Fiori
1.3.2.2
More Information
Further Reading Material and Links
● SAP Fiori - Keeping Simple Things Simple
● SAP Fiori Help Center
● SAP Fiori for SAP Business Suite 7 Innovations 2013
● SAP Fiori for Releases prior to SAP Business Suite 7 Innovations 2013
● SAP HANA Innovations for SAP Business Suite
● SAP Fiori Client
● App Types (Transactional Apps, Fact sheets, Analytical Apps)
● Catalog of SAP Fiori Apps
● Manager Apps
, Employee Apps
, Sales Rep Apps
, and Purchasing Agent Apps
● SAP Fiori - SAP User Experience Community
● SAP Fiori on SAP Store
● SAP Fiori on HANA Marketplace
● SAP Fiori Information on PartnerEdge
● Extensibility of SAP Fiori Apps
● SAP Fiori Toolkit
● Experience Fiori Now with Fiori Appliance
● SAP Fiori Simplifies the Enterprise Software Experience
● SAP UX Rapid Deployment Solutions
● SAP Smart Business Cockpits
Lessons-Learned Sessions from SAP
● Generic troubleshooting steps
● System admin should know how to generate stack xml in SolMan
● Double check the add-on components name and the target server
● Apply all SAP Notes before implementation
Introduction
25
● Make sure the backend applications are running before implementation
● Common mistake for setting trusted RFC
● Define system alias for the TASKPROCESSING service
● Common mistake for Launch Page setting
● Adding tiles to Launch Page
● Check the latest support package level
● SAP UI5 add on SP05 Issue with the Fiori Launchpage
● Consultants should know about OData troubleshooting
● Consultants should know about SAPUI5 troubleshooting
● Installing Process Gateway IW_PGW on NetWeaver 7.40
● UI Theme Designer Troubleshooting
● Approve/Reject comment handling
Videos
● Introducing SAP Fiori
● SAP Fiori Simplifies User Experience of Enterprise Apps
● Experience SAP Fiori
● SAP Smart Business cockpits video
● SAP Fiori Demo Video
● Colgate Customer Testimonial Video
● Valero Customer Testimonial Video
● PPC Cement
, Customer Video
● Demo Video - SAP Fiori - For Managers
● Demo Video - SAP Fiori - For Employees
● SAPPHIRE Presentation with Holger Fritzinger and Claudia Barrera from Colgate: Explore the SAP Mobile
Apps Portfolio and Strategy
● Overview Video with Nick Brown
● Demo Video with Scott Steadman
● SAP Fiori - German video
1.3.3
System Prerequisites
To migrate your system to SAP Business Suite powered by SAP HANA, your system must meet certain
prerequisites, minimum releases for example.
● Be aware of benefits provided by SAP Business Suite - Innovation 2013 that help you to continue to innovate
without disruption
26
Introduction
● Be aware of the minimum releases of your SAP ERP, SAP CRM, SAP SCM, and SAP SRM for SAP Business
Suite powered by HANA
● Check the release notes for all enhancement packages for details of current restrictions and release
restrictions
● Be aware of the optimizations available with SAP Business Suite powered by SAP HANA
● Know about the impact on third-party solutions and add-ons
For all relevant information about the system prerequisites, see Prerequisites linked in the information section.
Related Information
Prerequisites [page 76]
1.3.4
Technical Landscape Planning
Technical Landscape Planning involves a variety of activities, such as sizing, deployment and installation options,
data volume management, architecture options, and target landscapes.
● Technical System Landscape Design provides guidance on the appropriate IT infrastructure for SAP HANA,
based on your requirements
● Migration to SAP HANA only involves the switch to another database. Everything else in your landscape will
stay the same
● HANA Sizing provides guidelines for a hardware-efficient approach
● Multi-SID HANA installation can provide TCO benefits and greater flexibility of system operations
● DEV and QAS systems can be combined with the MCOS scenario in a single hardware in a multi-tiered
landscape
Migration Impact on Landscape
Switching to SAP HANA does not break the connectivity to other systems, such as third-party systems and
central hubs like Portal or PI, or cross-application connections such as CIF and ALE.
From a technical point of view, migration to SAP HANA is just a switch to another database. Most other things in
your landscape stay as they are.
A SAP Business Suite system running on SAP HANA can still connect to and be integrated with other systems and
hubs in the same way as a SAP Business Suite system running on any other database.
You can still use the same front ends and clients to connect to your system. Even the application servers can be
reused as they are, provided they are running on separate servers and not on the database host.
Introduction
27
What will change is the kind of database currently running. SAP HANA has a few operational specifics, for example
that it runs on SUSE Linux Enterprise.
28
Introduction
1.3.4.1
Technical System Landscape Design
To design the technical system landscape for SAP HANA, follow the steps described in this topic.
Introduction
29
Context
30
Introduction
To develop and implement the future technical architecture for SAP systems with SAP HANA, proceed as follows:
Procedure
1. Define the deployment options either in the data center (on-premise) or using a hosted (cloud) solution.
2. Define the hardware (HW) acquisition requirements either by using Appliance or by following the Tailored
Data center integration approach. For Appliance, check partner solutions with customer-specific data center
requirements.
3. Define the general technical architecture, i.e. the components required and the sizing for all applications. Map
the sizing results to your hardware using either single-node or scale-out HANA appliances.
Bear in mind the SAP HANA architecture, for instance the usage of Master Node.
4. Consider implementing a data volume management strategy if the required DB size is very large. If you
cannot reduce your uncompressed data below 4 TB, consider implementing the scale-out approach.
5. Decide on the required number of SAP systems to manage software changes (number of systems in a
landscape).
6. Deploy different components, MCOD, MCOS, and virtualization options for setting up each system
7. Define a strategy for high availability and disaster recovery.
8. Define a software change management landscape.
1.3.4.2
System Sizing
Due to the appliance character of SAP HANA, sizing is easier and at the same time more complicated. It is easier
because the choice of hardware configurations are limited at the moment, and SAP offers tools and procedures
that help to determine the required hardware for exact requirements. Sizing is more challenging because of data
growth and thus careful planning and aggressive housekeeping have a much higher impact on cost of ownership
than with traditional RDBMSs.
Sizing Principles
The most important sizing driver is the memory, and the second most important is the CPU requirement. I/O
sizing is also extremely important, but can only be performed during the realization phase. There is also a disk
space requirement for persistence and log data, but this sizing is completely dependent on memory and thus
fairly straight forward.
● Memory (most important sizing driver)
○ Memory sizing is determined by the data footprint in SAP HANA (business and metadata in column and
row stores)
○ Memory is also used by other components, for example SAP HANA caches and the operating system
● CPU
○ To forecast the DB CPU requirement is challenging. This is true for both SAP HANA and AnyDB
Introduction
31
○ CPU usage is different for SAP HANA than AnyDB
● Disk
○ Disk is required for data persistence and for logging data
○ Sizing formula is independent of whether the system is an OLAP or OLTP system
Sizing for New Installations of SAP Business Suite powered by SAP HANA
● Use Quick Sizer for initial sizing and apply the rules in SAP Note 1793345
finding a sizing for SAP Business Suite on SAP HANA
: Sizing for Suite on HANA for
● To perform a throughput-based sizing in Quick Sizer with realistic retention times for the business data, use
Quick Sizer (Online): https://service.sap.com/quicksizer
Table 8:
Result in Quick Sizer
Sizing Suite on HANA
Calculation Factors
Estimated database size
Input for HANA memory
(DB size / compression factor)
* temporary memory usage
Compression factor: 4
Temporary memory usage: 2
Estimated CPU requirements for the
DB server
Input for HANA CPU
DB SAPS * 4
Estimated database size
Input for HANA Disk Space
DB size / 2
Estimated CPU requirements for the
App server
Can be used 1:1
-
Estimated memory requirements for
the App server
Can be used 1:1
-
Sizing for SAP Business Suite powered by SAP HANA Migrations
Space Needed when Migrating to SAP Business Suite powered by SAP HANA
In general you can expect a compression factor (size on current system / size on SAP HANA) of ~4 based on the
early pilot customer results, although this can of course vary in every case.
● Use Current Customer System Size for Application server
● Apply SAP Note 1872170
in source system.
This SAP Note implements a report to estimate the memory space requirement for the database tables of
SAP Business Suite poweredy by SAP HANA systems. The program runs on non-HANA systems.The report
output is only an estimation of the memory requirement of SAP HANA. SAP makes no waranties with respect
to the accuracy of the report result. The customer is responsible for verifying any output and deciding on
whether to implement any of the recommendations made by the report.
○ Analyzes all (or selected) tables on the source system and estimates their size on SAP HANA
○ Uses data sampling
32
Introduction
○ Considers distribution of tables to row and column store
○ Considers de-clustering and de-pooling
○ Considers differences for secondary indexes
○ Database statistics must be up-to-date to have a reliable sizing result
What Is Changing Compared to SAP Business Suite on AnyDB?
SAP HANA DB differs in few sizing principles compared to normal RDBMS.
● DB (HANA) Main Memory Requirements
● DB (HANA) CPU Requirements
● Disk Space Requirements
The application server memory and the application server CPU remain unchanged.
Related Information
Sizing for SAP Business Suite powered by SAP HANA
Hardware Sizing (Quick Sizer)
SAP Notes:
SAP Note 1793345: Sizing for SAP Suite on HANA
SAP Note 1872170: Suite on HANA memory sizing
SAP Note 1698281: Assess the memory consumption of an SAP HANA system
SAP Note 11723135: Resource requirements for SAP ERP Central Component 6.0 EHP6
1.3.4.3
SAP HANA Deployment Options
The SAP HANA appliance software is delivered together with the corresponding hardware and can be deployed in
the data center in different ways.
SAP HANA can be deployed in several ways in the data center (on-premise):
● SAP HANA appliance - Bare metal single server as preconfigured validated stack
● SAP HANA and SAP NetWeaver AS ABAP on one server
● Scale-Out / HA & DR cluster as scalable from single node to geocluster
● Virtualized with VMware with VMware vSphere 5.1 or newer
SAP HANA in the Cloud
● SAP HANA One / HANA One Premium
● SAP HANA Enterprise Cloud
Introduction
33
SAP HANA Appliance (Single Server as Preconfigured and Validated Stack)
The SAP hardware partners deliver the SAP HANA appliance software together with the corresponding, validated
hardware as a prepackaged solution to the customer site. The exact bill of material for hardware components, the
operating system, additional software components, such as a file system, and the SAP HANA software itself is
provided by the hardware partners.
The SAP HANA product availability matrix provides more information about the validated hardware platforms for
an SAP HANA appliance:
● Search for HANA at https://service.sap.com/pam
● SAP HANA Enterprise 1.0 SAP HANA Platform 1.0 Product Availability Matrix
SAP HANA and SAP NetWeaver AS ABAP Deployed on One Server
SAP HANA and SAP NetWeaver AS ABAP deployed on one server is a multi-component and resource-optimized
deployment approach.
The following figure illustrates the benefits of deploying SAP HANA and SAP NetWeaver AS ABAP on one instead
of separate servers:
Availability
As of now SAP HANA and SAP NetWeaver AS ABAP on one server is generally available for all productive and
non-productive SAP HANA SPS07 single-node installations. All products based on SAP NetWeaver AS ABAP 7.4
are supported.
Requirements
● Additive sizing - Additional memory resources for the SAP NetWeaver AS ABAP system need to be available
on the SAP HANA server. For more information on memory sizing, see section System Sizing [page 31].
● Separate SIDs for both systems are required.
34
Introduction
More Information on SAP HANA Virtualization
● SAP Note 1953429
: SAP HANA and SAP NetWeaver AS ABAP on one Server
SAP HANA Scalability
Scales from very small servers to very large clusters. This concept is illustrated in the following figure:
Related Information
Overview - SAP HANA tailored data center integration
FAQ - SAP HANA tailored data center integration
SAP Notes:
1781986: Business Suite on SAP HANA Scale Out
1788665: SAP HANA running on VMware vSphere VMs
Introduction
35
1.3.4.3.1
Scaling SAP HANA
SAP Business Suite powered by SAP HANA can be scaled either vertically or horizontally.
There are two approaches for scaling an SAP Business Suite powered by SAP HANA system:
● Scaling vertically (scale up)
● Scaling horizontally (scale out)
Scale Up
This approach means that you increase the size of one physical machine by increasing the amount of the random
access memory (RAM) available for processing. Restrictions to this approach are due in part to the architectural
limitations of the current CPU generation. They are also due to hardware sizing being defined through the RAM to
processor core ratio, in currently released use cases, and current hardware platforms only allowing a maximum
number of CPUs or cores.
Scale Out
This approach means that you combine multiple independent computers into one system. Distributing a system
across multiple hosts allows you to overcome the hardware limitations of a single physical server. This means that
an SAP HANA system can distribute the load between multiple servers. This scenario is especially relevant if you
have special scalability requirements and very large database sizes. In a distributed system, each index server is
assigned to its own host to allow maximum performance. You can assign different tables to different hosts
(partitioning the database) and you can also split a single table between hosts, known as partitioning of tables.
36
Introduction
The concepts of vertically and horizontally scaling, and the difference between the two scaling approaches are
illustrated in the following figure:
The main goals of a scale-out concept for SAP Business Suite on SAP HANA are to allow for SAP Business Suite
powered by SAP HANA installations with more memory with stable response times and overcome 4 TB (12 TB
next year based on Intel’s new Ivy-bridge architecture) single-node scale-up restriction.
Prerequisites for scale-out installations in the context of SAP Business Suite powered by SAP HANA are as
follows:
● SAP Business Suite powered by SAP HANA Innovations 2013 (ERP EHP 7 SP01, SCM EHP 3 SP01, CRM EHP 3
SP01, SRM EHP3 SP01)
● SAP HANA SPS06 (required to include the relevant landscape reorganization enhancements)
● SAP NetWeaver 7.4 SPS03 (required to include the relevant migration tools)
● Approval for the scale-out on SAP HANA option for SAP Business Suite Innovations 2013 (via pilot note: SAP
Note 1781986 )
Related Information
SAP Notes:
SAP Note 1950470: Hardware Prerequisites for Business Suite on SAP HANA Scale Out
SAP Note 1781986: Business Suite on SAP HANA Scale Out
Introduction
37
SAP Note 1774566: SAP Business Suite - Restrictions
SAP Note 1885758: Landscape Reorg for Business Suite on SAP HANA Scale Out
SAP Note 1825774: SAP Business Suite Powered by SAP HANA - Multi-Node Support
1.3.4.3.2
SAP HANA Virtualization
Current virtualization solutions supported by SAP for running SAP HANA virtualized are:
● VMware vSphere 5.1 and SAP HANA SPS 05 (or later releases) for non-production use cases
● VMware vSphere 5.5 and SAP HANA SPS 07 (or later releases) for single-VM production and non-production
use cases
SAP extends support for SAP HANA on VMware to include general availability of SAP HANA SP07 (and later
releases) on VMware vSphere 5.5 in production, providing all the following conditions have been met:
● A single SAP HANA virtual machine on a dedicated SAP HANA certified server is supported. SAP HANA multinode / scale-out deployment configurations are not supported.
● Multiple SAP HANA virtual machines on a single physical server are generally not supported.
● The maximum size of a virtual SAP HANA instance is limited by the maximum size of a virtual machine on
VMware vSphere 5.5 release, which is 64 vCPUs and 1 TB of memory.
● Each SAP HANA instance / virtual machine is sized according to the existing SAP HANA sizing guidelines and
VMware recommendations.
Caution
CPU and Memory overcommitting must not be used.
● Only single-node, scale-up configurations based on 2 or 4-socket SAP HANA certified Intel E7 Westmere EX
processor or Intel E7 v2 Ivy Bridge EX processor are supported.
● 8-socket SAP HANA certified hardware configurations are not supported.
● Both SAP HANA appliance and SAP HANA Tailored Datacenter Integration (TDI) delivery methods are
supported for SAP HANA on VMware vSphere.
● VMware vMotion, VMware Distributed Resource Scheduled (DRS), as well as VMware HA capabilities can be
used to achieve operational performance and availability between two or more SAP HANA single-node VMs.
● Configuration and overall setup complies with current version of the SAP HANA Guidelines for being
virtualized with VMware vSphere and VMware Best Practices for SAP HANA virtualized with VMware vSphere.
For SAP HANA on VMware in non-production scenarios, the following exceptions to the conditions above
apply:
● Besides 2-socket and 4-socket, also 8-socket single-node SAP HANA appliances or SAP HANA TDI, verified
hardware configurations may be used. The Time Stamp Counter (TSC) must be synchronized between all
sockets or cores.
● Multiple virtual machines may be deployed on a single SAP HANA server. Each SAP HANA database instance
is to be sized the same as SAP HANA deployed on bare metal.
● Only single node configurations, no HANA DB clusters
● No overcommit of CPU and memory
● Same core-to-memory ratio applies as for bare-metal (e.g. 40 vCPUs with 512 GB memory, hyper threading
enabled)
38
Introduction
Related Information
SAP Note 1995460: Single SAP HANA VM on VMware vSphere in production
SAP Note 2024433: Multiple SAP HANA VMs on VMware vSphere in production (controlled availability)
SAP Note 1788665: SAP HANA running on VMware vSphere VMs
SAP HANA virtualized - Overview
1.3.4.3.3
Tailored Data Center Integration
In addition to SAP HANA as a standardized and highly optimized appliance, SAP now offers the opportunity to run
the SAP HANA server with a customer’s preferred storage solution.
Running the SAP HANA server with a customer’s preferred storage solution enables a reduction in hardware and
operational costs at installed-base customers through the reuse of existing hardware components and
operational processes. This approach not only helps to mitigate risk and optimize time-to-value by enabling
existing IT management processes for SAP HANA implementations, it also affords additional flexibility in
hardware vendor selection by leveraging the existing ecosystem. IT departments benefit from staying within IT
budgets, shorter implementation cycles, and better consumption of hardware innovations to drive the SAP HANA
adoption.
Motivation to Introduce SAP HANA Tailored Data Center Integration
Many SAP HANA customers have investments in shared storage architecture and because the in-memory
architecture of SAP HANA does not require tier 1 storage, SAP wants to allow customers to take advantage of
Introduction
39
their existing investments in skills and technology to make the transition to in-memory computing with SAP HANA
easier and more cost-efficient.
Prerequisites for Enterprise Storage
Server
Only servers listed in the SAP HANA Product Availability Matrix
are supported.
Configuration adjustments like:
● No local disks, no flash cards required
● Additional FibreChannel adapters for SAN boot are allowed
Storage
All storages successfully passed the SAP HANA hardware certification.
● Blog SAP Certified Enterprise Storage Hardware for SAP HANA
partners
SAP HANA
Installation
contains a list of
Needs a certified expert (internal or external) to be executed
Related Information
Overview - SAP HANA tailored data center integration
FAQ - SAP HANA tailored data center integration
IBM System Storage Architecture and Configuration Guide for SAP HANA TDI
VMAX Configuration Recommendations for SAP HANA TDI White Paper
1.3.4.3.4
SAP HANA in Cloud - SAP HANA Enterprise Cloud
Introduction SAP HANA Enterprise Cloud
SAP HANA Enterprise Cloud (HEC) is a private cloud solution provided by SAP and based on SAP HANA
technology. Private means that every customer receives an isolated system landscape. The landscape consists of
several Virtual Machines (VM) and physical SAP HANA systems. The administrative tasks are done over HECspecific management networks and administrative infrastructure by SAP administrators. HEC is fully isolated
from SAP Corporate Network. The HEC administrative tool can be access only thorugh two-factor authentication.
40
Introduction
Actual HEC Architecture
A customer system landscape consists of physical servers running HDB and several virtual machines. For
example, SAP Application Server can be set on such a virtualized environment. The HEC customer landscape is
completely integrated into the customer corporate network using IPSEC VPN and/or MPLS connections. The
concept of an HEC system landscape is shown in the following illustration:
Related Information
SAP HANA Enterprise Cloud
SAP HANA Cloud Platform Overview Presentation
SAP HANA Offerings in the Cloud
Business FAQs - SAP HANA Cloud Platform
Introduction
41
1.3.4.4
SAP HANA Installation Options
● MCOS HANA installation can bring TCO benefits and greater flexibility in the handling of your systems
● MCOD scenario can be used for cross-application reporting
● No need for additional ABAP system for add-on installation thanks to technical co-deployment
● Operational effort is reduced thanks to multiple SAP HANA installations
Installation Options
In addition to the standard installation option where one application runs on one SAP HANA instance, which in
turn exclusively runs on one server, there are other installation options like MCOD, MCOS, and Technical CoDeployment available for SAP Business Suite powered by SAP HANA systems.
With MCOD, you can deploy certain white-listed applications together on the same SAP HANA database but in
different schemas. This option allows you to perform common cross-schema reporting on the data of these
applications. SAP Business Suite components like SAP SCM or SAP SRM can be co-deployed with SAP ERP on
one SAP HANA database inside one database schema with SAP HANA Technical Co-Deployment. For nonproduction systems like development and test systems you have the option of installing multiple SAP HANA
databases on the same server with the MCOS scenario.
42
Introduction
The concept explained above is illustrated in the following figure:
Related Information
Landscape Recommendations
SAP Notes:
SAP Note 1661202: Support for multiple applications on SAP HANA(MCOD)
SAP Note 1681092: Multiple SAP HANA databases on one SAP HANA system(MCOS)
SAP Note 1826100: Multiple applications SAP Business Suite powered by SAP HANA
SAP Note 1849151: SAP NetWeaver 7.4 Java on HANA release information
1.3.4.4.1
Multiple Components One Database (MCOD)
SAP supports deploying and running multiple applications on a single SAP HANA production appliance only for
packaged applications and scenarios listed on the White List scenarios. If a particular packaged application or
scenario is not on the White List, running it on the same SAP HANA instance as any other packaged application or
scenario is not supported.
Introduction
43
Caution
Multiple SAP HANA-based applications running with a single SAP HANA system is also known as Multiple
Components One Database (MCOD) with regard to other SAP applications.
White List
The following applications can run together with other applications on one production SAP HANA system:
● Custom Data Marts
● Custom Applications
● SAP BW powered by SAP HANA
● SAP Application Accelerator (Suite Accelerator)
● SAP HANA Live
● SAP Rapid Marts
● SAP HANA Smart Data Access
● SAP CO-PA Accelerator
● ERP Operational Reporting with SAP HANA
● SAP Finance and Controlling Accelerator, specific scenarios
○ ERP Financial Accounting Accelerator
○ ERP Controlling Accelerator
○ ERP Material Ledger Accelerator
○ ERP Production Cost Analysis
● SAP Cash Forecasting
● SAP Operational Process Intelligence
● SAP Smart Meter Analytics
● SAP Liquidity Risk Management
● SAP Fraud Management
● SAP HANA Financials for Public Sector Rapid-Deployment Solution
● SAP Customer Engagement Intelligence
● SAP Demand Signal Management (DSiM)
● SAP Point-of-Sale Data Management (POS DM)
● SAP Business Planning and Consolidation (BPC)
● SAP Customer Activity Repository (CAR)
● SAP Promotion Management for Retail (PMR)
● SAP BusinessObjects BI Platform: Repository and Audit Database
● SAP NetWeaver AS JAVA components, including for example, Enterprise Portal and BI JAVA
● SAP On Shelf Availability
● SAP Tax Declaration Framework
44
Introduction
MCOD and SAP Business Suite powered by SAP HANA
Note
The following applications or scenarios on the White List for SAP Business Suite powered by SAP HANA are
valid with certain limitations.
SAP Enhancement Package 6 and Enhancement Package 7 for SAP ERP on SAP HANA
1. The following applications can be deployed into the same schema as SAP ERP, supporting native access to
SAP ERP data sources. SLT replication is not required:
○ SAP CO-PA Accelerator
○ SAP ERP Operational Reporting with SAP HANA
○ SAP Finance and Controlling Accelerator: Material Ledger
○ SAP Finance and Controlling Accelerator: Production Cost Planning (CO-PC Accelerator)
○ SAP Application Accelerator (Suite Accelerator)
○ SAP Master Data Governance in case of co-deployment with SAP ERP
2. SAP HANA LIVE (also known as SAP HANA Analytics Foundation) for SAP ERP, which is based on SAP ERP,
can be deployed into the same schema as ERP. SLT replication is not required:
○ SAP Working Capital Analytics, DSO scope
○ SAP Invoice and Goods Receipt Reconciliation
○ SAP Overall Equipment Effectiveness (OEE)
○ SAP HANA Analytics Foundation Browser
3. If you also want to install one of the following applications, it has to be deployed into a different schema from
SAP ERP. Since cross-schema mapping is supported, SLT replication is not required:
○ SAP Assurance and Compliance Software
○ SAP Customer Engagement Intelligence
○ SAP Operational Process Intelligence
○ SAP Customer Activity Repository
○ SAP Tax Declaration Framework for Brazil
SAP Enhancement Package 2 and Enhancement Package 3 for SAP CRM on SAP HANA
1. SAP HANA Live (SAP HANA Analytics Foundation) for SAP CRM, which is based on SAP CRM, can be
deployed into the same schema as SAP CRM. SAP SLT replication is not required. This is also a prerequisite
for the following applications:
2. If you also want to install the following application, you need to deploy it into a different schema from SAP
CRM. Since cross-schema mapping is supported, SLT replication is not required:
○ SAP Customer Engagement Intelligence
SAP Enhancement Package 2 and Enhancement Package 3 for SAP SCM on SAP HANA
1. The following applications can be deployed into the same schema as SAP SCM, supporting native access to
SAP SCM data sources. SLT replication is not required:
○ SAP HANA Live (SAP HANA Analytics Foundation) for SAP SCM
○ SAP Supply Chain Info Center
Introduction
45
2. If also one of the following applications should be installed, it must be deployed into a different schema as
SCM. As cross-schema mapping is supported, SLT replication is not intended:
SAP Enhancement Package 3 for SAP SRM on HANA
1. The following applications can be deployed into the same schema as SAP SRM, supporting native access to
data sources of SAP SRM. SLT replication is not required:
○ SAP HANA LIVE (aka SAP HANA Analytics Foundation) for SAP SRM (as prerequisite for the following...)
2. If also one of the following applications should be installed, it must be deployed into a different schema as
SRM. As cross-schema mapping is supported, SLT replication is not intended:
Regardless of the deployed applications mentioned above, deploy the following applications into a separate
schema:
● SAP Master Data Governance (no co-deployment with SAP ERP)
● Custom Data Marts
● SAP Rapid Marts
1.3.4.4.2
Multiple Components One System (MCOS)
The concept of multiple SAP HANA databases on a single SAP HANA system is also known as Multiple
Components One System (MCOS) with regard to other SAP applications.
SAP does not support running multiple SAP HANA databases (SIDS) on a single production SAP HANA
appliance.
SAP does support running multiple SAP HANA databases on a single non-production single-node SAP HANA
system, such as DEV, QA, test, and production fail-over. While SAP HANA is delivered by the hardware partners
with one DB installed, as of SP5, customers can install additional DBs (SIDS) on one SAP HANA system. The
deployment of additional SIDs is performed using the On-Site Configuration tool. The functionality for deploying
additional SIDs is included in the SAP HANA Lifecycle Manager.
SAP does support multiple SAP HANA databases on a distributed (multi-node) non-production SAP HANA
system. As in the single-node case, while SAP HANA is delivered by the hardware partners with one DB installed,
as of SP6, the functionality for deploying additional SIDs is included in the SAP HANA Lifecycle Manager.
Running multiple SAP HANA databases (SIDs) is supported for all types of non-production SAP HANA
systems.
46
Introduction
1.3.4.4.3
Technical Co-Deployment
With SAP HANA Technical Co-Deployment, the SAP Business Suite components SAP SCM and SAP SRM can be
co-deployed with SAP ERP in one SAP HANA database inside one database schema.
The SAP HANA Technical Co-Deployment option is available for SRM and SCM as an SAP ERP add-on. It supports
the following use case scenarios:
● Production and non-production systems
● Single-node or multi-node (scale-out) – depending on the release for certain SAP applications
● Can be combined with SAP Landscape Virtualization Management or MCOS
Table 9:
Strengths
Weaknesses
●
Simplified application landscape setup and maintenance
●
Middleware is still in use
●
Reduced operation efforts for DB/OS/Backup/Basis
●
Closer enhancement package dependencies
●
Possibility to scale out into separate deployment
●
Not yet available for CRM
●
Reduced TCO also on application level
●
Full potential of co-deployment not yet tapped
1.3.4.5
High Availability and Disaster Recovery
High Availability is a set of techniques, engineering practices, and design principles for business continuity. This is
achieved by eliminating single points of failure and providing the ability to rapidly resume operations after a
system outage with minimal business loss. Fault recovery is the process of recovering and resuming operations
after an outage due to a fault. Disaster recovery deals with recovering operations after an outage due to a
prolonged data center or site failure.
SAP HANA provides a range of solutions to recover from faults and disasters.
How to Ensure Business Continuity
High Availability consists, broadly speaking, of four stages:
1. Planning
2. Prevention and preparation
3. Failure detection and recovery
4. Fix failure and failback
During the planning phase, the business needs are evaluated against the cost and complexity of the different
solutions. Prevention and preparation includes the selection, installation, and configuration of redundant
components, standby systems, and replication. Failure detection involves integration within the existing network,
system monitoring, and the management systems to provide alerts and other indicators. Based on the selected
high-availability solution, recovery from failures may be automatic or manual. Failback is the process of restoring
the redundancy and of replicating after recovery to be prepared for a future failure event.
Introduction
47
Related Information
Central SAP Notes
SAP Note 1743225: HANA: Potential failure of connections with scale out nodes
SAP Note 1780950: Connection problems due to host name resolution
SAP Note 1913302: Connectivity suspend of Appserver during takeover
SAP Note 1755396: Released DT solutions for SAP HANA with disk replication
SAP Note 1732276: High availability limitations of HANA database
SAP Note 1900823: SAP Note - SAP HANA Storage Connector API
Further Reading Material and Links
SAP HANA Platform
SAP HANA - Storage Requirements
SAP HANA in Data Centers - Update session about News with SPS 07
Introduction to High Availability for SAP HANA
SAP HANA - High Availability FAQ
SAP Business Suite powered by SAP HANA - High Availability and Disaster Tolerance
1.3.4.5.1
High Availability Support
SAP HANA offers different kinds of high availability (HA) mechanisms, supporting a broad range of scenarios for
recovery from various faults, from simple software errors through system and hardware crashes up to disasters
that decommission a whole data center.
The figure below illustrates the four basic HA solutions and is followed by an explanation:
48
Introduction
A Recovery Time Objective (RTO) varies from industry to industry and depends on business requirements.
Most SAP customers require an Recovery Point Objective (RPO) of 0, since data loss in a connected system
environment means also restoring other, surrounding systems (for example SAP ERP connected with CRM).
In summary, four basic solutions support a high availability SAP HANA implementation.
● Backup & Recovery: Regular shipping of data backups to a remote location over a network or by couriers can
be a simple and relatively inexpensive way to prepare for a disaster. Depending on the frequency and shipping
method this approach may have an RPO of hours to days.
● Host Auto-Failover: One or more standby hosts are added to an SAP HANA system, usually within the same
data center, and are configured to work in standby mode. The standby host has no access to data and does
not accept requests and queries.
● Storage Replication: The storage itself replicates all data to another location within one or between several
data centers. The technology is hardware vendor-specific and multiple concepts are available on the market.
● System Replication: SAP HANA replicates all data to another location within one or between several data
centers. The technology is independent from hardware vendor concepts and reusable with a changing
infrastructure.
Recovery - Key Performance Indicators
Two commonly used key measures to specify the recovery parameters of a system following an outage are the
Recovery Point Objective (RPO) and the Recovery Time Objective (RTO).
Business critical systems are expected to operate with an RPO of zero data loss if a disaster takes place. To
achieve zero RPO and low RTO, meaning quick availability of a secondary system, data must be replicated
synchronously over longer distances to a secondary location. This synchronization might impact regular system
performance and could require more expensive standby and failover solutions. Impacts are driven by network
latency and additional commits from the database. This is the case regardless of the database software used.
Systems must often meet higher objectives for common errors than for very rare ones, such as disasters.
Recovery is the process of rapidly resuming end-to-end business after an outage.
All of this results in trade-off decisions focusing on the attributes of fault recovery functionality, cost, and solution
complexity. SAP offers complementary design options for DR support between data centers: storage replication
and system replication.
1.3.4.5.2
Disaster Recovery
The SAP HANA database supports high availability solutions for disaster recovery using synchronous disk
mirroring of data and log volumes.
SAP HANA Disaster Recovery - Storage Replication
Cluster for Failover components can observe the productive SAP HANA database and switch to a secondary
landscape using the Storage Connector API. The secondary database landscape starts at the time of the failover.
Introduction
49
The downtime in the case of a failover includes the start time of the database plus the time the system needs to
load the essential column store tables. This solution works with by integrating the Storage Connector API of SAP
in the HA solution of the hardware appliance partners.
This concept is illustrated in the figure below:
The replication is done synchronously or asynchronously depending on the hardware layout and the requirements
of the customer. Synchronously means that an SAP HANA transaction at I/O-level is only completed when the
locally persisted transaction log has been replicated remotely; that is, there is a higher latency than without
replication. This method ensures that the changed and committed blocks are available at the secondary site.
Replicating asynchronously means that the method does not ensure that the blocks are changed at the
secondary site, but on the other hand, it has a better performance.
The performance impact is to be expected for operations that change data as soon as the synchronous mirroring
is activated. The impact strongly depends on a number of external factors, such as distance and the connection
between the data centers. The synchronous writing of the log with the concluding COMMITs is the crucial part
here. If an emergency occurs, the primary data center is no longer available, and a process for the takeover must
be initiated. So far, a lot of customers be preferred to use a manual process here, but an automated process can
also be implemented. This takeover process then officially ends the mirroring, mounts the disks to the alreadyinstalled SAP HANA software and instances, and starts up the secondary database side of the cluster. If the host
names and instance names on both sides of the cluster are identical, no further steps with parameter hdbrename
are necessary.
The solution requires further design decisions, for example in the case of failover, if an SAP HANA server on the
secondary side becomes the active database server, detailed implementation is hardware vendor specific. Due to
its continuous nature, storage replication offers a more attractive Recovery Period Objective (RPO) than backups,
but requires a reliable, high bandwidth, and low latency connection between the primary and the secondary sites.
The secondary system can be used during normal operation for other purposes, such as testing and development
as long as it does not influence the productive primary site in any way, for example by a shared infrastructure. If
the takeover takes place, those systems must be shut down and the storage will be reconfigured for the system
taken over.
50
Introduction
SAP HANA Disaster Recovery - System Replication
Using SAP HANA system replication, all data n the SAP HANA software layer, the database kernel, is transferred
to another site. All secondary system services constantly communicate with their primary counterparts, replicate
and persist data and logs, and load data to memory. In this mode, the secondary system does not accept requests
or queries.
When the secondary system is brought up in live replication mode, each service component establishes a
connection with its counterpart, and requests a snapshot of the data in the primary system. From then on, all
logged changes in the primary system are replicated. Whenever a transaction is persisted in the primary system,
it is also sent to the secondary system and persisted there. A transaction in the primary system is not committed
until the logs are replicated.
This concept is illustrated in the figure below:
During system replication, all data on the software layer is transferred . This concept is already known from the
current SAP database installation. Depending on customer requirements for performance and data safety (RPO),
SAP HANA provides different modes for replication offering control regarding RPO and performance:
● Synchronous: A database transaction is finished only when it is persisted at both sites.
● Synchronous in-memory: A database transaction is finished as soon as it is persisted on the primary site and
the secondary has acknowledged receiving data into memory.
● Asynchronous: A database transaction is finished when it is persisted on the primary site and the network
interface of the primary site has confirmed sending the data successfully.
A complete secondary system that is configured identically to the primary stays on standby until the takeover
takes place. All of the SAP HANA data is preloaded and during a takeover of the secondary node, depending on
the configured mode, only a small amount of data has to be loaded into the memory.
1.3.4.5.3
High Availability Scenarios
Depending on your data center operations, hardware configuration, and software landscape, you can select
between several options for High Availability scenarios for SAP Business Suite powered by SAP HANA.
Business Continuity, which includes Disaster Recovery (DR) and High Availability (HA), has the highest priority for
the strategy of SAP in the context of AP Business Suite powered by SAP HANA. SAP works closely with hardware
Introduction
51
(HW) partners to provide customers a flexible choice etween different, but best-suited HW/software solutions for
DR and HA scenarios. Current capabilities include, for example, single-node failover with multiple standby servers
within one cluster configuration, and storage-based mirroring of SAP HANA system replication across data
centers.
The following examples are possible HA scenarios for SAP Business Suite powered by SAP HANA:
● Host auto-failover with a standby node
● SAP HANA system replication
Host Auto-Failover
Host auto-failover is a local N+m fault recovery solution (m is often 1). One or more standby hosts are added to
an SAP HANA system and configured to work in standby mode.
As long as they are in standby mode, the databases on these hosts do not contain any data and do not accept
requests or queries. When an active (worker) host fails, a standby host automatically takes its place. Since the
standby host can take over operations from any of the primary hosts, it needs access to all of the database
volumes. This can be accomplished by a shared networked storage server using a distributed file system, or with
vendor-specific solutions that use an SAP HANA program interface, the Storage Connector API, to dynamically
detach and attach networked storage when failovers occur, for example by using block storage through Fibe
Channel.
This scenario is illustrated in the graphic below:
52
Introduction
Once repaired, the failed host can be rejoined to the system as the new standby host to re-establish the failure
recovery capability:
SAP HANA System Replication
SAP HANA System Replication is the shadow database solution of SAP with SAP HANA. The technology is similar
to other shadow technologies on the database market. SAP HANA System Replication provides an extremely
short Recovery Time Objective (RTO) and is compatible with all SAP HANA hardware partner solutions. System
replication employs an N+N approach, with a secondary standby SAP HANA system that is identically configured
as the active, primary system. Each service and instance of the primary SAP HANA system communicates pairwise with a counterpart in the secondary system.
The instances in the secondary system operate in live replication mode. In this mode, all secondary system
services constantly communicate with their primary counterparts, replicate and persist data and logs, and load
data to memory. The main difference is that the secondary system does not accept requests or queries.
Introduction
53
The scenario described above is illustrated in the graphic below:
Advantages with System Replication
● Memory is continuously loaded at a secondary site in preparation for the potential takeover and occupies
resources
● Switchover is faster than with storage replication or mirroring (2-5 minutes)
● During the takeover of the secondary site, it is only necessary to roll forward from the latest synchronization
point
● Very short performance ramp (only minutes not hours without preparation)
1.3.4.6
SAP Data Volume Management
SAP Data Volume Management (SAP DVM) is a framework that helps to set up and monitor a Data Volume
Management strategy that defines how to manage and reduce future data growth, and reduces the existing DB
size by following a holistic approach that considers and integrates the following options: data avoidance, data
summarization, data deletion, and data archiving.
54
Introduction
● Data Volume Management helps to reduce your productive data volume.
● Start reducing your data before the migration to reduce migration time, effort, and HW cost.
● DVM is a strategy that includes archiving, for which it may use your existing archiving solution, data deletion,
and summarization.
● SAP provides the DVM work center in SAP Solution Manager.
● Continue using DVM as an ongoing effort to keep your data volume low.
The methodology provided in this framework consists of best practices, tools, and SAP services for all stages of a
DVM strategy, from the initial identification of the challenges to continuous improvement of an existing DVM
strategy.
SAP DVM supports the deployment and operation of a DVM strategy:
● As a proactive measure during the solution implementation
● As a proactive measure during the solution go-live
○ Starting with monitoring and analysis on regular basis
○ Minimizing data volume step-by-step according to demand
● As a reactive measure during the solution operation
○ Setting up monitoring and analysis
○ Minimizing data volume by following DVM methodology object categorization
DVM for SAP Business Suite powered by SAP HANA
The size of tables or complete databases is a key driver of a business downtime for certain maintenance activities
such as system copies, Unicode conversions, migrations to SAP HANA, or release upgrades. It is therefore crucial
to actively control and manage data volumes to reduce the downtime baseline for planned maintenance events.
Additionally, you reduce your investments in the storage and efforts in operations, and achieve an optimal and
stable performance in business transactions with increased data quality.
DVM for SAP Business Suite powered by SAP HANA is essentially DVM for SAP Business Suite. There are two
things that change: With SAP HANA as the database, memory is the driving factor for licensing. This means a
more aggressive housekeeping strategy should be preferred.
SAP HANA differentiates between column store and row store tables. Row store tables are stored only on the
master node of an SAP HANA scale-out solution, so the available space for these tables is restricted by hardware.
The overall data volume of the row store tables affects the time that is needed for a database restart, and the
amount of data should therefore be kept as small as possible.
Related Information
DVM Video Tutorials
DVM Configuration for SAP Solution Manager 7.1
Introduction
55
DVM at SAP Service Market Place:
Application Lifecycle Management Processes
SAP Notes:
SAP Note 1159758: Data Volume Management: Central Preparation Note
SAP Note 1487247: Guided Self Service: Data Volume Management - Prerequisites
1.3.4.6.1
DVM Strategy
The Data Volume Management strategy mitigates risk by early identifying unusual data volume increases and
provides you with expert guidance on how to reduce data growth and data volume. It also helps to reduce Total
Cost of Ownership (TCO) by early monitoring and controlling the development of data volume.
You can use the DVM strategy to manage data volume in the following cases:
● Solution transition
○ SAP HANA migration
Minimization of downtime and migration time
Cost optimization
○ Upgrade, conversion, and system split
Minimization of downtime
● Solution operation (proactive and reactive)
Key Elements of the DVM Strategy
● Legal compliance
○ Legal regulations (country specific, for example tax and product liability)
○ Retention policy, for example retention periods, and compliance management, for example storage
○ Corporate policies
● Organizational readiness to be established
○ Advisory and responsibilities, for example auditors, and data or business process owners
○ Project, project team and role of DVM champion
● Technical readiness
○ Landscape components ready for continuous data analyses and monitoring, for example tool-based
● Implementation concept
○ Guidelines, methods, principles
○ Data governance
○ Solution categorization (shortterm, midterm, longterm)
● Operation concept
○ Operations and monitoring
○ Continuous improvement
56
Introduction
DVM Strategy Platform
The DVM work center in SAP Solution Manager is used as a platform for DVM operations. The DVM work center is
used for data discovery (monitoring) and data profiling (analyzing) of the data volume on a regular basis.
Data discovery and data profiling include the following features:
● Alert notification and management
● Trend analysis for individual systems (allocation statistics, utilization, and time-based distribution analyses)
● Reporting of continuous improvements (KPIs)
● Best Practice documentation
● Calculation of potential savings
● Information about archiving performed in the system landscape
● Visualization of system size and application size, and archiving (DVM planning dashboard)
DVM Strategy Processes (Categorization)
There are four categorization aspects for business objects or data objects:
Size and Volume
● Largest and fastest-growing objects
● Objects used most, objects with oldest data, and unused data (time-based analysis)
Complexity
● Fast and easy implementation of applicable reduction methods by object types (transactional, master data)
○ Housekeeping objects, for example system administration data
○ Technical objects, for example basis and cross-application
○ Business quick-win objects
○ Legally relevant business objects
● Expected saving potential of reduction
Legal Compliance
Business objects or data objects for which data archiving is used can be categorized by legal compliance issues,
for example whether or not they use retention management. This means that,you need to define and use retention
management rules for the objects, such as retention periods as criteria for the destruction of data.
Solution Transition
Solution transition is categorized by process issues such as upgrades, Unicode conversion, and system splits or
system merges to minimize system downtime.
Introduction
57
1.3.4.6.2
SAP DVM Service Portfolio
As a holistic methodology, SAP DVM supports the assessment, implementation, operation, and continuous
improvement (DVM life cycle) of a data management and archiving strategy (DVM strategy).
The purpose of the DVM service portfolio is to provide the following offerings in a way that is adequate for each
DVM lifecycle process:
● Services
● Tools
● Best-Practice guidance
This portfolio is illustrated in the following figure:
Data Volume Management Service Delivery
Continuous Quality Check - Data Volume Management - Information Sheet for Service Delivery
58
Introduction
1.3.4.7
SAP HANA Live Architecture Options
● Side-by-side architectures allow you to leverage SAP HANA Live without disrupting your existing landscape.
● Integrated architectures bring the full power of OLTP and OLAP integration on a single database platform.
● SAP HANA Live integrates OLTP and OLAP storage to avoid redundant data, computational overhead for
aggregates, and so on.
● Virtual Data Models present queries that can be used in custom developments, specific analytics applications,
or with BusinessObjects BI tools.
Side-By-Side Scenario
In this scenario, there are two separate systems where data is replicated by using SAP Landscape Transformation
Replication Server.
Introduction
59
The graphic below illustrates this concept and is followed by an explanation:
In the side-by-side scenario, the database tables that are used by the content packages need to be replicated
from the corresponding SAP Business Suite back-end system to the SAP HANA database. This is done using SAP
Landscape Transformation Replication Server. If you want to execute views from the content packages, the data
from the corresponding tables must be available.
Recommendation
SAP recommends creating all required tables as specified in the SAP Notes corresponding to the content
package and to replicate the data only for tables used in executed analytical scenarios. This ensures that no
unnecessary data is replicated, that no unnecessary SAP Landscape Transformation Replication Server
resources are consumed, and that no unnecessary DB memory is consumed. Data for additional tables can be
replicated subsequently if you want to execute additional scenarios.
60
Introduction
Table 10:
Pros
Cons
●
Transaction system does not require any modification
beyond replication interfaces setup
●
Requires additional infrastructure to host SAP HANA Live
system
●
No disruption to existing operations and processes
●
Requires real-time or near-time replication through SLT
for data to be available in SAP HANA Live
Integrated Scenario
SAP HANA Live shares an SAP HANA appliance with the SAP Business Suite system, whose data is used for SAP
HANA Live.
Recommendation
This scenario is recommended for source systems that run on SAP HANA.
The graphic below illustrates this concept and is followed by an explanation:
Introduction
61
In the integrated scenario, you do not need to create and replicate the database tables, as they are already
available in the SAP HANA database. They are maintained through the data dictionary of the corresponding ABAP
application server. This means that no steps for creating tables and replicating data are relevant in this scenario.
Since the ABAP server creates all tables in one specific database catalog schema (normally <SAPSID>), this
needs to be mapped to the authoring schema of the imported content packages.
Table 11:
Pros
Cons
●
No replication of data required, therefore no latency for
operational reporting
●
Requires an upgrade of the whole transactional system to
SAP HANA as a primary database
●
No investment required for dedicated SAP HANA appli
ance for SAP HANA Live
●
Reporting processes might compete with transactional
operations for system resources
Related Information
Administrator's Guide SAP HANA Live for SAP Business Suite, Support Package Stack 03
Help Portal Pages:
SAP HANA Live for SAP Business Suite 1.0
SAP HANA Live for SAP ERP
SAP HANA Live for EHP4 for SAP ERP
SAP HANA Live for Policy Management
SAP HANA Live for SAP CRM
SAP HANA Live for SAP SCM
SAP HANA Live for SAP solutions for GRC
SAP HANA Live for SAP GTS
SAP HANA Live Browser
SAP HANA Live Authorization Assistant
1.3.4.7.1
OLAP and OLTP Storage
SAP HANA Live provides direct access to analytical views that query and aggregate the existing transactional
information of the system in a comprehensible and consumable way. SAP HANA Live therefore does not store any
aggregated or pre-calculated data. In turn, it performs on-the-fly calculation of the numbers required, based on
real-time transactional data.
SAP HANA Live provides reusable query views. These are designed for direct consumption by an analytical
application, based on HTML5 for example, or a generic analytical tool such as BusinessObjects Business
Intelligence. They are always the top view in a hierarchy of views and are not designed for reuse in other views.
62
Introduction
What this means:
● SAP HANA Live can eliminate operational data stores that cause redundancy and latency
● It allows for decision making based on real-time data reports
● It is built on the premise that all reports should access untransformed data as a source. No business rules are
applied, and transformation takes place after the reports have been executed in the Virtual Data Model
● Aggregates or calculations are not stored, but calculated on the fly at query time
● If you have an integrated landscape scenario, no replication of data is required
1.3.4.7.2
Virtual Data Models
A virtual data model (VDM) is a structured representation of SAP HANA database views used in SAP HANA Live
for SAP Business Suite and follows consistent modeling rules.
A VDM provides direct access to SAP business data by using standard SQL or OData requests. Business data is
exposed through well-defined database views, operating directly on the tables of the SAP Business Suite systems
and transforming them into consistent and easily understandable views. These views can be consumed directly by
rich client UIs, as for example HTML5, SAP BusinessObjects, and Excel, without any additional software layers,
such as an ABAP application system in between (two-tier architecture).
A virtual data model consists of the following types of views:
● Query views are designed for direct consumption by an analytical application, based on HTML5 for example,
or a generic analytical tool such as BusinessObjects tools. They are always the top view in a hierarchy of views
and are not designed for reuse in other views. The virtual data model also includes reuse views however, to
support applications based on the virtual data model.
● Reuse views are the heart of the virtual data model. They expose the business data in a well-structured,
consistent, and comprehensible way, covering all relevant business data in SAP Business Suite systems. They
are designed for reuse by other views and must not be consumed directly by analytical tools.
● Private views encapsulate certain SQL transformations on one or several database tables, or even other
views. They are not classified as reuse views, as they might not carry clear business semantics, but are
intended to be reused in other views. They are comparable to subroutines or private methods in programming
languages. A private view can be based on database. tables, other private views, or on reuse views.
Introduction
63
The graphic below illustrates the VDM concept and is followed by an explanation:
This graphic represents the information flow from SAP components at the bottom, through a Virtual Data Model
process to be made available for consumption through reuse views. These reuse views can in turn be leveraged by
SAP through its own query views, for example for Analytics applications, or by end-users through custom
extensions. The end-users can choose any compatible front-end tool to customize or consume the data provided
by the reuse views.
64
Introduction
1.3.4.8
SAP HANA Target Landscapes
There are three types of target landscape for SAP HANA: the two-tier, the three-tier, and the four-tier landscape.
The Hardware-Efficient Approach (High Availability)
Two identical hardware installations exist for SAP HANA: one for the non-production systems (DEV, QA and for
DR) and one exclusively for the SAP HANA production system. This approach allows for development (DEV),
quality assurance (QA), production (PRD), and disaster recovery (DR) systems. DEV and QA are installed on the
same hardware as DR, meaning that DEV and QAS need to be located in the secondary data center.
It is possible to run a development or a QA instance, or both, of the three-tier installation on this secondary cluster
hardware, simply to use it until the take-over is executed. The take-over then stops these DEV and QA instances
and mounts the production disks to the hosts. An additional set of disks for the DEV and QA instance is required in
this case.
The concept described above is illustrated in the following figure:
1.3.4.8.1
Two-Tier Landscape
If you are working to a very tight hardware budget, you need two dedicated servers: one for productive use and
one for development, and possibly also QA. You can create the QA system as an additional system on the same
Introduction
65
HW as the development system using the SAP HANA On-Site configuration Tool. SAP supports running multiple
SAP HANA databases on a single non-production (MCOS scenario).
System Deployment Possibilities
The minimum landscape setup consists of development (DEV) systems and production (PRD) systems.
To set up PRD systems, you could have a bare metal single-server or Scale-Out systems with an option of SAP
HANA as appliance or tailored data center integration.
DEV and QAS systems can be set up with the MCOS scenario by using single hardware.
66
Introduction
With the SAP HANA On-Site Configuration tool customer-specific configuration, that is not available within factory
installation, can be changed or adapted. The illustrated scenario is normally used for non-productive landscapes:
1.3.4.8.2
Three-Tier Landscape
Having dedicated hardware for each tier ensures stability and availability. This is also a mature environment in
production support mode.
In SAP HANA environments, the quality assurance system (QAS) should reflect the production system (PRD) as
closely as possible and be a full copy of it. This is the prerequisite for realistic volume tests. With the flexibility
provided by having a separate system in each tier, all changes can be created in the development system (DEV),
while all tests can be carried out n QAS before transports are imported o PRD.
The three-tier landscape incurs the lowest costs, but poses quality risks in case of high project activity. Using
multiple clients in DEV only partly mitigates these risks.
Introduction
67
Recommendation
To mitigate risks, a recommended procedure is for all projects to go live at the same release date when projects
for the next release date have ideally not started yet.
The sandbox system can be also added temporarily and be used for prototyping new functionalities or new
releases. There is no transport path between the sandbox system and DEV system.
To set up QAS and PRD, systems you could have a bare metal single-server or Scale-Out systems with an option
of SAP HANA as appliance or tailored data center integration.
To set up a DEV system, you can use the virtualization option with VMware with VMware vSphere.
1.3.4.8.3
Four-Tier Landscape
This landscape is the best practice for solutions with production support and for development projects of medium
scope, even in parallel releases. As it allows for staged testing, using multiple clients in DEV is possible, although
not necessary.
In SAP HANA environments, the preproduction system (PRE) should reflect the status in the production systems
(PRD) as closely as possible and be a full copy of it. This is the prerequisite for realistic volume tests.
All changes are created in DEV. The QAS is used as a testing environment for integration testing and data
conversion testing. This system partially contains the changes from the new release that currently is in
development. The PRE is the environment for the final integration test, once the scope of the release is fixed
(release test), and a regression test and a technical system test have taken place.
The PRE must not be corrupted with new release functionalities or new maintenance packages before the
designated time, ideally as close to go-live as possible, and should be refreshed from PRD on a regular basis, if
possible.
This landscape makes the best possible use of change management for production support and project
development. The development team can do both, product changes and support..
The sandbox system can be also added temporarily and be used for prototyping new functionalities or new
releases. There is no transport path between the sandbox system and DEV.
68
Introduction
To set up PRE and PRD systems, you can use a bare metal single-server or Scale-Out systems with an option of
SAP HANA as appliance or tailored data center integration.
To set up a DEV and QAS system, you can use the virtualization option with VMware with VMware vSphere.
Alternatively, DEV and QAS systems can be set up with the MCOS scenario in single hardware.
1.3.5
Project Planning
This chapter points out particular considerations when planning your migration to SAP Business Suite powered by
SAP HANA.
● Data volume, custom code migration, and testing plans can significantly influence cost and effort or introduce
risks in a Suite on HANA deployment project.
● Tools and accelerators may aid in project planning.
● Services are available to assist your implementation from the planning phase through the run phase of your
project.
● An example high-level project plan for a rapid deployment of SAP ERP on SAP HANA is included.
Phases and Project Timelines
Phases
For more information about the project phases, see Migration Project Phases linked in the information section.
Timelines
Migrating your SAP Business Suite application, such as SAP ERP, to the SAP HANA database, can be quick with a
rapid deployment solution. See the sample schedule below for an overview of the project activities and basic time
periods.
Introduction
69
Note
Keep in mind that the project timeline for your SAP Business Suite on SAP HANA implementation depends on
your specific system and requirements.
Effort, Time, and Risk Influences
● Testing Protocol:
Testing is commonly the largest area of effort in an implementation project. The testing requirements, that is
how well the test scripts are defined prior to testing, whether testing is automated or has to be done manually,
and the general testing and approval requirements and practices of your organization, are key factors that
influence the time required for testing and the number or type of testing periods. For more information, see
Test Management linked in the information section.
● Data Size:
The size of the overall database influences the implementation project in many ways. It impacts initial
hardware costs as well as operational costs, time required for many technical and functional steps, and
impacts user efficiency. For more information, see Data Lifecycle Management linked in the information
section.
70
Introduction
● Pool and Cluster Tables:
The size of these tables influences the time required for converting the tables into transparent tables.
● Level of Customization:
The number of custom objects influences both the SAP ERP enhancement package update and the effort
needed to recognize the full benefit of the SAP HANA database because custom objects need to be evaluated
for code optimization. For more information and detailed guidance, see Custom Code Migration and
Optimization linked in the information section..
● Current System Release and Versions:
The current application release may require an enhancement package upgrade, which may introduce
additional steps including regression testing. There may also be upgrades needed for integrated systems or
add-ons. For more information, see chapter Value Discovery, linked in the information section, and follow the
official guides for installation of the system.
● Add-Ons:
Ensure that any implemented add-ons are certified prior to starting the migration to SAP Business Suite
powered by SAP HANA.
For notes related to add-ons, see chapter Value Discovery.
● Hardware Specifications:
The number of CPUs and the amount of memory are fundamental items affecting the time required for tasks
and the costs of hardware.
● Network Bandwidth:
Bandwidth influences the data transfer rate between systems.
● Hardware Location:
The hardware location and proximity to one another influences the latency of data transfer.
Example
For example, if the target and source systems are co-located, the data transfer is typically faster than in
cases where they are in different locations.
Note
Physical shipment of data may even be required in certain circumstances.
● Project Team Expertise:
The SAP HANA skills and experience of key project team members impact the project schedule and efficiency
of completing many tasks. Also, the general experience of the team related to the specific application that has
to be upgraded or to implementation projects in general is very important.
Related Information
Migration Project Phases [page 6]
Test Management [page 116]
Data Lifecycle Management [page 72]
Custom Code Migration and Optimization [page 72]
Value Discovery [page 8]
Introduction
71
1.3.5.1
Data Lifecycle Management
Prior to an SAP Business Suite powered by SAP HANA implementation is a great time to execute your data
lifecycle management policy. Your policy should outline where and for how long different types of records are
stored. For example, some data can be deleted without archival and most can be deleted after archival for a
certain period.
Understandably, archival or deletion of data from your SAP Business Suite system as the data lifecycle
management policy allows provides you with benefits in many ways. You can reduce capital and operating
hardware costs as well as other operating costs by shrinking the size of your database since you are storing and
moving less data both during the project and during routine operations after go-live. This also equates to less risk
with less downtime during the project and afterwards. You also have less business risks by adhering to your data
retention policy and your users can gain efficiencies with less data that have to be interpreted and managed.
Recommendation
Therefore, it is strongly recommended to perform housekeeping of your system and remove any unnecessary
data from the SAP Business Suite application as part of preparation for your deployment of SAP Business Suite
powered by SAP HANA. To identify large tables in your landscape to review them for potential reduction, you
can use SAP transaction SMIGR_BIG_ROW_STORE_TABS as referenced in SAP Note 1634681 .
You can access the Data Volume Management guided self service at SAP Enterprise Support Academy
Guided Self Services
under
Data Volume Management (DVM) - Service session .
Related Information
SAP Note 1872170: Suite on HANA memory sizing
Best-Practice Document Data Management Guide for SAP Business Suite
1.3.5.2
Custom Code Migration and Optimization
Optimizing standard SAP Business Suite code has resulted in significant performance improvements in many
transactions and processes. Similarly, the custom code in your environment needs to be evaluated to determine
which modifications should be made to maximize the benefit of SAP HANA and the priority of the modifications.
Some custom code may need to be modified to avoid performance degration.
Caution
Custom code migration is an area of risk if sufficient resources with appropriate knowledge are not allocated
for the project.
A best practices and recommendations guide has been published to help you plan and execute the custom ABAP
migration and optimization activities. The guide contains explanations of many tools that assist you during the
optimization process and that include familiar transactions such as STAD, SAT, and ST05, as well as new tools
72
Introduction
such as the SQL Monitor, the enhanced SAP Code Inspector, and the SQL Performance Tuning Worklist. The
guide also provides you with recommendations for using these tools.
To have a more accurate picture as a basis for determining your code optimization activities, you can activate
usage analysis, that is Usage and Procedure Logging (UPL) or SQL Monitor (SQLM), or both, as early as possible
in your productive SAP Business Suite environment. This is the basis to prepare for custom code assessment
even before you start with the SAP Business Suite powered by SAP HANA transition project. For more
information, see Considerations for Custom ABAP Code when Migrating to SAP HANA - Best Practices and
Recommendations linked in the information section.
When planning your code migration and optimization, see the current guidelines for code optimization so that you
are aware of the related tools and educational opportunities. For more information on golden rules, tools, and
other aspects of code modification to fully use SAP HANA, see Code Migration and Optimization linked in the
information section.. If you need assistance in modifying your custom code, several SAP services are available.
Related Information
Code Migration and Optimization [page 96]
Considerations for Custom ABAP Code when Migrating to SAP HANA - Best Practices and Recommendations
1.3.5.3
Downtime Minimization
The migration of existing SAP Business Suite systems to SAP Business Suite powered by SAP HANA involves the
update of the application's enhancement package and the subsequent migration of the database. These activities
can be performed with different approaches to system outages.
Strategy 1: Combined EHP Update and Migration
With Software Update Manager (SUM) 1.0 SP9 or higher, you can combine the update and migration to SAP
HANA for SAP Business Suite systems. Database Migration Option (DMO) minimizes the effort required for
testing, system preparation, and other activities while also minimizing the production downtime. There are certain
prerequisites and requirements. For more information, see SAP Note 1875197 : Conditions: Using DMO of SUM
for Business Suite systems.
Strategy 2: EHP Update and Migration with One Planned Downtime
The update of the SAP Business Suite application and the migration to the SAP HANA database are performed as
two tasks during one outage. This approach minimizes the effort required for some preparatory project steps, for
example the isolation of systems, because they are performed only once. However, the outage is longer than the
individual outages for update and migration.
Introduction
73
Strategy 3: EHP Update and Migration with Two Planned Downtimes
The update of the SAP Business Suite application is performed during one outage and the migration to the SAP
HANA database is performed during a subsequent outage. This approach minimizes the disruption in business
operations because there are two shorter production outages. However, this approach results in additional effort
for preparation or any step that is required for the update and the migration.
Related Information
Suite on HANA Roadmap and Release Information
Follow this link to find the latest releases for SAP Business Suite powered by SAP HANA.
SAP ERP 6.0
1.3.5.4
Planning Resources
Project Planning Guidance
For guidance in planning the technical steps of the migration of your SAP Business Suite powered by SAP HANA
system, see Quick Guide Rapid database migration of SAP Business Suite to SAP HANA.
For broader guidance in planning the overall project, see HANA ASAP 8 Methodology.
Note
Be sure to review the relevant guides before initiating your project to ensure that all appropriate steps are
included. See links to the guides on SAP Business Suite powered by SAP HANA and specific application on SAP
HANA portions of chapter Value Discovery.
SAP Services for SAP HANA
You may also use SAP services for SAP HANA for various steps throughout your project lifecycle, from planning to
go-live. Listed below are some of the available services. However, it is not a complete list. Also, some of the
services are free, some are included as part of different service level agreements, and some are provided by SAP
Field Services. For more information, contact your SAP Account Executive.
Services available for the plan and build phases of your project include:
74
Introduction
● Design Thinking Workshops:
Business and technical stakeholders jointly explore business problems and solutions to find the highest value
from leading edge technology.
● SAP HANA Planning Assessment:
Understand how SAP HANA and in-memory technology fit into your IT environment, and identify the right
business use cases for your SAP HANA implementation.
● Business Process Performance Optimization
● Custom Code Analysis and Optimization:
Optimize your custom code for SAP Business Suite powered by SAP HANA
● Pilot Implementation for SAP HANA:
Ensure a smooth pilot implementation of SAP HANA and determine how it fits into your existing landscape by
using best practices for moving data in-memory.
● Custom Development and Support of Custom Code Management
● Rapid Deployment Solutions for SAP ERP powered by HANA, CRM powered by HANA, SAP HANA Live, Rapid
Database Migration to SAP HANA, and more
● SAP HANA Enterprise Cloud:
With SAP HANA Enterprise Cloud, you get access to a range of services such as rapid onboarding, data
migration, and elastic infrastructure hosting services.
● Unicode Conversion
● Technical Implementation or Upgrade
● Technical Performance Optimization
● Implementation Control Center
SAP HANA Services available for the run phase of your project include:
● SAP Safeguarding:
Portfolio of services that identify factors that pose a risk to your implementation, upgrade or migration
project, as well as to daily operations and provide recommendations on how to manage them.
● SAP MaxAttention:
Highest level of SAP support
● Support for Custom Developed Solutions
● System Administration for SAP HANA
● Application Management
● Go-Live Services
● Operation Control Center:
Helps you prepare and transition smoothly into productive operations
● Education Services
Related Information
Quick Guide Rapid database migration of SAP Business Suite to SAP HANA
HANA ASAP 8 Methodology
Value Discovery [page 8]
SAP HANA Services e-book
In-Memory Computing (SAP HANA) Services
Introduction
75
SAP Rapid Deployment Solutions for SAP Business Suite powered by SAP HANA
SAP Enterprise Support Academy
To access best practices provided as HTML source or integrated into SAP Solution Manager, follow this link. The
Deployment Best Practices for SAP HANA section of this page is part of a new knowledge transfer model provided
by SAP Active Global Support.
1.4
Build
Among other things, this chapter explains how to migrate your system, deploy SAP HANA Live, analyze your
runtime, and test your system's performance. This topic provides you with a brief overview of the chapter.
In the Build chapter, you receive information that helps you to do the following:
● Simplify and speed up your system migration with Database Migration Optimizer (DMO)
● Understand the steps required for the deployment of SAP HANA Live
● Optimize your custom developments by prioritization and runtime analysis with Unit Procedure Logging
(UPL), Code Inspector (CI), and SQL Monitor (SQLM)
● Plan your functional tests and performance tests, and improve your testing efficiency by using test
automation tools such as SAP Component-Based Test Automation (CBTA), SAP Test Acceleration and
Optimization (TAO), or Extended Computer Aided Test Tool (eCATT)
● Understand how SAP services can help you speed up and safeguard your migration project
1.4.1
Prerequisites
Before upgrading SAP Business Suite components, you have to consider certain prerequisites.
● Know the benefits of SAP Business Suite i2013 - Innovation 2013 that helps you continue innovating without
disruption
● Be aware of the minimum releases of the following systems required for SAP Business Suite powered by
HANA:
○ SAP ERP
○ SAP CRM
○ SAP SCM
○ SAP SRM
76
Introduction
● Check the release notes for all enhancement packages for current restrictions and release restrictions
● Be aware of optimizations available with SAP Business Suite powered by SAP HANA
● Know about the impact on third-party solutions and add-ons
Dual-Stack Split
Caution
Dual-stack systems are not supported any longer for the following upgrade targets: EHP7 FOR SAP ERP 6.0,
EHP3 FOR SAP CRM 7.0, EHP3 FOR SAP SCM 7.0, EHP3 FOR SAP SRM 7.0.
SAP HANA does not support dual-stack systems (that is, systems running both AS ABAP and AS JAVA in one
system with one SAP system ID and one startup framework). Before the upgrade, you must split existing dualstacks or remove the AS JAVA. After the split you can migrate the AS ABAP system to SAP HANA.
SAP Business Suite i2013
SAP Business Suite i2013 - Innovation 2013 includes new enhancement packages for all SAP Business Suite core
applications:
● SAP ERP 6.0 EHP7
● SAP CRM 7.0 EHP3
● SAP SCM 7.0 EHP3
● SAP SRM 7.0 EHP3
All of these innovations are available with the traditional certified databases as well as with the SAP HANA
database, thus giving more choice to customers to continue innovating without disruption.
For more information, see SAP Business Suite Innovations 2013 Frequently Asked Questions Document linked in
the information section.
Minimum Releases
SAP Business Suite i2013 is the recommended minimum release for SAP Suite on HANA.
Exception: ERP 6.0 EHP 4 for SAP HANA Live. For more information, see SAP HANA Live - aka SAP HANA
Analytics Foundation.
Direct updates to SAP Business Suite i2013 are possible for the following minimum source releases:
● SAP ERP: R/3 4.6C onwards
● SAP SCM: SCM 4.1 onwards
● SAP CRM: CRM 5.0 onwards
● SAP SRM: SRM 5.0 onwards
Introduction
77
For more information about the minimum DMO release, see Technical System Migration linked in the information
section. If you consider to virtualize a productive system, see our Cloud solutions for Business Suite powered by
SAP HANA instead.
Related Information
What changes, what does not change? After a migration to SAP HANA data base
SAP Help Portal Page: SAP Business Suite powered by SAP HANA
SAP Road Map for Applications Using SAP HANA
Product Road Map Updates
Applications powered by SAP HANA
SAP HANA Live for SAP Business Suite 1.0
What's New in the SAP HANA Platform (Release Notes)
SAP HANA Platform
Dual-Stack Split
SAP NetWeaver Discontinues Dual Stack
Dual-Stack Split
Dual-Stack Split: SAP Notes
SAP Note 1816819: Dual Stack support for Business Suite systems
SAP Note 1797362: Dual-Stack Split for Systems Based on SAP NetWeaver
SAP Business Suite i2013
SAP Business Suite Innovations 2013 Frequently Asked Questions Document
Minimum Releases
SAP HANA Live - aka SAP HANA Analytics Foundation
Technical System Migration [page 82]
1.4.1.1
Latest Release Information
Get information about where to find the latest release information for SAP Business Suite powered by SAP HANA
including SAP ERP, SAP CRM, and SAP SCM.
SAP Business Suite powered by SAP HANA
● SAP Note 1916010
: Limited Version Interoperability for Business Suite 7i2013
● SAP Note 1388258
: Version Interoperability within the SAP Business Suite
● Strategy beyond SAP Business Suite 7 Innovations 2011
78
Introduction
SAP ERP powered by SAP HANA
With SAP ERP 6.0 EHP7, most areas of the existing SAP ERP functions for SAP HANA can use the in-memory
technology and enable business applications to perform better.
Always check the latest information for SAP ERP powered by SAP HANA:
● SAP ERP Help Portal page including release notes: http://help.sap.com/erp_607
● SAP Note 1865866
: SAP EHP 7 for SAP ERP 6.0 - Release Information
Further information for SAP ERP powered by SAP HANA:
● Optimizations for SAP Business Suite on HANA
● SAP Note 1737650
: EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note
● SAP Note 1730102
: Release Restrictions for SAP Netweaver 7.40
● SAP Note 1789659
: Release Restrictions for SAP Netweaver AS ABAP 7.40
● SAP Note 1789659
: Overview Suite on HANA Restrictions
SAP CRM powered by SAP HANA
Always check the latest release information available for SAP CRM powered by SAP HANA:
● SAP CRM Help Portal page: http://help.sap.com/crmhana
● Release Notes for SAP EhP 3 for SAP CRM 7.0
● Release notes for SAP EhP 2 for SAP CRM 7.0,version for SAP HANA
● SAP Note 1768032
restrictions)
: SAP EhP 2 for SAP CRM 7.0, version for SAP HANA (optimization and current
SAP SCM powered by SAP HANA
Always check the latest release information available for SAP SCM powered by SAP HANA:
● SAP SCM Help Portal page: http://help.sap.com/scm_hana
● SAP Enhancement Package 3 for SAP Supply Chain Management 7.0 - Release Notes
● SAP APO 7.0 EHP 3 on SAP ERP 6.0 EHP 6/7 - Release Notes
● For release restrictions regarding to SAP EhP 2 for SAP SCM 7.0,version for SAP HANA, see SAP Note
1768043 .
SAP NetWeaver 7.4 Java on SAP HANA
With SAP NetWeaver 7.4 SP04 the components of the following instances based on Application Server Java are
released for use with SAP HANA Database 1.00:
● Application Server Java
Introduction
79
● NW Product Description
● Adobe Document Services PDF Export Demo Applications
● BPM
● EP Core - Application Portal
● Enterprise Portal
● BI Java
● Advanced Adapter Engine Extnd
● PI Adapter Engine (Java EE)
● Enterprise Services Repository
● Composite App. Framework
● Composition Platform
● Guided Procedures
● AS Java Extensions
● Development Infrastructure
Note
Development Infrastructure is not enabled for MCOD usage. For more information, see SAP Note 1661202
.
Related Information
SAP Note 1849151: SAP NetWeaver 7.4 Java on HANA release information
SAP Note 1747907: HANA Platform is supported by NWD
1.4.1.2
Impact and Advantages
Impact on Add-Ons
The SAP Notes listed in this topic provide you with information about dd-ons for roducts powered by SAP HANA,
including SAP ERP, SAP CRM, SAP SCM, SAP NetWeaver Application Server ABAP, and SAP Suite on HANA.
For more information, see the SAP Notes linked in the information section and subscribe to receive the latest
updates.
80
Introduction
Impact on Third-Party Solutions
In most instances, recertification is required. SAP will provide details in future roadmaps. To find current certified
solutions, see Partner Information Center: Search for Solutions linked in the information section.
Advantages of SAP HANA Optimization
HANA optimizations are delivered through enhancement packages.
For more information about optimizations, see Optimizations for SAP Business Suite on HANA.
Latest SAP HANA Revisions
In addition to SAP HANA releases and specific SAP HANA application releases, such as SAP Business Information
Warehouse on HANA and SAP Business Suite powered by SAP HANA, SAP provides innovations via the HANA
database revisions.
Table 12:
Central SAP Note for HANA
Description
1514967
Access the latest SAP HANA database revision in section Re
lated Notes.
Note
Every revision has its own SAP Note.
Related Information
Impact on Add-Ons
SAP Note 1855666: Suite on HANA: 3rd Party Add-ons
SAP Note 1896062: EHP7 for SP ERP 6.0: Compatibile Partner products
SAP Note 1826531: Add-on compatibility of SAP NetWeaver 7.4 - ABAP
SAP Note 1877529: SAP EhP 3 for SAP CRM 7.0 with SAP HANA
SAP Note 1821797: SAP EhP 3 for SAP SCM 7.0: Compatible Add-on
SAP Note 1820906: EHP7 for SAP ERP 6.0: Compatible Add-ons
SAP Note 1820903: EHP3 for SAP CRM 7.0: Compatible Add-ons
SAP Note 1820905: EHP3 for SAP SRM 7.0: Compatible Add-ons
SAP Note 1855666: Suite on HANA: 3rd Party Add-ons
Impact on Third-Party Solutions - Certified Solutions:
Partner Information Center: Search for Solutions
Advantages of SAP HANA Optimization:
Optimizations for SAP Business Suite on HANA
Introduction
81
1.4.2
Technical System Migration
● Database Migration Option (DMO) combines system upgrade and migration
● Migration steps are simplified and business downtime is reduced
● The source database remains consistent, so a fast fallback is possible
● Database Migration Option has less prerequisites for the existing DB software level
At several stages during the lifecycle of your SAP solution, you are required to copy or migrate your system. SAP
recommends copying your system to create test, demo, and training systems for example. If you need to change
your operating system, database, or both of them, you have to migrate your SAP system.
During a migration process, all data is ported from a source database and imported to a target database. If you
are using SAP Business Suite on HANA, you are required to upgrade your existing system and migrate to HANA.
There are various techniques that can be used to copy and migrate an SAP system:
● Copy an SAP system without changing the operating system or database (homogeneous system copy)
● Copy an SAP System while changing the operating system, database, or both (heterogeneous system copy)
Homogeneous System Copy
The main purpose of a homogeneous system copy is to build a test, demo, or training system, or to move a
system to a new hardware. The difference to a heterogeneous system copy is that both the database and
operating system remain the same. On some platforms, the system can therefore be copied by using databasedependent methods, such as backup or restore.
Note
Regardless of whether you change the version or bit version of either the operating system or the database, the
system copy is still considered to be a homogeneous system copy. The Microsoft Windows 2000 32-bit system
is copied to the Microsoft Windows 2003 x64 system for example.
Heterogeneous System Copy (Migration)
The main purpose of a heterogeneous system copy is to create a copy of an existing SAP system on the platform
where either the operating system, database, or both the operating system and the database, differ from the
operating system, database, or both the operating system and the database, of the source system. The whole
migration process consists of five main steps (described in detail in the system copy documentation):
1. Preparatory steps in the source system
82
Introduction
2. Export of the data of the source system to a database-independent format
3. Transfer of the exported files to the target host
4. New system installation together with data import
5. Post-processing steps in the target system
1.4.2.1
Migration to SAP HANA
For the migration to SAP HANA, several migration path options are available.
● New Installation: Install a new system on SAP HANA without changing your existing system and transform
the existing solution by selective migration.
● The classical migration of ABAP systems to SAP HANA: The heterogeneous system copy by using the
classical migration tools Software Provisioning Manager 1.0 and R3load.
● One step upgrade and migration with Database Migration Option (DMO) of Software Update Manager
(SUM): This is provided with DMO in Software Update Manager and is planned to become the standard
migration option when migrating to SAP HANA.
New Installation
Install a new system based on SAP NetWeaver Application Server ABAP 7.40 in parallel to your existing system
and transform the existing solution by selective migration. The advantage of this approach is that there is no risk
for the production system and you get a clean system without outdated data.
Considerations for New-Installation Approach
● Not suited to replace the current production system
● Requires transfer (transport, migration, and load) of relevant business data
● Additional hardware can be required for the application server
● No real data and performance comparison possible
Introduction
83
Recommendation
For systems with resident transactional, data such as SAP Business Suite, this option is recommended for
testing the overall SAP HANA approach and for gaining first experience, but not for migrating or replacing your
current production system.
Classical Upgrade and Migration to SAP HANA
You can upgrade your existing system and then perform the database migration, such as heterogeneous system
copy by using standard tools, for example, Software Provisioning Manager, SAPinst, R3load, and Migration
Monitor), with the classical migration procedure for databases.
When you migrate a system to SAP HANA with the classical approach, the following steps are required:
● Dual-Stack Split
This applies to any kind of migration whenever a dual-stack sytsem is involved. For more information, see
Prerequisites linked in the information section.
● Upgrade or Update:
If your system has a lower release then upgrade it to the latest product supported by SAP HANA (SAP ECC
6.0 EHP 7). If your SAP Business Suite system already has the right release but an enhancement package not
supported by SAP HANA, apply the required enhancement package (enhancement package 7).
● Heterogeneous System Copy: Database Migration
Perform the heterogeneous system copy as described in the SAP HANA System Copy Guide that is available
in SAP Service Marketplace at http://service.sap.com/sltoolset under
Documentation
System Provisioning
SL Toolset 1.0
System Copy: Systems Based on SAP NetWeaver <Release>
<Platform> . If you have a non-Unicode system, perform a Unicode conversion before the migration or
plan a migration combined with a Unicode conversion.
Recommendation
Only if the standard Database Migration Option (DMO) of Software Update Manager (SUM) does not meet your
requirements (for example, because DMO of SUM is not yet available for your scenario or platform and you
want to perform the migration now, or because you prefer clear separation of tasks to the “big-bang” approach
of DMO), consider using the classical migration with a heterogeneous system copy.
84
Introduction
Related Information
SAP Note 1775293: Migration/system copy to SAP HANA using latest SWPM 1.0
SAP Note 784118: System Copy Tools for ABAP Systems
SAP Note 1783927: Prerequisites for Table Splitting with target HANA database
SAP Note 1680045: Release Note for Software Provisioning Manager 1.0
System Copy and Migration
Prerequisites [page 76]
1.4.2.2
Database Migration Option (DMO)
The Software Update Manager 1.0 (SUM) SP07 or higher is equipped with a new feature: the Database Migration
Option (DMO). With this new feature, you can avoid landscape changes (SID, host name). The SUM tool
combines all relevant steps for -place migration to SAP HANA: Unicode conversion, upgrade, and migration.
Migration Scenario
Migrating an existing SAP system to SAP HANA requires several steps. The advantage of place-migration instead
of a new installation is that the existing system is upgraded, and you are able to retain the existing system ID, host
name, and connectivity, assuming that you run your SAP system on AnyDB. Required steps are dual-stack split,
Unicode is converted, the database of AnyDB is updated, your SAP software is upgraded, and the database is
migrated to SAP HANA.
DMO Processing Overview
The DMO processing steps are based on the shadow system functionality of SUM. As part of the process, SUM
creates the shadow repository on the existing database until the downtime phase while the SAP HANA database is
set up in parallel, for example the client and schema. The connection should be established from the source
system. In subsequent steps, the shadow repository is copied to SAP HANA, the database connection of your SAP
system is migrated to the SAP HANA database, and then the downtime starts. After migrating and converting the
application data, the upgrade is finished, and the new system runs on SAP HANA. The traditional database
continues to run without being modified, and thus remains as a fallback throughout the complete process.
DMO Phases During the Procedure
The main differences to the standard upgrade procedure are following:
● Replacement of the “Switch of shadow tables” step from he standard procedure with the migration steps of
the In-Place Migration Upgrade.
Introduction
85
● Execution of the downtime and post processing steps on the target database in the In-Place Migration
Upgrade.
In-Place Migration Upgrade
86
Introduction
DMO of Software Update Manager for SAP Business Suite systems
Software Update Manager (SUM) has been extended to combine system update and migration to SAP HANA.
With SUM 1.0 SP10, for non-Unicode source systems, the DMO procedure includes the Unicode Conversion (for
single code page systems).
System Prerequisites for DMO Migration
● Dual-Stack split - DMO works only with ABAP systems, so a dual-stack split may be required beforehand.
● OS/DB: according to PAM with restriction - i5 not yet supported ("DB2 for IBM i" / "DB2 for IBM iSeries" /
"DB2 for IBM i5/OS")
● Source release:
○ SAP ERP 6.0 or higher (e.g. EHP1, EHP2, EHP3)
○ Systems as part of SAP Business Suite 7 or higher (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SCM 7.0, SAP
SRM 7.0)
○ SAP SCM 7.0 is supported, but you have to manually migrate the live cache after migration as described
in SAP Note 1825703
○ Systems based on SAP NetWeaver 7.0 (e.g. SAP ERP 6.0) need at least SP17 for software component
SAP_BASIS
● Target release: System based on SAP NetWeaver 7.4 and higher
Introduction
87
DMO Path for SAP Business Suite Systems
Related Information
Central SAP Notes
SAP Note 1813548: Database migration option (DMO) for Software Update Manager
88
Introduction
SAP Note 1875197: Conditions: Using DMO of SUM for Business Suite systems
SAP Note 1031096: Installing Package SAPHOSTAGENT
SAP Note 1732061: Central Note - Software Update Manager 1.0 SP07 [lmt_008]
Further Reading Material
Migration Options for SAP Business Suite to SAP HANA database
Upgrade and Migration to SAP Business Suite powered by HANA
Strategy beyond SAP Business Suite 7 Innovations 2011
Decision Matrix to Choose Best Migration Option of ABAP Systems to SAP HANA
DMO: technical background
Database Migration Option (DMO) of SUM - Introduction
Latest info of DMO at Service Market Place
Go to http://service.sap.com/sltoolset:
(SUM)
1.4.3
Software Logistics Toolset 1.0
Software Update Manager
.
SAP HANA Live Deployment
Read this topic for a brief overview of SAP HANA Live.
SAP HANA Live is an additional technical component that allows ou to run additional (external) reports on your
data. The Virtual Data Model (VDM) serves as an open, generic representation of your business data, for
consumption with any external tool. SAP HANA Live is installed on the SAP HANA Appliance.
The following sections provide you with information on:
● The installation steps required for your system landscape
● The various consumption options and related products
Installation High-Level Steps
The installation of SAP HANA Live consists of the following steps:
1. Make sure that you meet all prerequisites. For more information, see the SAP Help Portal page SAP HANA
Platform.
2. Activate the schema, and create tables in SAP HANA.
3. Import Virtual Data Models and applications into the SAP HANA server.
4. Start the initial data replication from SAP Business Suite into SAP HANA.
5. If relevant, configure the applications required for SAP HANA Live.
Postrequisites
Post-installation steps require metadata for date and time to be created using SAP HANA Studio.
Introduction
89
For more information regarding the installation of SAP HANA Live, including the applications required, the
activation of the schema, and all necessary steps, see the Administrator's Guide on the SAP Help Portal page SAP
HANA Live for SAP Business Suite 1.0.
Related Information
SAP Help Portal: SAP HANA Platform
SAP Help Portal: SAP HANA Live for SAP Business Suite 1.0
1.4.3.1
Activate
To activate SAP HANA Live, an initial table has to be created in accordance with the database being used. Virtual
Data Models also need to be imported, and data has to be replicated. For further information, read on.
Initial Table Creation in SAP HANA Live
Note
Creating an initial table is necessary for side-by-side scenarios.
Depending on the product you use, certain tables must be replicated. For a list of the tables you have to replicate,
see the following SAP Notes:
Table 13:
Package
SAP Note Number
All packages
1782065
Suite
: Tables for SAP HANA Analytics for SAP Business
sap.hba.ecc
1781992
: Tables for SAP HANA Analytics for SAP ERP 1.0
sap.hba.crm
1782066
: Tables for SAP HANA Analytics for SAP CRM 1.0
sap.hba.scm
1782067
: Tables for SAP HANA Analytics for SAP SCM 1.0
sap.hba.grc
1782068
: Tables for SAP HANA Analytics for SAP GRC 1.0
sap.hba.gts
1780655
: Tables for SAP HANA Analytics for SAP GTS 1.0
Note
Creating an initial table is only necessary in a side-by-side scenario. This means that your production system
uses another database as its primary data repository, and that a replication is in place with a SAP HANA
90
Introduction
database to feed the SAP HANA Live reporting system. If the tables are not created in the SAP HANA database
of SAP HANA Live, the replication will not have any structure to actually replicate the data.
This activation is not necessary in an integrated scenario. In an integrated scenario, your production system and
SAP HANA Live both use the same SAP HANA database as primary data repository. SAP HANA Live directly
queries the existing production of SAP HANA tables to produce its report outputs.
Import Virtual Data Models
To obtain the available VDM for your components, customers can either refer to the SAP Software Download
Center (SWDC), or use the Maintenance Optimizer with SAP Solution Manager to download the SAP HANA Live
packages. Each SAP HANA Live component has its own VDM package, as listed in SAP Note 1759574 .
Initiate Data Replication
Using the SAP HANA Live browser, customers can search, browse, tag, and consume SAP HANA analytical
content views by using an Internet Web browser. Customers can also use this application to define a list of tables
that are included in the SLT driver to set up the data replication.
Once the data replication has run its course, the VDM data model can populate data in the predefined Private,
Reuse and Query views.
1.4.3.2
Extend
This topic provides a more detailed overview of the functionality and advantages of the SAP HANA database. It
also provides you with information on SAP HANA Extended Application Services and on the SAP HANA XS server.
Traditional application-development structures use interfaces to manage and query their data. This requires an
additional intermediary controller component or an application server, acting as a broker between data
representation or applications and the actual database model.
SAP HANA greatly extends the traditional database server role. SAP HANA functions as a comprehensive
platform for the development and execution of native data-intensive applications that run efficiently on SAP
HANA, taking advantage of its in-memory architecture and parallel execution capabilities.
By restructuring your application in this way, you gain from the increased performance due to the integration with
the data source. Moreover,you can effectively eliminate the overhead of the middle-tier between the user
interface (the view) and the data-intensive control logic.
To support this data-integrated application paradigm, SAP HANA Extended Application Services provides a
comprehensive set of embedded services that provide end-to-end support for Web-based applications. This
includes a lightweight Web server, configurable OData support, server-side JS execution and, of course, full
access to SQL and SQLScript.
These SAP HANA Extended Application Services are provided by the SAP HANA XS server, which provides
lightweight application services that are fully integrated into SAP HANA. It allows clients to access the SAP HANA
Introduction
91
system through HTTP. Controller applications can run completely natively on SAP HANA, without the need for an
additional external application server. The concept of the SAP HANA XS server as part of the SAP HANA system is
illustrated in the graphic below.
By accessing the XS interface, developers can easily use the VDM Reuse views in order to build complex
representations, reports, or applications directly on top of granular data. By combining the power of the Virtual
Data Models with the functionality of rich content creation of modern development tools, you can manipulate
transactional data jointly with analytical data.
The application services can be used to expose the database data model, with its tables, views, and database
procedures, to clients. This can be done in a declarative way using OData services or by writing native applicationspecific code that runs in the SAP HANA context. You can also use SAP HANA XS to build dynamic HTML5 UI
applications.
In addition to exposing the data model, SAP HANA XS also hosts system services that are part of the SAP HANA
system. The search service is an example of this kind of system application. No data is stored in the SAP HANA XS
server itself. To read tables or views, to modify data, or to execute SQLScript database procedures and
calculations, it connects to the index server or servers, in case of a distributed system.
Related Information
SAP HANA Developer Guide
92
Introduction
1.4.3.3
Consume
This chapter provides information about how to consume SAP HANA Live and to access data from SAP Business
Suite powered by SAP HANA.
SAP HANA Live provides various methods to access data and queries from SAP Business Suite powered by SAP
HANA.
OData Services, SAP HANA XS Connections, and Standard SQL
These types of connections are made available to developers and end users who ant to create their own
applications or reports using the information and data exposed by SAP HANA Live. The various views available in
the Virtual Data Model (VDM) expose the data and ensure that any custom development leveraging its structures
returns results in a consistent manner. The OData service model definition enables developers to rapidly create
services for existing SAP HANA database artifacts. If application developers need more control over the
processing logic, SAP HANA XS offers XSJS services using server-side JavaScript.
Predefined SAP HANA Live Applications
● SAP Supply Chain Info Center
○ Provision of analytical reporting that works out of the box with streamlined data load
○ Decision support based on near real-time information
○ Predefining dashboards for different use cases (analytical workflows) for APO-based planning scenarios
○ Provision of use cases based on best practices for operational reporting on APO data leveraging the full
potential of SAP
● SAP Invoice and Goods Receipt Reconciliation
○ Improved clarification process for invoices
○ Avoidance of paying unjustified vendor invoices
○ Fostering communication between different departments
○ Quick retrieval of the purchasing history, receipts by vendor, and contact data for clarification
○ Avoidance of confusion that might be caused by different screens
● SAP Working Capital Analytics, DSO (Days Sales Outstanding) Scope
○ Allows real-time analysis of drivers of a company‘s days sales outstanding (DSO)
○ Enables interactive buildup of flexible analysis paths to analyze data
○ Innovative visualization of analysis process sequence
● SAP GRC Access Control Role Analytics
○ Analysis and deletion of roles out of GRC that have not been used for a certain period of time
○ Analysis and decommissioning of roles that have not been included in other roles or assigned to any user
for a certain period of time
○ Monitoring and analysis of roles that have been frequently used
○ Initiating risk analyses
Introduction
93
SAP HANA Live Browser is an HTML5-based Web application that allows you to quickly and easily search, browse,
tag, and consume views created for SAP HANA Live. SAP HANA Live Browser also allows you to seamlessly
consume data into SAP Lumira or SAP Analysis for Office. SAP HANA Live Browser allows you to generate SAP
Landscape Transformation Replication Server files for a view or a package as a .csv file. The SAP Landscape
Transformation Replication Server file contains information about tables that need to be replicated for a certain
view or package to work. SAP Landscape Transformation Replication Server allows you to use .csv files to
replicate the required tables.
SAP BusinessObjects Tools Compatible with SAP HANA Live
You can use various SAP BusinessObjects tools together with SAP HANA Live o create and integrate reports for
example, to visualize and manage data, or to insert crosstabs.
● SAP Crystal Reports for Enterprise
A reporting tool that allows you to create feature-rich reports and integrate them into Web and Microsoft
Windows applications.
● SAP BusinessObjects Dashboards
A software product for data visualization that customers can use to create dynamic and interactive
dashboards.
● SAP BusinessObjects Explorer
A tool that combines simplicity and speed of Internet search with the analytical power of SAP Business
Intelligence – for faster, more informed decision making. It allows you to analyze data and the relationship
between different blocks of data new ways not offered in the classic SAP Business Intelligence Tools.
● SAP BusinessObjects Analysis, Edition for Microsoft Office
A Microsoft Office add-in that allows a multidimensional analysis of OLAP sources. The data is displayed in
the workbook in crosstabs. You can insert multiple crosstabs in a workbook containing data from different
sources and systems.
● SAP Lumira
SAP Lumira is a data manipulation and visualization tool. You can connect to various data sources, select and
clean data, and manipulate and visualize data with a diverse offer of graphical charts and tables. SAP Lumira
is installed locally and can operate on data either remotely or on locally stored datasets.
Related Information
Predefined SAP HANA Live Applications
SAP Working Capital Analytics, DSO Scope
94
Introduction
SAP BusinessObjects Tools Compatible with SAP HANA Live
SAP Crystal Reports for Enterprise
SAP BusinessObjects Dashboards
SAP BusinessObjects Explorer
SAP BusinessObjects Analysis, edition for Microsoft Office
SAP Lumira
1.4.3.4
SAP HANA Live Rapid Deployment Solution
SAP HANA Live contains a solution that can be used to analyze data and to create reports.
The SAP HANA Live rapid-deployment solution enables real-time reporting on operational data from SAP
Business Suite software. This rapid-deployment solution provides pre-built reporting content to for simpler and
faster analysis of operational data based on Virtual Data Models on the SAP HANA platform, with best practices
and a service offered for a fixed scope and timeline.
Related Information
SMP: SAP HANA Live rapid-deployment solution
SAP HANA Live rapid-deployment solution
1.4.3.5
Documentation Reference
For more information about SAP HANA Live and relevant applications, see the documents linked in this topic.
The following documents outline best practices and specific scenarios regarding the deployment of SAP HANA
Live:
Table 14:
Link
Description
How to Utilize the View Browser Application Which Accompanies SAP HANA
The View Browser application that accompa
nies SAP HANA Live for SAP Business Suite is
available as an option for business users who
want to interact with SAP HANA content views
using an Internet Web browser instead of us
ing the SAP HANA studio.
Live for SAP Business Suite
How to Enhance SAP HANA Live:
https://scn.sap.com/docs/DOC-44726
http://www.saphana.com/docs/DOC-3884
Introduction
This guide demonstrates how to leverage SAP
HANA Live content to amalgamate SAP data
coming from different SAP Business Suite
source systems to provide a central view that
is used in reporting and analytics.
95
Link
Description
How to Realize Cross-System Reporting Using SAP HANA Live Content
This guide demonstrates how to leverage SAP
HANA Live content to amalgamate SAP data
coming from different SAP Business Suite
source systems to provide a central view that
is used in reporting and analytics.
http://scn.sap.com/docs/DOC-42917
http://www.saphana.com/docs/DOC-3885
How to Utilize the HANA Analytics Authorization Assistant for the SAP HANA
Analytics Foundation for SAP Business Suite
The SAP HANA Analytics Foundation (SHAF)
Analytics Authorization Assistance is available
as an option for security administrators who
want to create analytic privileges based on
SAP Business Suite security profiles or per
form mass maintenance of privileges. With this
automation tool, administrators can provide
users with authorizations in the SAP HANA
system to access data exposed by the data
base views of the SAP HANA Analytics Foun
dation for SAP Business Suite.
Note
This document was created in early 2013
and has not been updated since then. It
therefore uses the old term SAP HANA An
alytics Foundation while actually referring
to today's SAP HANA Live.
1.4.4
Code Migration and Optimization
This section deals with the question of what happens to the custom or partner ABAP developments when
migrating a system to SAP HANA.
Excecutive Summary and Key Takeaways
● Activate Usage Analysis - Usage and Procedure Logging (UPL) and SQL Monitor (SQLM) - as early as possible
in your productive SAP Business Suite environment.
● The longer the UPL runtime is, the more realistic is the usage picture you get. This is the basis to prepare for
custom code assessment even before you start with the SAP Business Suite powered by HANA migration
project.
● The data collected by SQLM together with SWLT provide a good overview of the custom code quality and help
to establish the base for custom code adjustment
● Check for existing SAP guidelines and best-practice documents regarding the process of migrating and
optimizing custom code. Align your internal development guidelines according to the SAP best-practice
documents.
● Ask your SAP contact for available SAP services that can help you mastering your migration to SAP HANA or
to support the custom code migration
96
Introduction
Custom Code Migration and Optimization - What It Is and Why?
To understand the impact of SAP HANA on your custom code, you always have to ask the following questions:
● How can custom code be adjusted to improve performance with SAP HANA?
● Is any custom ABAP code likely to cause performance issues with SAP HANA?
● Which programming rules should be applied to avoid functional issues?
● Which of the main businesses processes could potentially be massively sped up by SAP HANA?
● Which transaction should be both technically migrated and redesigned to use the full speed of SAP HANA?
● Pushing code to SAP HANA enables the full potential of SAP HANA to leverage the most important business
processes and transactions.
For more information about migrating your custom code to the SAP HANA database, see Custom Code Migration.
For more information about speeding up the execution of your custom code on the SAP HANA database, see
Custom Code Optimization.
● Custom Code Migration [page 99]
● Custom Code Optimization [page 100]
Business Value of Custom Code Migration and Optimization
● Streamlined architecture to provide better support for business growth
● Ability to fully leverage the standard SAP functionality
● Increased speed for your current business processes
● Custom code clean up and reduction of overall adjustment effort
● Reduction of maintenance time, costs, and efforts
● Easier implementation of new functional extensions
● No delays and upfront investments for a project if you use SAP HANA Enterprise Cloud
● Benefit from a consolidated architecture in day-to-day work
● Knowledge about the required impact to current landscape when migrating
Custom Code Migration and Optimization - How to Do It and What to Bear in
Mind?
The Custom Code Migration and Optimization approach contains two steps:
● Custom Code Assessment [page 101]
● Code Adjustment [page 106]
For videos and more information, see the information section.
Introduction
97
Related Information
ABAP for HANA Code Push-Down
Development scenarios with ABAP and SAP HANA
Transitioning Custom ABAP Code to SAP HANA - Best Practices and Recommendations
Top 10 FAQs about ABAP for SAP HANA
SQL Monitor Unleashed
ABAP for SAP HANA Reference Scenario
HA400 - ABAP Programming for SAP HANA
SAP HANA Academy
How to Evaluate ABAP Coding for Optimization on SAP Suite on HANA
HANA Reference for Developers - Links and SAP Notes (Part 1)
HANA Reference for Developers - Links and SAP Notes (Part 2)
SCN: ABAP for SAP HANA
SAP HANA Developer Center
Optimizing Custom ABAP Code for SAP HANA – The New ABAP SQL Monitor.pdf
Videos
Introduction into Advanced View Building in ABAP on SAP HANA
How to Build Core Data Services Views in ABAP on SAP HANA
Introduction into ABAP-Managed Database Procedures on SAP HANA
How to Implement ABAP-Managed Database Procedures on SAP HANA
How to Debug an ABAP-Managed Database Procedure (AMDP)
SAP Notes
SAP Note 1885926: ABAP SQL Monitor
SAP Note 1794297: Secondary Indexes for the business suite on HANA
SAP Note 1785057: Recommendations for migrating suite systems to SAP
SAP Note 1622681: DBSL hints for SAP HANA
SAP Note 1847431: SAP NetWeaver BW ABAP Routine Analyzer
SAP Note 1051576: Conversion of Single Code Page Systems to Unicode
SAP Note 1812713: Add-on compatibility of SAP NW AS ABAP 7.4 for Suite
SAP Note 1760306: SAP EhP6 for SAP ERP 6.0, version for SAP HANA 1.0
SAP Note 1855666: Suite on HANA : 3rd party Add-ons
SAP Note 1912445: ABAP customer code migration for SAP HANA - recommendations and Code Inspector
variants for SAP HANA migration
SAP Note 1935918: Downport Code Inspector Check Variants for HANA Migration
SAP Note 1821999: Rapid database migration of SAP Business Suite to SAP HANA
SAP Note 1875529: Code Inspector check for ABAP access to unsorted db content
98
Introduction
1.4.4.1
Custom Code Migration
The goal of custom code migration is to ensure that customers business processes are not impacted when
migrating a productive SAP Business Suite powered by SAP HANA. Some ABAP code might be changed to avoid
potential functional issues or loss of performance.
When migrating a productive SAP Business Suite system to SAP HANA, it might be necessary to change existing
custom or partner ABAP code to ensure the functional correctness of customer business processes (SAP HANA
Code Compliance). This is only the case if custom ABAP developments rely on the technical specifications of the
old database or directly access pool or cluster tables. In general, existing ABAP code runs on SAP HANA as
before.
Table 15:
Reason
Coding to be corrected
DB Migration
Native SQL, Hints, using DB specific features
SAP HANA Architecture
Depooling and Declustering
●
Direct access of technical index information or of clusters or pools
●
Reliance on the default sorting of DB content, which is not guaranteed
For details about the SAP HANA Code Compliance requirements, see 1785057
.
Custom code migration also deals with the question if any custom ABAP code were likely to cause performance
issues with SAP HANA.
Several scenarios immediately benefit from SAP HANA without the need for any adjustments. These include
aggregations, scan on non-indexed table fields, and high physical I/O. Other scenarios require adjustments to
achieve satisfactory performance. While analyzing your coding, there are a number of golden rules to adhere to in
order to ensure that your custom ABAP will not cause performance issues with SAP HANA. Existing golden rules
for Open SQL remain valid as general recommendations, but there have been a number of priority shifts, in the
case of index definition (lower) and avoidance of nested selects (higher) for example. Simple corrections in ABAP
frequently have a major impact on performance, for example replace nested SELECTs with FAE.
The purpose of SAP HANA is to increase performance. However, one of the main questions is which development
rules and custom code changes can help us achieve tangible performance improvement. To answer this question,
follow the golden rules described below.
Note
These golden rules for Open SQL remain valid as general recommendations.
Table 16: Golden Rules
Keep the result sets small
●
This means:
Rule still valid
Introduction
99
Minimize the amount of transferred data
●
This means:
Rule still valid
Minimize the number of data transfers
●
This means:
○
Rule still valid and even more relevant for SAP HANA
○
Prefer array operations for INSERT, UPDATE, and
DELETE when changing many records
○
Avoid nested SELECT loops
Minimize the search overhead
●
This means:
○
Rule still valid
○
In most cases, SAP HANA does not require secon
dary indexes
Keep load away from the database
●
1.4.4.2
This means:
○
Keep unnecessary load away from the database
○
Push down code for data-intensive calculations to
benefit from SAP HANA
Custom Code Optimization
SAP HANA code optimization allows you to target the potentially huge performance improvements of your
current performance pain points regarding business processes and transactions due to SAP HANA innovations.
First, it has to be clarified which main business processes have the potential to massively speed up SAP HANA.
With custom code optimization, customers can best exploit the capabilities of SAP Business Suite powered by
SAP HANA and thus hugely accelerate their main business processes.
In some cases, pushing code from the ABAP application level to SAP HANA unleashes the full potential of SAP
HANA. SAP HANA offers advanced view modeling,for this, for example Attribute views, Analytic views, and
Calculation views that are modeled or coded by using SQL script.
These views can be accessed by standard SQL:
● With ABAP < 7.40 these views can only be accessed at a low level through the native SQL (ADBC - ABAP
Database Connectivity)
● With ABAP 7.40 these views are natively supported in ABAP and can be accessed through the standard Open
SQL. Automatic client handling can be supported, and DDIC types can be mapped.
Another way to push down functional logic into SAP HANA is offered with stored procedures in SQLScript – an
extension to SQL for expressing data intensive application logic. Stored procedures are invoked through the CALL
SQL statement by passing the importing and exporting parameters, which can be scalars or table types.
● With ABAP < 7.40 stored procedures can be called using ADBC. This requires the following:
○ Manual handling of transfer tables for input and output parameters through temporary tables or result
views
100
Introduction
○ Manual mapping of database types to DDIC types
● With ABAP 7.40 stored procedures are natively supported in ABAP
○ Exporting and importing parameters, for example for function modules (including mapping parameter to
DDIC types)
1.4.4.3
Custom Code Assessment
A custom code assessment is executed in the customer's current system landscape and consists of three parts:
the code analysis, usage analysis, and definition of the master work list.
Code Analysis
With regard to SAP HANA code compliance, the enhanced Code Inspector offers static, rule-based checks to
easily find the code patterns that require corrections. The result of this analysis should be a complete list of all
mandatory findings.
Usage Analysis
The analysis of the custom code that is currently used is probably the most important part. It helps to identify and
quantify the affected coding and consequentially reduces the overall adjustment effort. To get a realistic code
usage profile, the usage analysis is normally run in a productive system or at least in a test system where realistic
tests are running. The result is a list of codings with the highest and the lowest footprint.
Custom code migration is a substantial part of any system upgrade. With SAP HANA, certain technology aspects
have changed, for example cluster and pool tables, and custom code needs to be adjusted over and on top of
other modifications. At the same time, many custom developments are not used any more. Custom Code Usage
Analysis monitors your productive system environment and show you which custom code is critical and which is
not used any more. Usage monitoring with the SAP standard tools does not have a significant impact on
productive operations. It is advisable to keep it activated for a longer period to provide qualified results.
SAP offers two standard tools to run the usage analysis
● Usage and Procedure Logging (UPL)
● ABAP SQL Monitor (SQLM)
Usage and Procedure Logging (UPL) is a new functionality available with any ABAP-based system based on the
core functionality of SAP Coverage Analyzer. UPL becomes standard with SAP Netweaver 7.01 SP10 or 7.02 SP9
+ Kernel 720 Patch 94 or 7.31 SP3 and 7.40.
In a live ABAP-based SAP system, a large number of different SQL requests are executed by the most diverse
processes. To find performance hotspots and also potential for optimizations in this very broad SQL load profile,
you require specialized SQL monitoring tools that also provide a connection to the running ABAP processes. The
new ABAP SQL Monitor (SQLM) allows monitoring the performance of ABAP SQL executions in productive ABAP
system, and links back to the driving entry point of the related business process, for example transaction code,
report name, RFC module, and URL. Aggregated performance key figures, such as number of executions,
Introduction
101
execution time, and records read, are collected per ABAP SQL command. This provides total transparency of the
running SQL in production environment and after a certain active SQL monitoring phase, for example, one day,
one week, or one month, the collected SQL monitor data can be used to answer, for example, the following
questions:
● Which SELECT in the customer code is executed most frequently in production?
● Which SELECT statements cause the longest runtime?
● Which SELECT in the customer code reads the most data?
● What does the SQL profile of the report XYZ or of transaction ABCD look like?
For more information about the availability and necessary preparation steps of the SQL Monitor, see OSS note
1885926 .
Standard analysis tools such as SQL trace or ABAP runtime analysis do not provide realistic picture because the
data volume, scenario, and usage of the analyzed transactions might be different in day-by-day business in
production. You might also miss a lot of processes, such as RFCs and batch processes, which represent the main
productive business scenarios containing a significant amount of SQL performance potential.
Define Master Work List
Generally, the definition of the master work list is a topic that requires the involvement of various parties, for
example business, development, and IT. This approach ensures that customers set the focus on custom code
modifications that have to be considered for the purpose of core business processes.
To define a prioritized list of custom code that has to be changed, you merge usage data of the dynamic
assessments with the affected static coding analysis.
● Define context from business perspective (entry point, transaction, involved data)
● Detect places with best cost and benefit ratio
● Find places where code can be pushed down to SAP HANA
● Fix performance bugs and unexpected database accesses
● Identify and exclude unused code
SQL Performance Work List Tool (SWLT) provides the functionality to combine, the static performance check
results for a given SQL statement with the relevant runtime data from a productive system. This combination of
data makes it easy to rank and filter the list to generate an optimized SQL performance tuning worklist.
102
Introduction
Example
You can download the SQLM data into a .zip file (XML format) and can upload the file in an SQL Monitor
snapshot in transaction SQL Performance Tuning Work List (SWLT):
Table 17: Overview of the Tools Supporting the Custom Code Assessment Activities
Code Analysis (1)
Usage Analysis (2)
Define Master Work List (3)
Description
Description
Description
●
Identify affected coding
●
Identify critical custom code
●
Define functional and performance
findings
●
Identify unused code
Result
●
Result
List of all findings
Tools
●
●
Code Inspector (DEV)
●
Code Inspector (Sandbox)
●
For Improvement:
●
1.4.4.4
UPL
Merge usage data with affected
coding analysis
●
Define the master work list that
contains a prioritized list of affected
custom code
Result
List of coding with highest / lowest
footprint
Tools
●
●
Prioritized list of coding that has to
be changed
Tools
●
SQL Performance Worklist Tool
(SWLT)
SQLMonitor (PROD)
Custom Code Management Approach
SAP provides an approach to manage the whole lifecycle of custom code objects for special business processes
needs. This methodology is based on Solution Manager applications.
Context
The innovative concept of Custom Code Management from SAP provides a comprehensive insight on how
companies can efficiently and effectively manage their home-grown custom code. From conception to retirement,
Custom Code Management delivers transparency on custom code objects, automates the analysis of every
change, and clearly identifies the objects' usage, utilization, and business impact. It also supports the optimization
cycles with a project-based approach to reduce the custom code footprint.
Introduction
103
This allows you to find SAP HANA optimization potential in existing ABAP custom code.
Note
There is no need to adapt all objects. Just focus on the most critical objects in terms of usage and impact.
Procedure
1. Capture the custom code footprint using Custom Code Lifecycle Management (CCLM).
2. Reduce the scope to objects that are used by leveraging Usage Procedure Logging (UPL).
3. Identify the impacted objects using ABAP SQL Monitoring (SQLM), Code Inspector (SCI), and ABAP Test
Cockpit (ATC).
4. Focus on objects that are critical for the business and with the most optimization potential with SAP
Performance Tuning Worklist (SWLT).
Related Information
Custom Code Lifecycle Management (CCLM) [page 104]
For more details about the Custom Code Management approach and the functional integration of the toolset, see
the link above.
1.4.4.4.1
Custom Code Lifecycle Management (CCLM)
Based on SAP Solution Manager, SAP provides a methodology that allows you to manage your custom code in a
holistic way instead of by performing administrative tasks. This helps to improve the quality of your custom code
104
Introduction
migration and optimization process, at the same time reducing the risk to impact other objects and the business
processes. It also helps to control and lower the total costs of your SAP Business Suite powered by SAP HANA
migration project.
Actions on Custom Code
● SAP HANA Code Compliance: Eliminate native SQL, db hints, check access to cluster and pool tables
● SAP HANA Performance: Review business critical transactions (top <x> most used transactions) with the
focus on performance
● Customer Code Compliance: Ensure code quality, comply to customer development guidelines
● Cleaning up unused code: Monitor current usage in production, remove unused code and related objects
● Review modifications: Revert to standard wherever possible, for example from modification to BAdI
implementation)
Managing Custom Code
Challenges
● Vast amount of custom objects to be analyzed and optimized
● Several parallel development tasks such as performance, optimization, functional redesign, and modification
cleansing
● Short and tight time frame
● Multiple teams, for example on-site and off-shore
● Interdependencies: Potential clashes between development teams, for example logical sequence vs. reality
● Precise coordination between development teams and test team required
● Daily reporting and detailed status tracking needed
How can we…
● Get a single view on all tasks?
● Plan and dispatch?
● Monitor progress and report?
To achieve this goal, the Custom Code Lifecycle Management application (CCML) in the SAP Solution Manager
serves as a central tool with a central object repository to manage and track the project activities related to
custom code. It supplements existing tools in the SAP Solution Manager and was developed especially for the
purpose of supporting your ABAP custom code developments throughout their lifecycle. The central repository of
the CCLM represents a collection of custom code objects that needs to be populated by the different code
analysis tools. Assigned attributes that are provided during the object analysis phase make it possible to control
the custom code change process.
Introduction
105
1.4.4.5
Code Adjustment
SAP offers a Custom Code Migration Service for SAP Business Suite powered by SAP HANA. For customers or
partners who want to carry out the migration themselves, SAP provides the code guidelines described in this
topic.
Evaluating ABAP Coding for Optimization on SAP Business Suite powered by
SAP HANA
If you have completed the migration to SAP ERP on SAP HANA within your SAP system landscapes, you can start
looking at areas where the ABAP program code can be optimized for performance improvement. This applies
especially to customized code in customer namespaces that you were already executing in the SAP production
system. Standard application code delivered by SAP is already automatically optimized during the migration. In
this case, the guide How to Evaluate ABAP Coding for Optimization On SAP Suite on HANA n be very useful. The
guide primarily focuses on three standard enhanced or new mechanisms that are made available by SAP. These
mechanisms help you to identify and evaluate the customized program code based on both the static and
dynamic usage of the SAP ERP on SAP HANA application.
The three mechanisms that will be discussed are:
● SAP Code Inspector (Enhanced)
● SQL Monitor (New)
● SQL Performance Tuning List (New)
106
Introduction
For more information, see How to Evaluate ABAP Coding for Optimization on SAP Suite on HANA
.
Considerations for Custom ABAP Code During Migration to SAP HANA
SAP HANA is a fully-fledged relational database system optimized for transactional (OLTP) and analytical (OLAP)
processing. As the underlying database system for the SAP Business Warehouse and the SAP Business Suite, it is
fully compatible based on the SQL support in the SAP NetWeaver Application Server ABAP. Due to the nature of
the in-memory columnar storage in SAP HANA, there are a few recommendations to consider during the
transition of custom ABAP developments to SAP HANA. The main focus during the execution of code adjustments
should always be on two aspects:
● Avoiding functional regressions during migration: During every database migration, you need to revisit
existing database-dependent coding based on the previous database system. This also includes coding
relying on undocumented implicit behavior.
● Detecting performance optimization potential: SAP HANA allows insignificant optimization of the
performance of existing ABAP developments. To fully benefit from the power of SAP HANA, certain data
access patterns should be revisited and optimized, in particular when classic performance recommendations
for Open SQL were not previously taken in to account
For more information, see Considerations for custom ABAP code during migration to SAP HANA. This document
guides customers and partners regarding existing custom ABAP developments when migrating to SAP HANA.
Additionally, it contains an overview of the available tools and provides guidance on how to use them in the
context of a migration to SAP HANA. In particular, it explains the steps that can be followed before a technical
migration takes place. It also includes steps that need to be considered independently from SAP HANA. The
document primarily addresses ABAP coding in combination with standard database access through Open SQL.
For some specific environments and frameworks, additional guides and recommendations may exist. On the other
hand, the document does not discuss the concrete optimizations of standard SAP code in the SAP Business Suite
powered by SAP HANA. It also does not give recommendations for using native SAP HANA development options,
for example column views or database procedures, to optimize the performance. Furthermore, the document is
not a replacement for existing approaches for performance optimization of SAP solutions, such as system tuning
and hotspot analysis. For these aspects, consider, for example, existing SAP services or similar offerings.
For more information, see Best Practice Guide - Considerations for Custom ABAP Code During a Migration to SAP
HANA .
1.4.4.6
Effort Estimation
During the Code Analysis process, you identified the affected custom coding. After defining the functional and
performance findings, you identify the critical custom code and the amount of unused code in the Usage Analysis.
At this point, one of the main tasks is to obtain list of coding with the highest and lowest footprint. After merging
the sage data with affected coding analysis, you can start to create the master work list that contains a prioritized
list of affected custom code.
Throughout the whole process, it is always advisable for various parties of business, IT or development, or all of
these, to be involved. The first priority should be on bug corrections, such as missing explicit sorting. Secondly,
simple corrections on ABAP with a major impact, for example a missing WHERE condition in widely used coding.
The second priority should be on simple corrections in ABAP with a minor impact. Corrections of low value that
Introduction
107
require much effort should be reviewed closely if there is a real need for them. If you identify processes where a
complete redesign is necessary to use the full speed of SAP HANA, a code pushdown to the database is
necessary, for example.
Recommendation
We recommend setting new projects after ABAP code has been migrated.
Note
SAP offers the Custom Code Migration Service for SAP Business Suite powered by SAP HANA and is delivered
with its own assets and service content. It contains a draft for a master work list provided by SAP. For
customers or partners who want to migrate their code themselves, SAP provides different code guidelines that
are described in this cookbook.
To get started, you can use the Microsoft Excel template linked below to insert all functional and performance
issues that you have identified during your analysis. This template provides you with an overview of the findings
and a better basis for your project planning estimations. As this is not a general SAP template, it is not possible to
warranty that it is complete.
Consider the following points also during your planning activities and your effort estimations:
● The analysis and preparation of the customer code can start before the SAP HANA migration. The required
tools do not depend on the database used and some are also available in earlier SAP NetWeaver releases.
● The functional adjustments and the first round of (simple) performance optimizations are usually very
manageable and are local corrections that do not require in-depth application knowledge.
● The results of the static performance checks can generate a very high number of messages. However, this is
not a cause for concern because these performance checks are of an informative nature (for example, there is
a nested SELECT) and can only be effectively used in combination with relevant performance data. The
addition of performance data (SQL Monitor) usually reduces the number of recommended performance
correction to a low two-figure digit.
● Customers can access extensive support offered by SAP Consulting and SAP Support for the SAP HANA
migration.
Related Information
Code Migration Effort Estimation Template for SAP Business Suite powered by SAP HANA migration projects
1.4.4.7
Functional Test Plan
During the scope identification, you can set up a functional test plan for critical business processes.
In addition to ur important business processes, you need to test business transactions that include modifications
and custom code. This aspect is of equally high importance, as igrating from a traditional database to SAP HANA
might impact transactions that include modifications or custom code, or both.
108
Introduction
Recommendation
It is recommended to set up a functional test plan for modifications and custom code.
You can make use of the static code analysis with ABAP Test Cockpit and UPL or the static and dynamic code
analysis with SQL Performance Tuning Worklist (SWLT).
Recommendation
It is strongly recommended to create a regression test plan section especially for business process tests with
adjusted custom code and modifications.
The goal is to have no negative impact on critical business processes and at the same time to reduce the
regression test effort as much as possible. The most efficient way to create a risk-based and effort-optimized test
plan is to use the Business Process Change Analyzer (BPCA) of SAP Solution Manager.
Related Information
Best Practice: Test Management for SAP Business Suite on SAP HANA Migration Projects
1.4.4.8
Tools Overview
The following section provides you with a summary of tools mentioned in previous sections. These support you in
your custom code migration and optimization tasks.
SAP Code Inspector (SCI) / ABAP Test Cockpit (ATC)
SCI is the standard tool for analyzing ABAP developments to detect potentially critical source code in terms of
performance, security, globalization, or quality in general. The code is analyzed by performing a set of selected
checks that can be grouped into different check variants. SCI is integrated into the ABAP Test Cockpit, a universal
tool for quality assurance of custom developments. For further details about C and SCI, and w to use them, see
ABAP Test Cockpit / SAP Code Inspector of the following document:
Best Practice Guide - Considerations for Custom ABAP Code During a Migration to SAP HANA
For more information, see ABAP Test Cockpit – an Introduction to SAP’s new ABAP Quality Assurance Tool
Introduction
.
109
SQL Monitor (SQLM)
SQLM allows you to ace the performance of all ABAP SQL executions in production, and links back to the driving
business processes. The new ABAP SQLM provides total transparency of the running SQL statements in a
productive environment and is a central tool to be used in your performance optimization process.
Recommendation
To be thoroughly prepared for custom code migration and optimization, we recommend activating LM as early
as possible in your productive SAP Business Suite environment. The longer the runtime is, the more detailed e
SQL trace line will be, and the more realistic the usage and performance picture of your business processes.
For more information and best practices, see Optimizing Custom ABAP Code for SAP HANA – The New ABAP
SQL Monitor .
Usage and Procedure Logging (UPL)
UPL is a new functionality available in any ABAP-based system, based on the core functionality of SAP Coverage
Analyzer. It is used to retrieve usage data about all called and executed ABAP units, such as programs, function
modules down to classes, methods, and subroutines. It then ends these SAP Business Warehouse. UPL does not
affect your system's performance in any way, d catches usage information of ABAP routines directly when they
happen. It provides you with 100% coverage of usage without estimations or evaluation of ABAP call stacks. This
also includes detection of dynamically called ABAP elements. UPL is the only technology to close the existing gaps
in the SAP workload statistic:
● UPL data is cross-client data and measurements are taken system-wide
● UPL data also includes indirect calls
UPL will support you to evaluation the real usage after the custom code was requested and will help you to focus
on the right requirements in the upcoming development cycles of custom code migration and optimization.
For more information about UPL and about how to use it, see Creating Check Steps for Objects Recorded by
Usage Procedure Logging and Custom Code Management Roadmap .
SQL Performance Worklist Tool (SWLT)
SWLT enables you to identify ABAP SQL code that has potential for performance improvement. This tool allows
you to combine the result list of the new static ABAP code scans (ATC/SCI) with the runtime monitoring data of
SQLM or UPL, and creates a unified worklist. This worklist allows you to rank and filter the findings according to
your business process specific performance issues. For prerequisites and best practices on SWLT, see SQL
Performance Tuning Worklist of Best Practice Guide - Considerations for Custom ABAP Code During a Migration
to SAP HANA . For more information, see SQL Performance Tuning Worklist SWLT help .
110
Introduction
Repository Data Analyzer (RDA)
RDA is a stand-alone tool for performing static code scans to create a hierarchical ABAP code dependency tree.
This dependency information can be used to identify unused code objects when cleaning up your custom code.
The code scan is usually executed periodically in your QA system and allows a top-down and a bottom-up
approach. RDA is offered as a project-based solution of the SAP System Landscape Optimization. For more
information and contacts, see System Landscape Optimization .
1.4.4.9
Code Migration Service
Main Service Content of the Service
● Analysis of usage of custom code with Usage and Procedure Logging
● Scan of custom code to identify impacted objects
● Definition of master worklist and project plan to adapt custom ABAP coding
● Adaptation can be done through remediation or retirement
● Final result presentation including detailed roadmap, project plan, proposals for next services, and next steps
Target of the Service
● Service is target at customers who are migrating to SAP Business Suite powered by SAP HANA
● Ensure that customers' own ABA custom code is SAP HANA-compliant when migrating to SAP Business Suite
powered by SAP HANA
● Ensure that customers' custom ABAP code is SAP HANA-optimized for critical business process that are of
high value when migrating to SAP Business Suite powered by SAP HANA
Different Aspects of the Service
The service provides SAP HANA-related expert guidance from SAP regarding to different aspects that can be
separated into functional, architecture, strategy, and knowledge aspects.
Functional Aspects
● Provide information about changes in database-specific coding
● Provide a detailed master worklist to identify the coding that has to be adopted and the coding that should be
changed
Architecture Aspects
● Establish awareness about impacts of SAP HANA on ABAP coding
Introduction
111
Strategy Aspects
● Provide guidance to put details into your SAP HANA roadmap from a technical perspective
● Provide a detailed project plan for the migration of custom code to SAP HANA
● Provide a roadmap for the optimization of your custom code for your business-relevant scenarios
Knowledge Aspects
● Establish basic awareness and understanding of changes concerning your current custom code
Business Value of the Service
● Get detailed information on the investments being made n your custom coding to get SAP Business Suite
powered by SAP HANA and your custom code running
● Create guidelines for upcoming projects in custom code
Service Delivery
● Kick-off and result presentation on-site, analysis can be done remotely.
● Expert consultants (technical and regarding application)
● Fixed price
1.4.4.9.1
Service Details
One core element of the service is the Custom Code Assessment for SAP Business Suite powered by HANA. The
service provides SAP HANA-related expert guidance from SAP Consulting.
Functional Aspects
● Provide information about changes in database-specific coding
● Provide a detailed master work list to identify the coding that must be adopted and the coding that should be
changed
Architecture Aspects
● Establish awareness about SAP HANA impacts on ABAP coding
112
Introduction
Strategy Aspects
● Provide guidance to put details into your SAP HANA roadmap from a technical perspective
● Provide a detailed project plan for the migration of custom code to SAP HANA
● Provide a roadmap for the optimization of your custom code for your business-relevant scenarios
Knowledge Aspects
● Establish basic awareness and understanding of changes concerning your current custom code
The following figure illustrates the workflow of the service:
Introduction
113
The following figure illustrates the scope of the service regarding performance improvement:
Business Value
● Obtain tailed information about he investments being made to your custom coding to get SAP Business Suite
powered by HANA and your custom code running
● Create guidelines for upcoming projects in custom code
Service Content
Analysis of the use of custom code with a UPL scan of custom code, thus identifying impacted objects.
● Definition of the master work list and a project plan to adapt custom ABAP coding
● Adaption can be done by means of remediation or retirement
● Final result presentation including a detailed roadmap, project plan, proposals of next services, and next steps
Service Delivery
● Kick-off and result presentation on-site, analysis can be done remote.
● Expert Consultants (technical and regarding application)
● Fixed price
114
Introduction
1.4.4.10 Best Practices and Guidelines
Before starting with a custom code migration and optimization project, it makes sense to check existing best
practices and guidelines. A number of golden rules should also be taken into account. You might need this
information to save time, focus on the most important activities, and to benefit from the experience of others.
Best Practices for ABAP Custom Code Transition to SAP HANA
This guide provides you with best practices and recommendations, and gives you detailed considerations
regarding custom ABAP code when migrating to SAP HANA. It describes typical usage scenarios and explains
how to make use of the relevant tools. Based on the simple process model with the three phases Planning,
Migrate, and Optimize it explains the recommended steps and approaches that you can use as a checklist when
planning the migration project.
Best Practice Guide - Considerations for Custom ABAP Code During a Migration to SAP HANA
ABAP on SAP HANA - From Analysis to Optimization
A considerable number of guidance documents and blogs in the SAP Community Network also provide you with
best practices and guidelines. One of them is the ABAP on HANA - from analysis to optimization blog.
The blog describes relevant steps to maximize the effect of ABAP performance tuning on custom coding for an
SAP system running on HANA DB. It focuses on tools and guidelines delivered by SAP and starts with a procedure
describing how to find candidates, for example reports and transactions, that show a significant potential to
improve the performance, which optimizes the ABAP coding. In each section, different optimization aspects are
discussed, starting with identifying potential candidates and ending with tips and tricks from real-live projects.
The most relevant sections are:
● The golden rules – Five performance guidelines for ABAP database operations
● How to find candidates – Use ST03N
● The toolbox – Code Inspector and ABAP Trace
● Optimizing ABAP code – Use FOR ALL ENTRIES and JOINs
● Tips and tricks – Some hints based on our experience
● Code pushdown – Stored procedures and HANA Artifacts
ABAP on HANA - from analysis to optimization
Custom Code Development for HANA
The following guide focuses on the custom code optimization process. It lists different options of pushing down
ABAP code, gives examples, provides modeling recommendations, and explains what needs to be considered in
terms of the SAP HANA architecture.
ABAP for SAP HANA
Introduction
115
Performance Guidelines ABAP Development on SAP HANA
When planning a migration to SAP HANA, certain considerations related to existing custom ABAP code are
required. This includes mandatory items that are related to a change of the database platform in general, and
some additional recommendations specific to SAP HANA. If you are an experienced ABAP developer, you might
know the classical performance guidelines for using Open SQL. One of the frequently asked questions is about
what changes occur in the context of SAP HANA regarding these guidelines. Although, the priorities of some rules
are changing, which means that some aspects are less important due to the nature of the in-memory column
store, there are also certain patterns of suboptimal coding with higher impact on SAP HANA. Furthermore, there
are completely new opportunities for performance tuning on SAP HANA that were not possible in the past, for
example pushing complex operations to the database.
Performance Guidelines for ABAP Development on the SAP HANA Database
1.4.5
Test Management
Get information about how to put into practice the test management for SAP Business Suite powered by SAP
HANA migration projects. Note that there is a service available offered by SAP called Test Management for SAP
solutions that is also applicable for SAP HANA.
● Bear in mind Business Process Impact Analysis and custom code developments during your preparation
phase of Test Management
● Business process experts should be involved during all of your test activities
● Use SAP Solution Manager for example for Business Blueprint, Business Process Change Analysis, and Test
Reporting
● SAP provides the service Test Management for SAP Solutions for Enterprise Support Customers to set up
testing for SAP applications and non-SAP applications as well as for SAP HANA and SAP Mobile
Why Is Test Management in SAP Business Suite powered by SAP HANA
Migration Projects So Important?
Test Management during SAP Business Suite powered by SAP HANA migration projects is one of the most
important tasks that you have to consider. You should therefore be aware of the most important test
management activities for functional and performance tests, which allow you to migrate to SAP HANA without
negatively impacting business processes executed by SAP Business Suite solutions. This is also particularly
important for your custom developed applications.
116
Introduction
What Is the Best Test Management Approach?
If a company plans to migrate its actual SAP Business Suite solution from a traditional database to SAP HANA,
several test and validation activities are necessary. Many companies have their own strategy and approach to
handle the test management during a database migration.
Recommendation
It is advisable however to separate all test activities into three phases.
These three phases are the Preparation Phase, the SAP Suite on SAP HANA Migration Project, and the After GoLive. For more information about these phases, see Test Management Phases.
For more information about strategy, products, and capabilities provided by SAP for functional test management
and change impact analysis, see the information section.
Related Information
Application Lifecycle Management
Application Lifecycle Management Processes - Test Management
SAP Online Knowledge Products: SAP Solution Manager
Test Management Phases [page 118]
For more information, demos, and configuration guides dealing with the Test Management tools, see the following
link:
Application Lifecycle Management Processes - Test Management
For more information about strategy, products, and capabilities provided by SAP for functional test management
and change impact analysis, see the following links:
Application Lifecycle Management
Introduction
117
E-Learning Material
SAP Online Knowledge Products: SAP Solution Manager
1.4.5.1
Test Management Phases
The test management process consists of three phases: the preparation phase, the test execution phase, and test
activities that follow after going live.
Phase 1: Test Management Preparation
In this phase, a status assessment followed by an approach and tool decision is recommended for the following
test management aspects:
● Business Blueprint
● Test Scope Identification
● Test Planning
● Functional Regression Tests
● Performance and Load Tests
● Service Tests
● Reporting and Sign-off
Recommendation
SAP recommends organizing the preparation phase in separate work streams for each of these aspects.
Once the status assessment and the tools decisions have been made, the test management should be set up, and
planning activities should be carried out. At the end of the preparation phase, you can initiate the technical steps
of the SAP Business Suite powered by SAP HANA migration project.
Phase 2: Test Execution During SAP Business Suite powered by SAP HANA
Migration Project
During the migration project phase, the test team executes functional tests, performance and load tests, as well
as service and interface tests. Business process analysts will be involved during integration tests. Any incidents
that occur are analyzed, while problems are resolved, and retested. At the end of this phase, the test team signs
off the test activities.
118
Introduction
Phase 3: After Go-Live Test Activities
SAP HANA Revisions
SAP HANA maintenance activities are provided through SAP HANA revisions. Regression tests are required at the
technical and the business process level to validate the maintenance activities. Smart test-scope identification
techniques are required to avoid full regression tests that are not feasible due to time and effort constraints.
SP for SAP EHP, Version for SAP HANA
Introduction
119
Based on customer feedback, SAP has analyzed and prioritized existing transactions. Many optimizations
delivered with enhancement packages (EHPs) are active without the need for any manual steps. For a detailed list
of all improvements, see the attachment in SAP Note 1761546 .
Some of these optimizations have be activated in the IMG or through a Business Function, or both. For more
information, see the latest release notes.
Functional regression tests are therefore required at the technical and the business process level to validate the
maintenance activities. Smart test-scope identification techniques are required to avoid full regression tests that
are not feasible due to time and effort constraints.
Related Information
Release Notes SAP ERP 6.0 EHP6, version for SAP HANA
1.4.5.2
Best Practices
It is strongly recommended not to limit the test activities to technical objects. Business process tests should also
be added to the overall test scope. Business process experts (BPx) should also be involved in functional
integration tests. Manual test cases therefore need to be expressed in business language and assigned to the
business process hierarchy.
120
Introduction
Automated test scripts used for efficient regression tests are assigned to the appropriate business process of the
business process hierarchy, which enables risk-based test scope identification. At this point, documentation of
the system landscape and the business processes can be carried out with the SAP Solution Manager.
Recommendation
SAP recommends defining the Business Blueprint in the SAP Solution Manager, which allows you to efficiently
identify the test scope and subsequently execute the test. If a Business Blueprint is missing either in part or
entirely, you also have a number of alternatives available for setting up a Business Blueprint in SAP Solution
Manager.
For more information about SAP HANA test management, see the SAP Best Practice document Best Practice:
Test Management for SAP Business Suite on SAP HANA Migration Projects.
This document focuses primarily on the two most relevant SAP test options and provides you with best practices
in SAP Test Management for the SAP Business Suite powered by SAP HANA migration. In this context, you will
learn about best practices from SAP regarding the most important SAP test aspects such as:
● Test scope identification and test plan generation
● How to consider custom code migration in test plans
● Functional regression tests including test preparation and planning, test execution, reporting, and sign-off
● Performance and load tests including preparation and planning, and execution
● Service Tests
Related Information
1.4.5.3
Services
SAP Field Services Consulting offers the Test management for SAP Solutions service. This service directly
supports functional tests of strategic landscape components such as SAP HANA. The test approach of SAP is
universally applicable to all applications and technologies, both for SAP and non-SAP applications.
As far as SAP HANA is concerned, the key interest is performance and efficiency. It is also necessary however to
ensure that HANA operates effectively and stably, producing the intended and expected result. The approach to
reach this challenge is to execute end-to-end functional tests that ensure the functional correctness of the SAP
HANA server, user clients, and application servers.
Typical challenges in terms of quality assurance (QA) and testing include:
● The lack of a centralized testing approach
● The lack of a process-oriented approach to testing
● The lack of traceability throughout the application lifecycle from requirements to tests to defects
● Testing in heterogeneous landscapes
Introduction
121
● Software updates affecting mission-critical business processes
● Risk reduction
● Third-party supplier management
● On-time and on-budget delivery
● The lack of agility
● Stacked testing due to timeline crunch
Value Proposition
● Lower risk due to state-of-the-art testing tools and methodology
● Higher test quality thanks to a central testing platform
● Comprehensive and integrated reporting on all test phases
● Integration - HP QC is fully integrated with the ALM solution of SAP
Service Methodology
The service consists of four approaches:
Test Preparation and Scope During this step, the test scope is identified, and the test is prepared.
Identification
Test Planning
During this step, the test is planned, test cases are created, and the test
infrastructure is installed.
Test Execution
During this step, the test is executed. Test results are analyzed and reported.
Final Testing Activities
During this step, the optimization potential is identified, the KPI is analyzed, and
the final documentation is created.
Each test approach takes place during a certain project phase or between, sometimes overlapping with the
subsequent project phase.
122
Introduction
This concept is illustrated in the following figure:
Service Scope
The test scope identification varies depending on the type of modification.
● New SAP Solution:
With the SAP Solution Manager Business Blueprint functions, you design and document business processes,
and catalog them hierarchically. The business departments specify business requirements in the Business
Blueprint and assign manual or automatic test cases, or both, to the business processes in the Business
Blueprint.
● Update of an Existing SAP Solution
For an Update of an existing SAP solution, you check whether important applications or critical business
processes are affected by the update. To execute the tasks, the Business Process Change Analyzer (BPCA)
supports you with the analysis of change impact.
Introduction
123
These concepts are illustrated in the following figure:
In general, the service offers two different test options to support all testing related activities. Test Option 1 is
based on the test Workbench of SAP Solution Manager, while Test Option 2 uses SAP Quality Center by HP and
the integration with SAP Solution Manager.
1.4.5.3.1
SAP Solution Manager: Test Workbench
Test Management with SAP Solution Manager: Test Workbench
SAP customers who select test option 1 use test management capabilities provided by SAP Solution Manager. In
this setup, test cases for single business transactions or end-to-end business processes are assigned to the
Business Blueprint at the appropriate level, which is the basis for all subsequent test management activities.
Test Preparation
● Scope identification
124
Introduction
● Configure Solution Manager:
○ For test case management
○ Refer to the message template
○ Complete all configuration through STWB_SET
○ Set up test systems in Solution Manager
○ Set up workflow and e-mail notification
Test Planning
● Set up manual test strategy
● Create test plans and test packages
● Create tests and store them in SOLAR02 for unit, integration, and user acceptance test
● Create test plans and test packages
● Assign users to test packages
● Define test sequence for manual tests
Test Execution and Reporting
Test Preparation
● Execute test cases for string and integration tests
● Report progress
● Coach defect tracking and monitoring
● Solution Manager BI integration provides graphic-based reports
Test Management with SAP Solution Manager and SAP Quality Center by HP
SAP customers who select test option 2 use test management capabilities provided by SAP Quality Center by HP
and integration with SAP Solution Manager. In this setup, the company transfers the Business Blueprint nodes
from SAP Solution Manager to the requirements module. The test cases are defined in the test plan module and
assigned to the items of the requirements module, which is then the basis for all subsequent test management
activities.
Setup of Solution Manager or QC Adapter
● Provide basic knowledge transfer
Test Preparation
● Scope identification by specifying releases
● Create project and users
● Synchronize business and test requirements from Solution Manager to HP QC
● Configure HP QC dashboard for reporting
● Configure basic defect workflow
Test Planning
● Set up manual test strategy
Introduction
125
● Create test in test plan or upload through Microsoft Excel add-in
● Create test sets in test lab for unit, integration, and user acceptance test
● Plan and schedule tests
Test Execution and Reporting
● Execute string and integration test
● Report progress
● Coach defect tracking and monitoring
1.4.5.4
Test Automation Tools
The guiding principle for test automation is always to reach the highest test coverage at the lowest possible level
(module level) to ensure robustness and performance. Every customer is faced by a number of test automation
challenges with each upgrade or migration.
The challenges that a customer might face during an upgrade or migration process include :
● High costs to create automated tests
● Costly to maintain after every UI change
● Business users must have the functional expertise
● Requires technical proficiency
● Replication test data similar to production data is complex
Business Value of Test Automation Tools
● Reduce maintenance effort
● Reduce implementation time for new tests
● Increase test coverage
● Increase test efficiency
SAP Test Automation Framework
Test Automation Framework is fully integrated into SAP Solution Manager and allows you to directly create test
cases based on SAP and certified external tools in the business-process context automatic.
SAP offers the following Test Automation Framework tools and products in combination with SAP Solution
Manager:
● Component Based Test Automation (CBTA)
● Extended Computer Aided Test Tool (eCATT)
● SAP Test Acceleration and Optimization (TAO)
● SAP Quality Center by HP
● Business Process Change Analyzer (BPCA)
126
Introduction
Recommendation
For SAP Business Suite powered by SAP HANA migration projects that are handled using test management
capabilities provided by SAP Solution Manager:
It is recommended to use SAP Component Based Test Automation (CBTA) for all test automation activities
based on SAP GUI such as SAP ERP, or on SAP CRM Web UI such as SAP CRM.
Recommendation
For SAP Business Suite powered by SAP HANA migration projects that are handled using test management
capabilities provided by SAP Quality Center by HP and integration with SAP Solution Manager:
It is recommended to use SAP Test Acceleration and Optimization (SAP TAO) for all test automation activities
based on SAP GUI such as SAP ERP, or on SAP CRM Web UI such as SAP CRM.
Recommendation
For systems not based on SAP GUI or SAP CRM Web UI, for example Portal, Business Objects, BW, or Crystal
Reports:
These systems are often part of SAP Business Suite powered by SAP HANA migration projects. It is
recommended to complete CBTA or SAP TAO by using, for example, HP Quick Test Professional (QTP).
Component Based Test Automation (CBTA)
CBTA stands for Component Based Test Automation. It is shipped with SAP Solution Manager 7.1 SP07 and the
license is included in the SAP Enterprise Support contract. CBTA allows the creation of automatic tests via a
dedicated recorder. It supports scenarios on systems under test that are based on the SAP GUI or CRM WEB UI
technology.
Component Based Test Automation (CBTA) – Customer Benefits
● Test creation wizard for business analysts to create test scripts
● Composition of test scripts by reusing default components delivered by SAP and customer-specific screen
components
● Composition of automated E2E process tests including parameter handover between the test components
● Fast repair of damaged CBTA test scripts because of modular approach
● Separation and central planning of test scripts, test data, and systems under test
● Test scripts, test data, systems under test are separated and centrally planned
● CBTA is fully integrated with SAP Solution Manager 7.1 through Test Automation Framework
● Usage rights are included for customers with SAP Enterprise Support contract
Compared to eCATT (record and playback approach), CBTA test scripts follow a modular approach. Therefore,
test components can be reused and damaged test scripts be repaired fast. Apart from that, CBTA scripts can be
created easily by business analysts while eCATT requires developers' expertise to creation and maintain test
cases.
Introduction
127
CBTA is composed out of 2 software components: An add-on to be installed on SAP Solution Manager 7.1 from
SP7 on, and a front-end component to be installed on the user's desktop. Installation and configuration of both are
described with SAP Note 1763697 .
extended Computer Aided Test Tool (eCATT)
eCATT enables automatic testing in SAP GUI for Microsoft Windows and SAP GUI for Java. For other GUIs and
external applications, eCATT provides an interface for external tools. The tool can be used with the Test
Workbench and is also integrated with the Object Navigator (transaction SE80).
Features
● Test transactions, reports, and scenarios
● Call BAPIs and function modules
● Test remote systems
● Check authorizations in user profiles
● Test updates of database, applications, and GUI
● Test the effect of modifications on customizing settings
● Check system messages
SAP Test Acceleration and Optimization (SAP TAO)
SAP Test Acceleration and Optimization is completely integrated into SAP Solution Manager and supports you n
automating your business process tests. It allows you to quickly generate automatic tests during regression
testing of SAP solutions.
You can create drafts of test cases, test components from transaction screens, and parametrize. These single
transaction tests can be combined into a scenario test. Due to the modular test case approach, it is easier to
manage potential modifications of your software that need to be considered in your test case. With SAP TAO, you
can set up your tests based on generated modular test components and therefore significantly facilitate the
maintenance of your test cases.
Recommendation
To build automated regression tests, it is strongly recommended to deploy SAP Test Acceleration and
Optimization (SAP TAO) in conjunction with SAP Quality Center by HP.
Note
SAP TAO is shipped on a license-based cost model.
128
Introduction
Table 18: SAP TAO Features
Feature
Description
Test Creation
You can easily record and execute tests. To build tests, you
can use the default components of SAP TAO. The subject
matter expert (SME) needs less time to explain the business
process to QA experts.
Regeneration of Components Affected
You can regenerate any number of components whenever
there is a change to the business process.
Test Consolidation
To speed up the test execution, you can consolidate a test into
a component and use it in a scenario test.
Test Execution
You can execute multiple tests at the same time in SAP Qual
ity Center You can also create or update technical bills of ma
terial (TBOM) for associated SAP Solution Manager items.
SAP Quality Center by HP
The SAP Solution Manager adapter for SAP Quality Center by HP supports role-specific testing and covers the
complete testing process, from collecting the requirements to defining the test case and reporting. This
infrastructure is therefore easy for customers to implement and use, as it follows the typical testing process for
SAP solutions.
Using the adapter, customers can seamlessly transfer information about business processes and test assets,
Business Blueprint structures and test objects for example, from the SAP Solution Manager to SAP Quality Center
by HP. SAP Quality Center by HP is the main testing environment for the customers' quality teams.
Once the test is complete, the test results are transferred from SAP Quality Center by HP directly o SAP Solution
Manager, automatically displaying the results of the predefined tests. This helps project leads to gain increased
control over testing processes and allows customers to reuse this information during subsequent application
management phases, for example upgrades or continuous business improvement projects.
This integration allows the functional experts to trace the status of the business process test in the SAP Solution
Manager, while quality experts continue working in SAP Quality Center by HP.
Business Process Change Analyzer (BPCA)
With the Business Process Change Analyzer you can identify business processes or business process steps that
are affected by planned change events. It is available in the Work Center Test Management of SAP Solution
Manager.
The underlying technology of BPCA is the Technical Bill of Material (TBOM). A TBOM is a list of ABAP objects
assigned to a transaction as part of your business process documentation, that is a record of all the inventories
related to a transaction. Particularly, a TBOM is created by recording the transaction code.
BPCA analyzes the change impact and identifies the potential impact on your existing business processes. The
purpose of this application is to identify core business processes that are affected by a change event such as a
custom code change, or an SP or EHP upgrade. This is done by comparing the TBOM, which lists the SAP objects
Introduction
129
that are used when business processes are executed, with the detailed information about the objects affected by
a change event.
Related Information
SAP Service Marketplace: Application Lifecycle Management Processes - Test Management
Component Based Test Automation
Component-Based Test Automation (CBTA)
Recording a Test Script Using Component-Based Test Automation
SCN: CBTA
extended Computer Aided Test Tool (eCATT)
eCATT: extended Computer Aided Test Tool (BC-TWB-TST-ECA)
Use that link to get a step-by-step introduction to eCATT.
SAP TAO
SAP Test Acceleration and Optimization
For more information and access to the Configuration and Administrators Guide on SAP TAO, follow this link.
For more information about compatibility questions, refer to the Compatibility Matrix available on SAP Service
Marketplace, by clicking the link above and choosing
Important Links
Compatibility Matrix .
SAP TAO - SAP Notes
SAP Note 1778083: Central entry point for release and upgrade information
SAP Note 1774967: Related to SAP TAO 3.0 configuration
SAP Quality Center by HP
SAP Solution Manager Adapter for SAP Quality Center by HP
Business Process Change Analyzer (BPCA)
Business Process Change Analyzer How-to guide
Business Process Change Analyzer (BPCA) - SAP Notes
SOLMAN 7.1 BPCA: Prerequisites for TBOM recording
FAQ: BPCA - Business Process Change Analyzer
1.4.5.5
Recommendations for Testing
To reduce the need for new test cases to be created, you can limit the project scope of the SAP Business Suite
powered by SAP HANA migration. One of the main goals of your migration project is to achieve satisfactory
overall performance while keeping the application stable. Be aware that the more functional enhancements, new
or changed business process requirements, or system landscape consolidation topics you add to the project
scope, the more complex and more costly your testing becomes. Business testing needs to cover all relevant
process areas. The main drivers are usually the following: Order to Cash, Accounting/R2R, P2P, and Controlling.
130
Introduction
Integrity Checks
To compare the results of any DB and SAP HANA DB, add integrity checks to your test activities for the most
relevant tables (50+ tables) .
● Check if the row count results of SAP tables are identical in SAP HANA and in the classic DB
● Calculate the hash totals and run a comparison
● Check if table structures on SAP HANA DB have been converted correctly into the column store format
Performance Tests
● To quantify the system performance, measure the runtime of your core business processes in the productive
system before starting the SAP HANA performance tests.
Note
Bear in mind that the system load can vary during daily operation hours. All test cases should be executed
several times and at different times of the day.
● Carefully plan when to execute which tests.
Recommendation
We recommend running performance tests in an exclusive mode, as the results could be influenced by
mass load tests.
Load Test - CRM on SAP HANA
Test Description
The aim of the load test was to create a massive BDoc load on the CRM middleware. To achieve this, more than
100 online users created more than 1000 BDocs per hour. The background jobs ran parallel too, while the main
ones ran during peak hours, like in the productive system .
Test Result
The test showed that the required load of 150% of BSP and E-Shop requests was achieved for the simulated
scenarios. The number of generated BDocs and RFC calls through the CRM middleware from ERP system also
provided 100% of the load that was expected during peak hours in the productive CRM system.
The CPU utilization showed no bottleneck situations on the CRM ABAP instance during any tests.
Based on the hourly average CPU utilization of 65%, the estimation is that the system could manage even 50%
more middleware load and 50% more online users.
Introduction
131
1.5
Run
● Monitoring the operational status and the most important key performance indicators of the database on a
regular basis ensures the smooth operation of your SAP HANA systems.
● Regular backups keep your data safe and make recovery possible
● The framework and functions provided by SAP HANA can be used to implement specific security and
compliance policies. The security needs of current and future business applications are met with a rich set of
authorization mechanisms.
● You can consistently optimize your ABAP custom code, and redesign and optimize individual business
process cycles
● Transports are used to deploy software components or objects across various landscapes, for example from
development to quality to production.
1.5.1
Monitoring
● To ensure the smooth operation of your SAP HANA systems, it is important to monitor the operational status
and the most important key performance indicators of the database on a regular basis.
● For monitoring purposes, both SAP and third-party tools can be used. Each of the tools has its own appeal
and advantages. These range from being able to display server activities in isolation to the offer of a solution
to the problem - the root cause analysis.
Monitoring SAP HANA DB
To ensure the smooth operation of your SAP HANA systems, it is important to monitor the operational status and
the most important key performance indicators of the database on a regular basis. These include system
availability, memory usage, CPU consumption, disk usage and alerts. To monitor these indicators, you can use the
monitoring tools listed below, as well as various views in the SAP HANA database.
● For system availability, the complete HANA architecture including the name server, index server, statistics
server, preprocessor and SAP HANA XS is monitored.
● The statistics server reports alerts for the system when resource usage of database and statistical thresholds
are violated. These are displayed as Low, Medium or High priority.
132
Introduction
● Disk usage monitors the amount of memory on the disk and the memory available for storing data files for
SAP HANA.
● Memory usage is a critical SAP HANA resource. The memory pool is used for storing in-memory tables, for
thread stacks, and for temporary computations, intermediate results and other data structures.
For more information, see SAP HANA Memory Usage Explained.
To monitor used memory, you can use the monitoring tools listed below, as well as various views in the SAP
HANA database.
Monitoring SAP HANA Systems
To ensure the smooth running of your SAP HANA systems, it is important to monitor system availability and key
performance indicators regularly. The SAP HANA studio includes several tools for monitoring your systems:
● System Monitor: This editor provides you with an overview of all your SAP HANA systems at a glance,
including system availability and current resource usage information. From the System Monitor you can drill
down into each individual system in the Administration editor.
● Monitoring Dashboard: This Web-browser based view visualizes key aspects of system health and
configuration on a single screen with the option to drill down to more detailed views.
● Administration: This editor provides detailed information about resource usage, current alerts, system
performance, system configuration, as well as tools for analyzing and troubleshooting issues in your system.
Introduction
133
Related Information
Introduction - SAP HANA in Data Centers
DBA Cockpit for SAP HANA
SAP HANA Memory Usage Explained
SAP Community Network:
SAP Application Operations
BI Monitoring
SAP HANA Platform SPS 06:
SAP HANA Administration Guide
SAP HANA Technical Operations Manual
1.5.1.1
Monitoring Tools
System Monitor
The System Monitor is an editor that provides you with an overview of all your SAP HANA systems at a glance.
From the System Monitor, you can drill down into the details of an individual system in the Administration editor.
To see all information for all systems, you must have either the MONITORING role or the system privilege CATALOG
READ and the object privilege SELECT on the schema _SYS_STATISTICS.
Monitoring Dashboard
The Monitoring Dashboard visualizes key aspects of system health and configuration on a single screen with the
option to drill down to more detailed views.
The SAP HANA studio includes a Web browser-based dashboard that visualizes key aspects of system health and
configuration, such as current high and medium priority alerts, memory and CPU usage, availability of data
backups, and so on. From the dashboard, you can drill down to views containing more detailed information.
134
Introduction
To be able to access the Monitoring Dashboard, you must have the role
sap.hana.admin.roles::Monitoring. This role is not granted by default to the standard MONITORING role.
Therefore, a user administrator must grant the role to your user explicitly. To grant this role, a user administrator
requires the object privilege EXECUTE on the procedure GRANT_ACTIVATED_ROLE, in addition to the system
privilege USER ADMIN.
Administration Editor
To identify problems early and avoid disruptions, you need to monitor your systems continuously. While the
System Monitor provides you with an overview of all systems at a glance, the Administration editor allows you to
drill down into the details of resource usage and performance for each system.
In the Administration editor, you can monitor the following:
● Overall system state and resource usage by system and host
● Status and resource usage of all system components, for example, name server, index server, and so on
● Auto-failover status and configuration of hosts in distributed systems
● Alerts issued by the system in relation to its status, performance, and resource consumption
Introduction
135
● Disk space consumed by system processes for the various storage types (data, log, and trace)
● System performance, for example, by analyzing performance indicators such as expensive statements,
running threads, and load history
To open the Administration editor with read-only access to the system views and alert information, you must have
either the MONITORING role or the system privilege CATALOG READ and the object privilege SELECT on the
schema _SYS_STATISTICS.
1.5.1.2
Monitoring Options
You can monitor the SAP HANA database with SAP HANA Studio, DBA Cockpit, SAP Solution Manager, thirdparty tools, or SAP NW LVM.
Monitoring with SAP HANA Studio
One way of monitoring is using the SAP HANA Studio. As the Studio is part of the SAP HANA Appliance, no extra
licenses are required.
For a quick overview, you can use the System Monitor. This can be used to monitor system availability and the
operational status of the SAP HANA system. Defined alerts inform the user critical situations on the database. The
SAP HANA Studio also provides information about memory consumption of SAP HANA, CPU usage, disk usage,
status of system replication, session monitoring, display information of individual steps of statement execution
(most expensive statements for example) and much more. The statistics server is the basis for the SAP HANA
Studio and provide historic monitoring data. SAP HANA Studio can be used to define thresholds for when a
system status should be reported as critical.
136
Introduction
Monitoring with DBA Cockpit
To monitor the database, you can also use DBA Cockpit, which retrieves the alerts from the SAP HANA database.
In DBA Cockpit, all of the main monitoring functionalities in the SAP HANA Studio are supported. The statistics
server is also the basis of DBA Cockpit and provides historical monitoring data. DBA Cockpit can be used to define
thresholds for when a system status is reported as critical. DBA Cockpit is part of SAP Basis. No extra licenses are
required. The system administrator might need to grant authorizations for this tool.
Monitoring with SAP Solution Manager
SAP Solution Manager provides another option for monitoring the SAP HANA database and the layers above.
Solution Manager communicates with HANA via the host agent and the diagnostic agent. Alerts are read from
HANA here and passed on to Solution Manager.
Solution Manager can be used to define thresholds. A threshold defines the point at which a system status is
shown as critical. SAP Solution Manager also provides an automated regular status check of your SAP solutions:
SAP Early Watch Alert (EWA). This tool monitors the essential administrative areas of SAP components and keeps
you up to date on their performance and stability. To facilitate quicker problem solving, a root cause analysis is
also provided. A part of the root cause analysis is the End-to-End Analysis. Starting with the application and
ending on the database level, issues can be isolated and identified by using this analysis type.
If you have a maintenance contract with SAP, SAP Solution Manager can be used without a license.
Monitoring with Third-Party Tools and SAP Solution Manager
SAP Solution Manager can also be used in combination with third-party monitoring tools. Solution Manager then
serves as a “relay station” for monitoring information for external monitoring tools. This is an interesting
alternative if the company in question already uses monitoring tools, but these tools cannot access SAP HANA.
There is no interface certification for HANA monitoring. The documented SQL interface can be used. For more
information, see the document SAP HANA SQL and System Views References linked below.
Introduction
137
Third-Party Tools with Direct Access
Alternatively, third-party monitoring tools can access the SAP HANA database directly in order to retrieve and
process alerts.
Monitoring with SAP Landscape Virtualization Management
Another option for monitoring the system status is SAP Landscape Virtualization Management. This makes it
possible to monitor running HANA processes and the entire application server as well. Operational activities such
as server start and server stop are possible, too.
In Enterprise Edition, dashboards can configured which provide a visual overview of all basic activities, such as
status of the SAP instances, servers, validations and performance graphics, for example the server’s CPU load.
Unlike Enterprise Edition, Standard Edition is license free.
138
Introduction
The graphic below provides you with an example of SAP Landscape Virtualization Management:
Related Information
Monitoring with SAP HANA Studio
For more information, see chapter Working with the SAP HANA Studio.
Monitoring with DBA Cockpit
HANA Supportability and Monitoring
DBA Cockpit for SAP HANA: Authorizations
Diagnostics and System Information with DBA Cockpit
Monitoring with SAP Solution Manager
SAP Solution Manager
End-to-End Analysis Overview
Monitoring with Third-Party Tools
SAP HANA SQL and System Views References
Introduction
139
1.5.1.3
Operations Control Center (OCC)
The Operations Control Center is a central IT support entity at the customer site that proactively monitors the
whole SAP environment (important non-SAP applications can also be included.
The OCC collects technical (application operations) and functional (business process operations) monitoring
information IT landscape components and business processes.
Recommendation
We recommend that you set up a physical room within the IT Support organization to view the exceptions and
alerts on large screens.
The following figure illustrates the general concept of an OCC:
1.5.1.4
SAP Offerings
SAP Service Offerings
SAP Data Technology Services (operation services) offers a portfolio of services for the entire operation lifecycle
– starting from the operation strategy definition to running operations and carrying out continuous
improvements.
140
Introduction
The following graphic illustrates the operational lifecycle:
Table 19:
Service Parameter
Components
Volume
Language
Location
Service Time
Introduction
Description
●
SAP runs SAP best – we can provide you expert SAP sup
port services.
●
Depending on your requirements, we can support you in
all of the SAP HANA components that you use or only in
selected ones.
●
Our SAP Application Management Service (AMS) is deliv
ered by shared pool resources, which means you only pay
for what you use and not for idle time.
●
Nevertheless, we provide named resources that know
your system and landscape by heart.
●
Our network of SAP support specialists spans he globe.
●
Therefore, we can support you in multiple languages.
●
Our standard support language is English.
●
Both AMS and Remote Application Operations (RAO) are
typically delivered from our Remote Delivery Centers –
which gives you a cost benefit compared to on-site deliv
ery.
●
Depending on your needs, we can also design a model
with on-site resources that are combined with remote re
sources.
●
Even in a remote model, our consultants can come to
your locations for special activities.
●
SAP expert resources are at your service during the
agreed service time, for example, Monday to Friday 8:00
a.m. to 6:00 p.m. CET.
●
For special activities like patches or upgrades, special
availability can be arranged.
141
Service Parameter
Service Level Agreements (SLAs)
Description
●
During the service time, we will provide you with a first re
sponse within an agreed time frame, which depends on
ticket priority.
●
Other SLAs can be discussed.
There are two service types depending on the region:
1. Application Management Service (AMS) and Remote Application Operations (RAO)
2. Remote Service for Database Operations (RDO)
The RDO Service is scoped by the number and type of existing servers that the client ants to have supported.
For all servers identified as in scope, RDO provides:
○ Monitoring and Alerting
○ Problem Resolution
○ Proactive Performance Management
○ Software Infrastructure Maintenance
SAP Training Offerings
● SAP HA200 - SAP HANA Installation and Operations
● SM100 - SAP Solution Manager Configuration for Operations
● E2E100 - End-to-End Root Cause Analysis
● E2E120 - Technical Monitoring in SAP Solution Manager 7.1
● PDEF75 - SAP Landscape Virtualization Management (LVM)
142
Introduction
1.5.2
Backup and Restore
● Plan regular backups of your SAP HANA database.
● You can use a number of strategies and tools to perform your backups.
● Re-importing a backup is known as recovering.
● There are also a number of ways to perform a recovery.
● Security is an important consideration when backing up and recovering data.
Database Backup
All SAP Business Suite objects are saved in the underlying database. It is therefore important to perform regular
backups of your database, to protect the system against data loss.
If necessary, you can back up all SAP Business Suite files and subfolders, including configuration files and log files,
at operating system level..
The backup and restore concept of the database for your system landscape should not only consider SAP
systems. It should be embedded in the overall business requirements and take into account the whole process
flow in your company. The backup interval depends on the way the Business Suite is used. For example, you can
create a full backup of the database every week. All changes since the last backup (that is, the transaction log of
the database) are backed up at more frequent intervals. The interval also depends on how quickly you need to be
able to recover a backup. If the number of log backups to be recovered is very high, the time required to perform
this recovery increases significantly since more log information needs to be rolled forward.
Ensure that the backup files are written to separate devices, to prevent a loss due to hardware failure. You also
need to monitor the space at file level to ensure that there is sufficient space for the data backup and the log
backup. In addition to backing up the data segment and the log segment, back up the configuration files. After
planning and setting up a backup mechanism, we recommend that you test the restore scenario. This ensures
that the importing of a backup works correctly.
You can create a backup in a number of different ways, using established backup strategies:
● Backup using Scheduling with DBA Cockpit
For more information, see DBA Planning Calendar.
● Backup using Shell and SQL Scripting in combination with OS-based Scheduling and hdbsql
● Ad-hoc backup with SAP HANA Studio
For more information, see SAP HANA Administration Guide.
● Using the BACK INT interface and third-party tools
For more information about certified tools, see SAP Partner Center.
Database Copy
You can create a homogenous copy of a database by recovering an existing source database backup to a
different, but compatible, target database.
Introduction
143
A homogenous database copy is a quick way to set up cloned systems, for example, for training, testing, and
development. For this reason, copying a database can significantly reduce total cost of delivery (TCD).
Note
It is planned to introduce a database cloning feature in SAP Landscape Virtualization Management Software
(LVM).
Database Recovery
It is recommended that you use SAP HANA studio to perform a recovery. We recommend that you create a new
full backup at the earliest opportunity after the database recovery.
It may be necessary to recover the SAP HANA database in the following situations:
● A disk in the data area is unusable.
● A disk in the log area is unusable.
● As a consequence of a logical error, the database needs to be reset to its state at a particular point in time.
● You want to create a copy of the database.
When restoring the database, you first define the recovery variant that you want to use. The system then checks
whether all required backup files, including log files, exist. Only once this check has been performed does the
system start to recover the database by importing the selected full backup and the log segments.
Possible Recovery Types
● Recover the database to its most recent state
● Recover the database to the next point in time
● Recover the database to a specific data backup
● Recover the database to the next log position
Related Information
Introduction - SAP HANA in Data Centers
SAP HANA Technical Operations Manual
Education:
SAP HA200: SAP HANA Installation and Operations
Database Backup
HANA Supportability and Monitoring
For more information about running a backup using Scheduling with DBA Cockpit, see this PDF file.
DBA Planning Calendar
144
Introduction
For more information about running a backup with SAP HANA Studio, see chapter Working with the SAP HANA
Studio in the SAP HANA administration guide.
SAP Partner Information Center
Via BACK INT interface and third-party tools:
To find an overview of the certified tools (including version information), go to the SAP Partner Information
Center, and choose SAP Certified - Integration with SAP HANA in the Certification Category field and HANA-BRINT
1.1 in the SAP-Defined Integration Scenarios field.
SAP Notes:
SAP Note 1730932: Using backup tools with Backint for HANA
SAP Note 1730928: Using external software in a HANA appliance
For more information about third-party backup tools, see these SAP Notes.
Database Copy
For more information, see the section Copying a Database Using Backup and Recovery of chapter Backing Up and
Recovering the SAP HANA Database in the SAP HANA administration guide.
1.5.2.1
User Authorizations
To back up or restore the SAP HANA database, you need specific user authorizations the database level.
To perform a backup a recovery, the following authorizations are required:
Table 20:
Task Type
Required Authorization
Back
To perform backups, you must have the following system priv
ileges:
●
BACKUP ADMIN or BACKUP OPERATOR
●
CATALOG READ
This privilege is required collect the information needed
by the backup wizard.
Recover
Open the Backup editor
Delete data and log backups from the backup catalog and
The recovery process is executed as the operating system
user (<sid>adm). You must therefore have the logon creden
tials of this user.
●
BACKUP ADMIN
●
CATALOG READ
●
BACKUP ADMIN
physically from the backup location.
The system privileges BACKUP ADMIN and BACKUP OPERATOR exist so you can implement a finer-grained
separation of duties if this is necessary in your organization.
A user with the system privilege BACKUP ADMIN can perform all backup-related operations, including backup
deletion and configuration. A user with the system privilege BACKUP OPERATOR can only perform backups.
Introduction
145
Example
For example, if you have automated the regular performance of backups using on, it is more secure to use a
user with the privilege BACKUP OPERATOR to avoid the malicious deletion of backups.
1.5.3
Security
● SAP HANA provides a framework and functions that can be used to implement specific security and
compliance policies.
● The integration with your security network and data center infrastructures is enabled with standard interface
support.
● The security needs of current and future business applications are met with a rich set of authorization
mechanisms based on standard SQL privileges and SAP HANA-specific extensions.
● SAP HANA is used in different scenarios that require different security approaches. The architecture of the
scenario determines the security approach.
The Importance of Security
As it becomes increasingly important for organizations to protect their critical data from unauthorized access and
to ensure compliance with a growing number of rules and regulations, the demands on security are also
increasing. As an in-memory computing platform that supports multiple implementation scenarios and use cases
– from traditional relational databases underneath SAP applications to the platform for development and
deployment of innovative new applications – SAP HANA can play an important part in critical IT and application
infrastructures.
It is therefore essential that you integrate SAP HANA into your infrastructure securely and protect your data in
SAP HANA.
Differences of SAP HANA Security Concept Towards Other SAP Solutions
SAP HANA has a very similar concept to other SAP solutions, for example you have roles, users, and
authorizations. Therefore the general approach is the same as before and you can continue to use your security
strategy.
There are differences in the details like what type of authorizations are available and tools. The security
requirements and measures heavily depend on the scenario in which the SAP HANA application is operated. When
SAP HANA is used as a database of an SAP application, the same security approach applies and specific SAP
HANA security features are mainly needed to control access of administrators to the database.
146
Introduction
Security Functions
Depending on the scenario in which SAP HANA is used, only some of these functions might actually be needed.
Others might be provided in other architecture layers.
The security functions overview is illustrated in the graphic below:
Table 21:
Authentication/SSO
SAP HANA offers various authentication methods:
●
For SQL access:
1.
User name and password (incl. password policy)
2. Kerberos
3. SAML 2.0
●
For HTTP access (via SAP HANA XS):
1.
User name and password (incl. password policy)
2. SAP logon tickets
3. SAML 2.0
4. X.509
Introduction
147
Identity Store
Authorization
Encryption
Audit Logging
148
For logon, users must exist in the identity store of the SAP
HANA database
●
Roles (and privileges) can be assigned to users.
●
Roles are used to bundle and structure privileges. Role hi
erarchies are supported.
●
Roles can be created in the repository during design time.
This makes it possible to export and import roles using
repository functions. The user and role management of
SAP HANA XS is fully integrated with the core database
user and role management.
SAP HANA provides a rich set of authorization mechanisms
based on standard SQL privileges and SAP HANA-specific ex
tensions to meet the needs of current and future business ap
plications. All access to data and execution of actions in the
database require authorization: Privileges control what users
can do.
●
System privileges: Authorize execution of administrative
actions for the entire SAP HANA database
●
SQL privileges: Authorize access to data and operations
on database objects
●
Analytic privileges: Authorize read access on analytic
views at runtime, provide row-level access control based
on dimensions of the respective view
●
Package privileges: Authorize access in the repository
(modeling environment) at design time
●
Application privileges: Authorize access to SAP HANA
XS application functions
SAP HANA can encrypt this persistent storage (the data vol
umes on disk), which ensures that users cannot see the actual
content even if they can access the data volumes on disk us
ing operating system commands. SAP HANA offers various
encryption methods
●
Communication encryption based on SSL
●
Data volume encryption on disk
Audit logging tracks actions performed in the database: who
did what – or tried to do what – and when. SAP HANA offers
logging of critical events for security and compliance. These
include
●
User, role, and privilege changes
●
Configuration changes
●
Read and write access (tables, views), execution of pro
cedures
●
The audit trail written to OS SYSLOG. Audit logging can
be configured in the SAP HANA studio or using SQL
statements. Audit policies define which actions in the da
tabase are logged, such as audit target and audited
users. These policies can be configured to the customer’s
needs.
Introduction
Security Administration
SAP HANA offers security administration with
●
SAP HANA Studio
●
SQL interface (command line tool hdbsql)
Related Information
SAP Help Portal page of SAP HANA Platform: Security Information
SAP Help Portal page of SAP ERP: Security Information
SAP Notes:
SAP Note 1598623: SAP HANA appliance software: Central Security Note
SAP Note 1730928: Using external software in a HANA appliance
SAP Note 1730929: Using external tools in an SAP HANA appliance
SAP Note 1730930: Using antivirus software in an SAP HANA appliance
SAP Note 1730932: Using backup tools with Backint
SAP Note 1730999: Configuration changes in HANA appliance
SAP Note 1730996: Unrecommended external software and software versions
SAP Note 1730997: Unrecommended versions of antivirus software
SAP Note 1730998: Unrecommended versions of backup tools
SAP Note 1731000: Unrecommended configuration changes
Introduction
149
1.5.3.1
Data Center Integration
SAP HANA supports standard interfaces to enable integration with customer security network and data center
infrastructures.
The figure below illustrates the security infrastructure of SAP HANA and is followed by an explanation:
● Identity management (user and role provisioning)
○ SQL-based interface for user and role creation
○ Out-of-the-box connector for SAP Identity Management is available
● Compliance infrastructure
○ Out-of the box connector for SAP Access Control is available
● Standard-based single sign-on infrastructures based on Kerberos, for example Microsoft Active Directory
SAML
● Logging and monitoring infrastructures
○ Database audit trail written to Linux syslog
Operating System
SAP HANA comes with SE Linux Enterprise (SLES) 11 pre-installed and preconfigured. is already includes
preconfigured security settings, such as minimal network services running. To conform with internal and external
IT policies, customers n make certain changes or additions to the standard SAP HANA appliance installation. The
details are described in SAP Notes.
150
Introduction
Security Patches
SAP HANA security patch information is published as part of the general SAP security patch strategy (SAP
Security Notes). SAP HANA security patches are delivered as SAP HANA revisions and can be applied using the
Software Update Manager for SAP HANA. Operating system security patches are provided and published by
SUSE.
Network
Recommendation
It is recommended that you operate the SAP HANA appliance in separate network zones.
Recommendation
To prevent unauthorized access to the SAP HANA appliance and the SAP HANA database through the network,
we recommend the application of network firewall technology to create network zones for the different
components and to restrictively filter the traffic between these zones implementing a minimum required
communication approach.
The network communication channels, such as purpose and ports, used by SAP HANA are documented in detail
in the SAP HANA master guide. The SAP HANA security guide includes recommendations on the use of firewalls,
for example to separate internal and external communication as well as the options for encryption using SSL. A
reference for the SAP HANA network protocol is also available.
Compliance Infrastructure
Compliance plays an important role in many customer environments. SAP HANA provides functions that support
customers in achieving compliance.
Compliance in most cases is not a product feature, but depends on many factors such as:
● Relevant rules and regulations such as IT policies, industry, and country
● Existing technology and infrastructure, processes, and audit approach
To achieve compliance, usually both process and functional requirements need to be fulfilled:
● Best practices in security operations
● Need-to-know principle, separation of duties all levels
● Control of privileged access
● Ability to audit
● Deletion of data
SAP HANA takes an end-to-end approach to enable application compliance, the basis for which is provided by the
built-in database security features and the security options of the whole software and hardware stack. This is
extended by the integration of SAP HANA into existing security infrastructures through standard or documented
Introduction
151
interfaces and the option to use third-party tools that are required for data center operations. customers can
implement their specific security and compliance policies based on the security provided by SAP HANA, .
1.5.3.2
Security Scenarios
SAP HANA can serve two purposes relation to SAP Business Suite wered by SAP HANA. It n serve as the database
for SAP Business Suite applications, and it n serve as the database for SAP HANA Live analytics for SAP Business
Suite. When being used for SAP HANA Live, the database can be shared with the SAP Business Suite application
ith ittle or no data replication, or it can be installed in a sidecar manner, where data is replicated from the SAP
Business Suite system to a separate SAP HANA database for SAP HANA Live.
SAP HANA as Database for SAP Business Suite
In this architecture, a three-tier application, security management features such as authentication, authorization,
encryption, and audit logging are located and enforced mostly in the application server layer, while the database is
used only as the data store
Applications connect to the database through a technical user account, and direct access to the database is only
possible for database administrators. End users do not have direct access to either the database itself or the
database server on which it is running. As a consequence, security in the database layer is mainly focused on
securing administrative access to the database.
For access from SAP Business Suite:
● The same security model as with other databases applies for user access.
● Security functions of SAP NetWeaver ABAP or SAP NetWeaver JAVA still apply.
○ Application server connects with technical database user to SAP HANA database
○ Authorization management is as before with existing methods
○ User management is performed in the application server
● SAP HANA security functions are used to manage administrative access to the database.
152
Introduction
SAP HANA Live for SAP Business Suite
Individual users directly access the SAP HANA database sing the SQL protocol, for example to consume reports,
view dashboards, or to use SAP BusinessObjects Business Intelligence solutions. Therefore, all security functions
of SAP HANA, for example, for user management, authentication, privilege management and authorization check,
encryption of communication channels and of data, and security logging, are used to secure access.
SAP HANA Live for SAP Business Suite supports direct access to SAP ERP data in SAP HANA.
● ERP data is exposed through analytical views as rtual data models.
○ Virtual data models can be used by the customer to create new views.
○ Virtual data models can be exposed, for example through SQL or TP, and consumed by different clients,
such as the browseror reporting tools.
○ SAP HANA Live can be used in a sidecar approach using replicated data or in an integrated approach.
● Each SAP HANA Live user gets a database user.
● Authorization check occurs within SAP HANA using privileges.
● Creation of SAP HANA authorizations can use a tool that allows the creation of authorizations directly in the
SAP HANA tudio based on the ABAP roles already defined in the profile generator of SAP Business Suite
(transaction code PFCG).
○ Analytics Authorization Assistant
Introduction
153
1.5.3.3
FAQs: Security
This topic answers frequently asked questions regarding security aspects of SAP Business Suite powered by SAP
HANA.
Will all existing SAP Business Suite ABAP users e migrated with the correct authorizations after an SAP
HANA tabase migration
Absolutely – The migration of an SAP ERP database to SAP HANA is a full database migration.
Will the user administration in SAP ERP on SAP HANA change and how does this impact our security team?
All SAP ERP users and roles are defined through the SAP ERP application layer. The only change is for the users of
the SAP HANA data modeling studio in the SAP HANA data mart, and his also applies to SAP HANA Live.
Recommendation
recommend that you train the security team in SAP HANA. There are specific technical training urses available.
Is the authorization for SAP HANA Live re similar to the SAP ERP on SAP HANA security model or to the SAP
HANA data mart security model?
154
Introduction
The user privileges in the SAP HANA security model are currently less granular than authorizations in the
application layers for SAP BW powered by SAP HANA and for SAP Business Suite powered by SAP HANA. For
SAP HANA Live, the SAP HANA-based analytical privileges are used with each analytics user becoming a
database user. The privileges of the database user are then verified when accessing SAP HANA Live objects.
Does SAP provide a tool to migrate SAP Business Suite application users' privileges to SAP HANA Live
authorizations?
The SAP HANA Live Authorization Assistant provides an authorization tool that generates analytic privileges and
corresponding roles of the selected SAP ABAP user. The assistant is available as an Eclipse plug-in for the SAP
HANA udio.
The assistant reduces manual effort sing a semi-automated generation, which the users’ SAP ABAP
authorizations are transformed to SAP HANA analytic privileges.
Related Information
SAP HANA Live Authorization Assistant
1.5.4
Optimization
● Consistently optimize your ABAP custom code - whereas different options, such as Open SQL, Vies, Native
SQL, as well as stored procedures can be used
● Redesign and optimize individual business process cycles due to higher agility in data analytics and because
real-time insights can be used to push real-time actions
Performance Optimization
SAP HANA is the real-time platform for accelerated enterprise applications. Porting your SAP Business Suite
system to SAP HANA means first itching to In-Memory DB, which improves database times.
With the optimization of SAP Business Suite powered by SAP HANA you want to use the full potential of the SAP
HANA platform innovations.
The starting point of the optimization is to consistently optimize your ABAP custom code. Open SQL is compatible
with AnyDB and is used to optimize existing queries without any additional operation impact. With views and
Native SQL you use native SAP HANA functionality to optimize data access. Stored procedures allow you to push
Introduction
155
down business application logic from the SAP Business Suite application layer into the SAP HANA database.
Using stored procedures, parallelized queries, and advanced view modeling results in:
● Improvement of database and application times
● ewer lines of code
● Reduced data traffic between layers
● Less main memory required for the application
The section Code Migration and Optimization, linked in the information section, describes the steps that are
required to optimize the custom code from the execution of the code assessment to the classified ABC worklist of
the prioritized technical objects and the execution of the code optimization. The main goal is to speed up
dedicated transactions and to reduce the overall cycle time of the core business processes.
Redesign and Optimization of Business Processes
SAP HANA enables you to execute Online Analytical Processing (OLAP) and Online Transactional Processing
(OLTP) on one platform and therefore opens the door for new individual business processes on your SAP
Business Suite system.
There is no need for data duplication, data aggregation, or index programming anymore. For example, SAP HANA
Live provides you with the semantic layer of a Virtual Data Model (VDM) to run analytics in realime. From insight
to action means that, based on real-time reporting and analysis executed directly in-memory, you can execute
transactions in realime. With SAP HANA your processes gain agility, you can think about real-time planning, realtime simulation, and real-time interactions. Optimizing SAP Business Suite powered by SAP HANA brings value
for IT, business, and people and requires the involvement of fferent parties. SAP Business Transformation
Services (BTS) and services of SAP Active Global Support can help you to leverage the full the potential of SAP
HANA.
The following table shows some examples of how SAP HANA can be used to optimize your business processes.
You can, for example, blur the boundaries between OLAP and OLTP, replace batch processes, and go without
aggregation and index programming.
Table 22:
From
To
Problems
Value
Pre-aggregated
On-the-fly aggre
gation
Data available in a
predefined aggre
gation is not suffi
cient for deep anal
ysis. Data analysis
projects are initi
ated to more pre
cisely understand
situations.
Flexibility: Slice
and dice informa
tion for highest
How to Find
With SAP HANA
Blurring the boun
daries between
OLAP and OLTP
relevance
Insight to action:
Closed loop analy
sis and process ex
ecution
156
Introduction
From
To
Problems
Value
How to Find
With SAP HANA
Once in a batch
window
When needed
Some batches can
be executed only in
particular batch
windows. This trig
gers processes de
lays.
pdate information
on an aseeded ba
sisto drive proc
esses earlier and at
higher accuracy
while reducing buf
fers.
Check critical
batch runs for rele
vance of more fre
quent updates.
Replacing batch
processes: For ex
ample, more fre
quent use of billing
run improves cash
flow
Stage gate for
process changes
Management deci
sion
Processes changes Check programs
Some process
can be applied on
changes require a
that reorganize
recalculation of ag an as-needed basis data.
gregates and in
dexes. Therefore,
the process can be
changed only if
there is enough to
recalculate the
data basis.
Precalculation
On-the fly calcula
tion
Large amounts of
data are precalcu
lated for reference
by end users even
No aggregation or
index program
ming: For example,
rebate processing
in SD
New data will drive Where you precal
the process with
culate information
out updating the
information matrix.
Responsiveness:
For example, pric
ing, calculation of a
pricing matrix
Drive automation
and new processes
through usage of
new types of data.
New processes:
if not needed to
achieve high per
formance during
user interaction.
Recalculation af
fects performance
and establishes the
reality as at the
start of the calcula
tion.
Bits and Bytes
Information
New types of data:
for example, M2M,
sensor data, and
RFID, is increas
ingly collected but
not yet tied into
processes in SAP
Business Suite.
For example, en
ergy management,
predictive mainte
nance, predictive
QM
Related Information
Code Migration and Optimization [page 96]
Introduction
157
1.5.5
Transport Management
● Transports are used to deploy software components or objects across various landscapes, from development
to quality to production for example.
● SAP HANA deployments can be carried out using various methods:
○ CTS+
○ Application Lifecycle Manager
○ SAP HANA Lifecycle Manager
○ SAP HANA XS
Transport
In integrated system landscapes, it is important to manage all changes in a central system. This is the only way to
synchronously execute changes that affect more than one production system.
If you use SAP HANA application-specific accelerators like CO-PA for example, in combination with your SAP ERP
back end, you might need to synchronize changes to the data models on SAP HANA with changes for accessing
the changed models from transactions on SAP ERP. SAP Solution Manager provides central transport functions
for the entire system landscape and additional support for quality management.
The graphic below illustrates the process of transporting changes and is followed by an explanation:
The process for transporting changes from a SAP HANA development system to a quality assurance and o the
productive system starts in SAP HANA Studio. You retrieve content from the SAP HANA source system there and
export it to enhanced Change and Transport System (CTS+) in SAP Solution Manager. The exported delivery
units are automatically attached to a transport request of CTS+. Once you have released this transport request,
158
Introduction
CTS+ triggers the automatic activation of the change in the SAP HANA repository on the target system, such as
quality assurance or production.
As well as supporting the transport and activation of new or changed data models, views, stored procedures, or
analytic privileges, SAP Solution Manager offers additional possibilities for improving the quality of changes. You
can use change analysis and reporting to obtain information about the current status and history of changes.
Configuration validation checks if the systems of your system landscape, such as development, quality assurance,
and production, are configured consistently and in accordance with the requirements. Quality Gate Management
provides an additional quality inspection for projects and ensures that changes are transported correctly and
synchronously to the production systems. Change Request Management within SAP Solution Manager controls
the entire change execution with detailed process and workflow control. From these options, you can select the
ones for controlling changes on SAP HANA that are best suited to your organization's quality strategy.
CTS is the standard Change and Transport System for SAP ABAP systems. SAP HANA repository content can be
packaged within delivery units. These delivery units can be captured insides and ABAP transport object, called
SAP HANA transport container. These SAP HANA transport containers can be transported via the standard ABAP
CTS.
Transport Scenarios for SAP HANA
There are a number of different transport scenarios for SAP HANA content, depending on how SAP HANA content
is used. You can use the HANA Transport Container (HTC) to transport SAP HANA content for ABAP for SAP
HANA applications. Otherwise, you can use the enhanced Change and Transport System or SAP HANA
Application Lifecycle Management to transport SAP HANA content for native SAP HANA applications.
SAP HANA content refers to SAP HANA development objects that are created in SAP HANA-based development
projects. SAP HANA content is not part of the SAP HANA database installation itself. It is stored in the repository
of the SAP HANA appliance software and can include different objects, such as schemas and table definitions,
information views (attribute views and analysis views), SQL scripts, or roles and authorizations.
A typical system landscape for SAP HANA development consists of a development system, a quality assurance
system, and a production system. To transport SAP HANA development objects from a system to a successor
system, there are a number of transport scenarios available. The transport scenario that is suitable for your
situation depends on the way the SAP HANA content is used that you want to be transported, and on your system
landscape.
Introduction
159
The concept described above is depicted in the following figure:
Native SAP HANA Content
Content for native SAP HANA applications is SAP HANA content that is developed exclusively for SAP HANA
systems. You can use the enhanced Change and Transport System (CTS+) to transport SAP HANA content for
native SAP HANA applications, or for non-ABAP applications that are based on SAP HANA. It is particularly wellsuited to heterogeneous transport landscapes in which CTS+ is already in use. From an administrative point of
view, the SAP HANA content is another object type that can be transported with the CTS in the same way as other
non-ABAP objects. The effort required for configuration is low, and the transport tools are already familiar. In
particular, you can use CTS+ if you want to transport SAP HANA content as part of an SAP solution (such as SAP
BI, Mobile, and so on), since in this case, you often need to create a link between the SAP HANA content and other
non-ABAP development objects and non-HANA development objects.
This transport scenario is integrated into the existing CTS transport landscape and into the SAP tools for change
control (Change Request Management and Quality Gate Management of the SAP Solution Manager) the transport
is performed in the same way as for any other non-ABAP application that is integrated into CTS+.
SAP HANA Content for Native SAP HANA Applications
If CTS+ is not in use, you can use SAP HANA Application Lifecycle Management to transport SAP HANA content
for native SAP HANA applications. You can use SAP HANA Application Lifecycle Management to perform
transports and monitor transport processes.
SAP HANA Application Lifecycle Management is particularly well-suited to SAP HANA transport landscapes with
no ABAP development (without CTS+) and with no requirement for synchronizing transports with other nonHANA content.
160
Introduction
SAP HANA Content for ABAP for SAP HANA Applications
SAP HANA content for ABAP for SAP HANA applications is usually transported together with ABAP objects
because the development objects are closely-connected in terms of content. You can use the HANA Transport
Container (HTC) to transport this SAP HANA content. The HTC is a logical transport object that is transported
with the standard ABAP transport tools. An HTC always contains all SAP HANA repository objects of a delivery
unit. The HTC is attached to a standard ABAP-transport request and transported together with the associated
ABAP objects. When the transport request is imported into the target system:
● The ABAP objects in the transport request (including the HTC) are imported into the ABAP system.
● The SAP HANA repository objects in the DU are imported into the SAP HANA repository. The import is
performed with or without activation, depending on the system settings of the associated ABAP software
component of the HTC.
This transport scenario is integrated into the existing CTS transport landscape and into the SAP tools for change
control (Change Request Management and Quality Gate Management of the SAP Solution Manager).
SAP HANA Lifecycle Management and SAP HANA XS
Starting with SAP HANA SPS 6, SAP HANA introduced Application Lifecycle Manager (ALM). This new tool is
made available with SAP HANA udio. It enables you to manage, replicate, and transport SAP HANA development
components.
SAP HANA ALM is an XS application automatically installed as part of the SAP HANA database server. A
document offering a full comparison of ALM and CTS+ can be found here:
HANA Application Lifecycle Management Setup & How It Compares to SAP CTS+ Integration
Additionally, SAP HANA XS can be used to transport components directly between SAP HANA systems by using a
tool called XS Lifecycle Manager (HLM).
The following points provide you with guidelines on the best way to transport and manage content between
systems or your specific situation:
● You should use CTS+ when:
○ Your SAP environment is made up of many SAP systems and you have an established change process
around ABAP transports
○ Your SAP environment already includes CTS+ for transporting non-ABAP related objects such as Portal,
PI, or SLD
○ Your SAP changes are managed by SAP Solution Manager Change Request Management (ChaRM)
● You should use CTS when:
○ You expect your SAP HANA content to be managed by a separate dedicated group of people who have no
responsibility or knowledge of your other SAP systems
○ Your landscape does not have other SAP systems (ABAP or Java).
○ Your SAP landscape has many ABAP systems but you do not have any Java systems for implementation
of CTS+
Introduction
161
Related Information
Further Reading Material on Transport Scenarios for SAP HANA
Resources on CTS+
Implementing Lifecycle Management
(see section 12)
How to transport ABAP for SAP HANA applications with HTC
SAP HANA Application Lifecycle Management
162
Introduction
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
Important Disclaimers and Legal Information
163
www.sap.com/contactsap
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

SAP Business Suite powered by SAP HANA Cookbook

Transcription

Similar documents

Formerly, Zygen Technology

Efficient project management – Although employees are

Supply Chain Through Mobility

High Voltage Maintenance

SAP Predictice Analytics Roadmap

Deloitte`s Journey from Analytics to S/4 HANA

SAP Enhanced Warehouse Management Project

success in furniture retail

From Business Warehouse to BI and Analytics : Bell Helicopter`s

MDS ap Corporate Brochure