ITM230 – Data Migration to

SAP S/4HANA with SAP Landscape

Transformation

Public
Speakers

Las Vegas, Oct 19 – 23 Barcelona, Nov 10 - 12

 Jochen Merkel  Jochen Merkel

 Roland Hamm  Roland Hamm

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Agenda

SAP S/4HANA - Architecture and deployment options

SAP S/4HANA – Data migration options
SAP LT supported SAP S/4HANA data migration scenarios
 Characteristics of SAP S/4HANA landscape transformation projects
 SAP LT as SAP S/4HANA data migration platform – Overview
 „Lab Preview“: File upload to SAP S/4HANA, cloud edition
 Details on SAP S/4HANA landscape transformation scenarios (On premise)
 Development roadmap & outlook
SAP S/4HANA - Data migration service map

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 4

SAP S/4HANA - Architecture
and deployment options

Public
SAP S/4HANA
Our next-generation business suite

SAP S/4HANA Enterprise Management is

SAP’s next-generation Digital Core
 Innovative in-memory Database
 New architecture and data models
 Renewed applications
 New UI technology
 Cloud & on-premise deployment models
 Natively integrated

SAP S/4HANA is a new product line.

The classical SAP Business Suite & SAP ERP is a separate product line and will still be available.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 6

High level stack architecture SAP S/4HANA
Logical view

SAP S/4HANA architecture

differs from the classical
Business Suite architecture
 Data structures
 Compatibility provided through
Core Data Services
 Application engines
 Launchpad / SAP Fiori
 SAPGUI for Windows still
available for compatibility reasons

This is the current state of planning and may be changed by SAP at any time.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 7

SAP S/4HANA architecture
Table consolidation
Logistics Logistics Material Ledger Accounting
(Quantities) (Valuation via „MBEW) (multi GAAP, multi currency)
GLPCT
MARD
MBEW
Business Suite
QBEW Totals
COSP ZZFISLT
Totals
MARC CKMLPP CKMLCR COSS FAGLFLEXT
OBEW OBEW
MSPR
MSTQ COFIT GLFUNCT

MSLB Index
MSTE

Totals MSTB CKMI1 BSIS BSIT BSIK BSID BSIM

MSLBH
MSKU Totals
MSTQH
MSSQ BSAS BSAT BSAK BSAD
MSKA
MSKUH
MSTEH MSSA MKOL MBEWH
MSTBH MSKAH QBEWH
MCHB Indices
MSSQH MKOLH Document BKPF GLPCA
OBEWH OBEWH MLHD MLIT BSEG ZZFISLA
MCHBH MKPF Documents
MSSAH
MLPP MLCR FAGLFLEXA
MSPRH MARDH
MSEG MLPPF COBK GLFUNCA
MLCRF
MARCH ANEK
Document
COEP COFIS
ANEP

Logistics Material Ledger

S/4HANA

Master Data Accounting

(Quantities) (multi GAAP, multi currency)

Material MATDOC Material BKPF ACDOCA

Prices

SIMPLE DATA MODEL SIMPLE PROCESSES THROUGHPUT INCREASE

» 4 tables remaining, no redundancies » Only one valuation method (Material Ledger) » INSERT only on database level
instead of 2 (IM + ML)
» Clear separation of master data from transactional data » No locks for standard price valuation
» Reduction of memory footprint
© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 8
SAP S/4HANA
One code line, different products

Following the “principle of one”, SAP S/4HANA will offer all main features* in different
deployment options

Development SAP S/4HANA

On-premise Edition
SAP S/4HANA
Dev.
Consolidation

SAP S/4HANA
Cloud Edition

Selected
corrections

Classical
Suite

*Detailed product features may differ in

different deployment options

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 9

 TheSAP
The S/4HANA Family
S/4HANA andand
family Migration Paths
transition paths

SAP Business Suite SAP S/4HANA family

(e.g. BS7i2013) SAP
S/4HANA
Cloud edition

SAP CRM Landscape Transformation

On-Premise (data migration based on New implementation
SAP LT capabilties) (based on Software Provisioning Manager)

SAP SCM
On-Premise SAP Simple Finance
SAP S/4HANA
oP Edition 1503 On-premise Edition
SAP
Business Suite System Conversion
AnyDB
On-Premise
SAP ERP
SAP ERP on HANA
On-Premise On-Premise New implementation
(based on Software Provisioning Manager)

Landscape Transformation
(data migration based on
SAP LT capabilities)

System Conversion
(based on Software Update Manager)

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 10

SAP S/4HANA – Data migration
options

Public
Transition to SAP S/4HANA
The 3 transition scenarios

On-Premise  Example: New or existing SAP customer

ERP System
New
implementing a new SAP S/4HANA system
Implementation Non-SAP with initial data load
System
S/4Cloud

System  Example: Complete conversion of an

ERP System On-Premise
Conversion existing SAP Business Suite system to SAP
S/4HANA
S/4HANA

ERP System
- Region A - On-Premise
 Example: Consolidation of current regional
Landscape
ERP System SAP Business Suite landscape or selective
Transformation - Region B -
data transformation into one global SAP
ERP System S/4Cloud S/4HANA system
- Region C -

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 12

Transition to SAP S/4HANA
Scenario 1 – New installation

Scenario description
New installation of SAP S/4HANA e.g. for SAP S/4HANA SAP S/4HANA
customers migrating a legacy system. SAP ERP 6.0 or On-premise Edition Cloud Edition
higher

Option: Initial data load SAP Fiori

from Legacy or SAP
system based on SAP
SAP S/4HANA Core
Non-SAP LT capabilities

Legacy SAP HANA

Any customers
Benefits for the customer legacy system
+ Reengineering and process simplification
based on ready-to-run business processes
and reference solution delivered with the What How
product
+ New implementation of industry-leading 1 Install S/4HANA SWPM (Software Provisioning Manager)
Business Suite
SAP Landscape Transformation
+ Pre-defined migration objects & Best Initial data load from • SAP source: system connection
Practices available in a guided process 2 source system • Legacy system: file upload;
SAP Data Services additionally supported

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 13

Transition to SAP S/4HANA
Scenario 3 – Landscape transformation

Scenario description
Customers who want to consolidate their SAP S/4HANA SAP S/4HANA
landscape or to selectively transform data On-premise Edition Cloud Edition

into a SAP S/4HANA system. Consolidation or selective

data transformation based
on SAP LT capabilities (SAP GUI) / SAP Fiori

SAP S/4HANA Core

Benefits
SAP HANA
+ Value-based migration: selective data
transformation allows a phased approach
focusing the first SAP S/4HANA migration
phase on parts of the business with highest
ROI and lowest TCI What How
+ Agility: stay on current business processes SAP Landscape Transformation
but move gradually to SAP S/4HANA 1 Consolidation Consolidate clients from different source systems into one new or
existing SAP S/4HANA system (build-up multiple client system)
innovations (Move to SAP S/4HANA at your
own pace!) SAP Landscape Transformation
2 Selective Data Transformation • Migration of business units/single entities such as company code
+ TCO reduction: system and landscape • Migration of selected SAP applications (example: central Finance)
consolidation with harmonized/ simplified
processes and unified master data lead to
lower cost of operations

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 14

Transition to SAP S/4HANA
Major elements of deploy phase in transition process

1 2 3

Preparation Technical Implementation Semantical Adoption

Preparation steps on start release
 Analysis of used business processes –
mapping to SAP S/4HANA innovations
 Identify required integration scenarios of
target state
 Run pre-Transformation Checks on source
system
 Used functionality, supported industries, available
add-on, custom code …
 Mandatory preparation steps to be executed
on source system.
 “Installation” of SAP S/4HANA
o SAP HANA Database
o SAP S/4HANA application core
 Customizing adjustments
 Adjustment of technical
infrastructure
 Adapt custom code to comply with SAP
S/4HANA scope & data structure
 Adapt business / processes to leverage
new SAP S/4HANA innovation
functionality
(e.g. use CDS-based real-time reporting
instead of Logistics Information System)
 Adapt integration scenarios (if applicable)
 Implement SAP Fiori UIs
 Introduce new SAP S/4HANA
innovation scenarios (e.g. advanced
planning and simulation features)

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 15

SAP LT supported
SAP S/4HANA data migration
scenarios

Public
SAP S/4HANA landscape Transformation Project(s)
Characteristics
In General
 SAP S/4HANA landscape transformation approach has to be set-up as a project with IT and business users involved

 CIOs are usually the sponsor and initiates TCO driven Landscape transformation project(s)

 Business responsible usually decide on the scope and timing of a value-based / selective data transformation project

Due the different availability of the SAP S/4HANA applications and various business reasons driving such a decision, business
responsible and IT need to set-up a holistic SAP S/4HANA transition roadmap and jointly identify SAP S/4HANA landscape
transformation opportunities.

Special technical considerations:

 Due to architectural changes in several ERP applications, a preliminary assessment needs to evaluate the readiness for a SAP S/4HANA
landscape transformation project -> several prerequisites apply or preparation steps may be required

 SAP provides predefined „migration content“ for dedicated landscape transformation scenarios –> however several project-specific
configuration steps, technical checks and adjustments required

The SAP Landscape transformation approach is not

a „turn-key“ solution similar to the system conversion approach

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 17

Transition to SAP S/4HANA
Required capabilities of a SAP S/4HANA data migration platform

Ability to analyze and check readiness of On-Premise

ERP System 1
New System source environment for SAP S/4HANA
Installation Non-SAP
landscape transformation scenario(s)
System
Configuration options to meet customer-
2
specific requirements and system Cloud
conditions
• Configuration based on pre-defined
transformation content
• Mapping capabilities and ability to define
System “transformation rules”

Conversion Flexible & high-speed data selection and

3
processing
• Performance tuning options for data transfer
• Support of required data transfer methods (such
as file upload, posting via standard interfaces or
ERP System table-based insert)
- Region A - • Data validation and reconciliation features On-Premise
Landscape
ERP System Compliance to post processing programs
Transformation - Region B - 4
for the semantical adoption to SAP
S/4HANA
ERP System Cloud
- Region C -

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 18

SAP Landscape Transformation
SAP S/4HANA data migration / landscape transformation platform

Source Environment Target Environment

SAP S/4HANA
On-premise Edition

Preconfigured transformation content Insert of data via

for SAP S/4HANA, cloud edition
standard interfaces

Process Control
LAN / WAN and table-based
Transformation & Analysis Object-based Transformation
1
Framework Business object-based data transfer

Insert of data via

Transformation Engines
(Migration, Conversion, Replication) standard interfaces
(BAPIs / Direct Input)
(new implementation)
File Upload

SAP MWB
Non-SAP
SAP S/4HANA
Legacy
Cloud Edition
Any customers
legacy system

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 19

„Lab preview“: SAP S/4HANA embedded – Migration cockpit
SAP S/4HANA, cloud edition (file upload)
1. Select Migrate your data from Guided Configuration menu 3. Generate file template for selected migration objects

2. Identify relevant migration objects 4. Start and monitor data migration process

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 20

SAP S/4HANA landscape transformation scenarios – On premise
SAP LT enabled solutions

Consolidation Migration of Business Units Migration of selected applications

(Company Code) (centralFinance)
Pre-configured

Tailored offerings for selective data migration requirements

(for example based on time slice, plant or other objects)
can be requested as project solution or service.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 21

Possible consolidation scenarios
Greenfield
“start from scratch”
Systems to be merged won„t be
in operative use afterwards.
A new system with a new
organizational structures and
processes will be created.
In case of a „selective“ migration
access to source systems for
historical information is required.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Brownfield
“Pick up best scenarios
within company”
Systems to be merged won„t be
in operative use afterwards.
A new system with a new
organizational structures but
existing processes will be
created.
In case of a „selective“ migration
access to source systems for
historical information is required.
Blackfield
“pure technical n to 1”
One system will be identified as
„leading“ system, others will be
merged into that.
All existing processes and
organizational structures will be
adjusted in case of conflicts.
In general all data will be
migrated.
Public 22
Possible consolidation scenarios

Greenfield Brownfield Blackfield

“start from scratch” “Pick up best scenarios “pure technical n to 1”

within company”

Systems to be merged won„t be
in operative use afterwards.
A new system with a new
organizational structures and
processes will be created.
In case of a „selective“ migration
access to source systems for
historical information is required.
Systems to be merged won„t be
in operative use afterwards.
A new system with a new
organizational structures but
existing processes will be
created.
In case of a „selective“ migration
access to source systems for
Reliability
historical information is required.
One system will be identified as
„leading“ system, others will be
merged into that.
All existing processes and
organizational structures will be
adjusted in case of conflicts.
In general all data will be
migrated.
on project duration

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 23

SAP S/4HANA landscape transformation scenarios – On premise
Consolidation

Motivation & Typical Use Cases Current scope and important considerations:
Reduce number of SAP systems by consolidating into one SAP S/4HANA: • Supporting data transfer from single clients to build-up a multi client SAP
S/4HANA system
• SAP solutions: ERP, CRM, SRM , SCM, PLM
• Post migration activities required to adjust transferred data in SAP S/4HANA
• SAP BW consolidation / SAP HCM consolidation
system (similar in system conversion)
Note: Migration into an existing SAP S/4HANA system/client is currently not
-> TCO reduction and process and data harmonization as additional value possible
proposition for the a SAP S/4HANA business case

Prepare Explore Realize / Deploy

It depends 6-10 weeks 8-10 weeks 16-20 weeks 2 weeks

• xxx
The preparation steps of
S/4HANA landscape
transformation projects are
similar as of any other
S/4HANA transition scenario
(New implementation or
system conversion)
The duration of the
preparation phase highly
depends on the applications
currently in use of the SAP
Business Suite and the
architectural impact of the
S/4HANA simplification
System comparison Implementation
 Customizing / Repository / Number ranges  Customizing harmonization
 Applications and related business objects in  Repository harmonization
use (Refactoring)
 System information: release, DB version. data  Number range concept
volume, etc.  Identify and close application
& process related gaps
Identify most suitable consolidation option
(and required services)  System & infrastructure setup
 Selective data load / migration
Define high-level project plan
 Data validation - IT
Quality Cycles & Dress Rehearsal Cutover & GoLive
 System & infrastructure setup  System & infrastructure setup
 Full data load / migration  Final data transfer
 Runtime estimation/optimization (in confirmed downtime)
 Data validation - IT  Data validation - IT
 Integration testing
 Integration testing (customer / key
(customer / key users)
users)
 Reconciliation according to concept  Final sign-off & hand-over
 Sign-off
 Cut-over preparation
(confirmation for downtime window,
agree- ment on communication
guidelines, etc.)

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 24

SAP Landscape Transformation - Outlook
SAP S/4HANA data migration / Landscape transformation platform

Source Environment Target Environment

SAP S/4HANA

Automated validation of the migration results

Preconfigured Validation Content On-premise Edition

Validation Framework
Preconfigured transformation content Insert of data via

Process Control
for S/4HANA, on-premise/cloud edition
standard interfaces
LAN / WAN and table-based
Transformation & Analysis Object Based Transformation
1
Framework Business object-based data transfer

Transformation Engines Insert of data via

(Migration, Conversion, Replication) standard interfaces
(BAPIs / Direct Input)
(new implementation)

Near Zero Downtime

File Upload

SAP MWB
Enabling Near-Zero-Downtime capabilities for source system

Non-SAP
SAP S/4HANA
Legacy Cloud Edition
Any customers
legacy system

Engine Content Next generation features

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 25
SAP S/4HANA related development roadmap

Transformation Platform Capabilities Landscape Transformation Scenarios (On Premise)

• Integrate LT posting capabilities closer with Consolidation

SAP S/4HANA and other LT platform
components • One step system / client merge of SAP Business Suite into SAP S/4HANA

SAP S/4HANA • Optimize use of LT based posting capabilities

Cloud Edition for SAP S/4HANA as target
• Investigate in alternatives / advanced Migration of Business Unit
solutions to replace file upload (for non-SAP
& legacy systems) • Complete development for a company code transfer (incl. merge) into an existing
SAP S/4HANA system / client
• Investigate in more automated checks to
assess SAP S/4HANA readiness in source
environment
Migration of selected applications
SAP S/4HANA • Integrate Validation Framework closer with
other LT platform components and develop • Improve central Finance specific aspects
On-premise Edition
content for automated validation / • Investigate in SAP S/4HANA Logistics specific migration aspects
reconciliation
• Investigate in suitable performance
optimization options based on NZDT
• Extend and optimize LT platform for key SAP
S/4HANA landscape transformation scenarios

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 26

Expected transformation content for SAP S/4HANA, cloud edition
Transfer of master / Transactional data
SAP S/4HANA
Cloud Edition
Project Services Edition - 1511: 20 Enterprise Edition - 1603: 44
Migration Objects Migration Objects

Activity Prices Inventory Balances Secondary Cost Elements Purchasing Info Records Standard hierarchy Functional Locations Open deliveries

Activity Type Groups Material Master Characteristic Master Inspection Methods Profit Centers Bank Master Routings

Planned independents Master Inspection

Activity Types Class Master Cost Centers Fixed Assets SD Pricing
requirements Characteristics

Bank Master Profit Center Groups Activity Types Inspection Plans Exchange Rates Functional Location Inventory Balances

Business Partner (CVI,

Profit Centers Activity Prices Bill of Materials Object Dependencies Purchasing Requisitions
Cust & Vend)

Business Partner (CVI,

Cost Center Group Purchase Order Service Master Sales Orders Contracts
Cust & Vend)

Accounts
Cost Centers Purchasing requisitions Material Master Purchase Orders Scheduling agreements
Payable/Receivable

Credit Memo Sales Order Material Classification Work Centers Internal Order Reference operation set

Material QM Inspection
Customer Invoice Billing Statistical Key figures Service Master Source List Order reservation
Type

Material External Work Breakdown Planned independents

Fixed Assets Supplier Invoice Equipment NOTE: The number of available objects
Customer Replenishment Structure requirements
may be different for on-premise edition

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 27

SAP S/4HANA – Data migration
service map

Public
SAP S/4HANA migration services
Offering from SAP Active Global Support and Consulting

Optional
For the E2E Solution Per System / Change-Cluster
Pre-Step

2 Scenario Decision 4
Innovation Strategy & Roadmap
1 New Implementation
Business Target Strategic Migration
SAP S/4HANA Scenario Architecture Roadmap Scenario
Discovery System Conversion Planning
& & & Implementation
Workshop Solution Platform Business Landscape Incl. Readiness
Mapping Strategy Case Transformation Check

2a
SAP S/4HANA
Implementation Strategy

3
Technical Architecture & Infrastructure

Prepare Explore Realize/Deploy

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 29

SAP S/4HANA – Landscape transformation services at a glance

SAP S/4HANA landscape transformation – Strategy Advisory & Roadmap Service

• Assess readiness of source environment for SAP S/4HANA landscape transformation approach

• Define SAP S/4HANA landscape transformation roadmap, incl. recommendations such as

 program / project plan (with effort estimation, timelines)

 most suitable technical solution approach (with related prerequisites and constraints)

SAP S/4HANA Landscape Transformation – Implementation Services for Consolidation and

selective data transformation scenarios
• Analyze and prepare affected source systems (e.g. release level, impact of applications in use, need for repository and customizing
harmonization, etc.)

• Determine affected data volume and possible measures for downtime optimization

• Technical execution (data migration), incl. testing and verification based on reconciliation lists

• Cut over and GoLive support

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 30

SAP TechEd Online
Continue your SAP TechEd education after the event!

 Access replays of keynotes, Demo Jam, SAP TechEd live interviews, select lecture sessions, and more!
 Hands-on replays

http://sapteched.com/online

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 31

Further Information

Related SAP TechEd sessions:

TEC114 - Transition paths to SAP S/4HANA
DMM213 - SAP S/4HANA Data Migration Deep Dive: The Right Path to Simple (New Implementation)
ITM201 - How to Plan and Execute the System Conversion to SAP S/4HANA (System Conversion)
ITM200 - How to Plan and Execute a Migration to SAP HANA (System Conversion)
SAP Public Web
www.sap.com/s4hana
http://scn.sap.com/community/s4hana
http://scn.sap.com/docs/DOC-65072 -> SAP S/4HANA - Data Migration Options & Roadmap
http://support.sap.com/saplt
SAP Education and Certification Opportunities
www.sap.com/education
….
Watch SAP TechEd Online
www.sapteched.com/online

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 32

Feedback
Please complete your session evaluation for
ITM230

©©2015
2015
SAP
SAP
SESE
oror
anan
SAP
SAP
affiliate
affiliate
company.
company.
AllAll
rights
rights
reserved.
reserved. Public 3333
Thank you
Contact information:

Jochen Merkel
Chief Product Owner – AGS SLO

SAP SE, Walldorf - Germany

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 34

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

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.

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. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

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 SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE‟s or its affiliated companies‟ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 35