SAP S/4 HANA Session

July 17, 2015

2014 IBM Corporation

Introduction and
Consulting Perspective- Why it Matters and Why
Now?

Bill Piotrowski

2
Agenda
Welcome: Bill Piotrowski
Consulting Perspective- Why it Matters and Why Now?: Bill Piotrowski
What is S/4HANA and Demo of Benefit Areas: Craig Rich and Michael Bergbauer
Simple Finance (Features and Differences): Ambuj Garg
Migration Path/Considerations: KJ Min
Deployment Models/Technical Considerations: Rocky Singh
Q&A: All
Why S/4 HANA Matters to our Clients, GBS and our
People
Business benefits for companies who adopt SAPs
S/4 HANA and Simple Finance as an enterprise
resource planning (ERP) foundational solution for
their business operations:
Less redundant data
Less reconciliation effort
Better user experience with Fiori
Simplified master data
Transaction processing and analytics together
Real time analytics
Better system performance
Accelerated financial close
As consultants, we must be prepared to have a point of view
regarding S/4 implementation strategies and options balancing ability
to execute and completeness of vision.
The purpose of todays session is to provide each of you with the
insight you need to provide this balanced advice to our clients.
Client Opportunities
Develop business case for migrating from ECC to
Existing SAP Install
Base
S/4
Demonstrate S/4 Proofs of concept, leveraging
LSS
Tailor
S/4 is roadmaps
ready now -for S/4
must bemigration options
recommended for all net new
Net New SAP For Greenfield SAP implementations, enable your client
Implementations
to leap frog their competition.
Risk averse/short timeframe companies an option to
implement S/4 and then migrate to Simple Finance and/or
Simple Logistics in the future.
4
 So why now?
S/4 is the future and the future is now.
The technology shift from ECC to S/4 is as significant as the shift from the mainframe SAP R/2 solution to the client
server SAP R/3 solution in the early 1990s.
Immediate opportunity since many companies chose not to migrate their ERP to Suite on Hana due to:
Focus on BW to Hana migration
Were waiting to better understand the business benefits of HANA beyond system performance improvement.
Imagine being able to render the maximum amount of information to a single users fingertips through analytical
insight, master data and transactional processing at the same time this is possible with S/4..
Employee roles are transformed, employee effectiveness is maximized, data entry clerks turn into knowledge
workers (e.g. customer service clerk can see customer profitability on same screen during collections call)
To re-imagine the roles of our clients employees, we must reinvent the art of the possible. As leaders in our SAP
business and in this industry, we must break out of our comfort zone, retool ourselves and our teams, and encourage
innovation focused recommendations to our clients.

We have the experience and its happening quickly

GBS has two S/4HANA / Simple Finance projects underway (Schlumberger, Kennametal), dozens of Suite on Hana
migrations and 100s of successful BW to Hana migrations
5
 S/4 can be a growth play for GBS
S/4HANA is an opportunity for our clients to simplify their business operations and to establish a platform for growth enabling digital
commerce, mobile and the shift to cloud computing. We are noticing that the energy and momentum generated during SAPPHIRE continues
to pose new growth opportunities for GBS - helping our clients navigate the S/4 decision journey.
Strengthening the GBS & SAP Relationship:
We are seeing S/4 as a meaningful reason to rekindle our long standing relationship with SAP at all levels. Clients need both
independent points of view on the potential of S/4 and how/when to implement.
Increased client interest in ERP on Cloud:
HANA is optimized to run on cloud also runs on premise. Our clients considering S/4 are also seriously considering cloud managed
services, especially for net new greenfield implementations.
Limited S/4 Talent in the marketplace:
Unique short term opportunity for GBS and our people to take the market as everyone is ramping up new skills.
SAP application support opportunities will also grow as clients realize it is too costly to attract and retain S/4 experienced talent
S/4 Implementation Strategic Planning:
Companies with an existing SAP install base and an existing application support provider oftentimes do not get thought leadership
from a pure play AMS firm.
Opportunity for the integrated GBS to provide thought leadership and help clients navigate the S/4 decision journey.

During todays call, challenge yourselves to find a way to discuss S/4 with your
clients tomorrow, and encourage your teams to make time to build these new skills.
6
What is S/4 HANA and Demo of Benefit Areas

Craig Rich and Michael

Bergbauer

7
 What is?
What is S/4HANA?
S/4HANA = Suite on HANA (ECC on HANA) + s-innovations, where currently available s-innovation is
Simple Finance 2.0. So until Q3/2015, S/4HANA = ECC on HANA + Simple Finance 2.0, and in Q4/2015,
S/4HANA = ECC on HANA + Simple Finance 3.0 + Simple Logistics 1.0.
What is Suite on HANA?
Business Suite (such as ECC, SCM, CRM and SRM compared to BW) running on HANA database as
opposed to traditional database such as Oracle and DB2.
What is Integration Strategy for Simple Finance with the rest of business functions?
Simple Finance runs on top of ECC on HANA and replaces only old Finance functions running on Classic
or New GL. All the other business functions are intact and already there, and no separate integration
strategy is needed
What is the roadmap for s-innovations?
The roadmap for s-innovations beyond Simple Finance 3.0 and Simple Logistics 1.0 is unclear. Next s-
innovation frequently mentioned is S_ERP, but there is no clarity around the scope of S_ERP, and it seems
more like generic term where Simple Innovation is applied to the areas other than Finance and Logistics. If
you have more information on this, please share with the team.

8
 Business Benefits
The speed of the HANA database and the simplification that Simple Finance brings are major
innovations. We must keep in mind though that the new technology is in essence an enabler for
much bigger and bolder innovations in Enterprise applications and especially in Finance.

9
 What is happening in my business right now?
Simple Finance directs the focus from the past to the present and the future.
How can we create new data in a more present oriented manner?
How do we store the newly created data more efficiently?
How do we report on the data in a timely manner?

10
 S/4HANA @ Kennametal
Kennametal Supplier of Tooling and Industrial Materials founded in 1938 with $3B Revenue
Mature SAP client since 1998 with recent reimplementation in 2010 with IBM
Fore-front of IT innovations and recognized by CIO Magazine's "CIO 100 Award" for second consecutive years
Pain Points - Complex Business Model resulting in complex Enterprise Structure, Profit Center Structure resulting in challenges

Generating Financial Statement for Business Units

Lack of Drill-Down Capability for analyzing Operational Issues
Product Costs by material, direct overhead, variable overhead, etc
Dynamic Product Cost Updates
Automatic Calculation of Unrealized Profit
Group Costs
Approach - Started Finance Optimization Initiative with S/4HANA to Optimize and Simplify Finance
Immediate Additional Business Benefits -
WIP calculation on production orders, Variance settlement into COPA, Cost Center assessments into COPA, Depreciation
Run, Actual Costing
Flying blind until the 3rd business day of the new month at Kennametal?
Future Innovative Vision
How does my result look right now?
What if we had a weekly or daily close of the books?
11
 Universal Journal & Line Item Reporting
What does it really mean to store all documents in one unified structure in one table?
Dramatically reduced reconciliation effort (no sub-ledgers, no aggregates, no
separation of OLTP and OLAP & reduced redundancy)
Flexibility: change of reporting structures (e.g. introduction of new dimension) much
easier because there are no pre-calculated aggregates
Maximum detail & total visibility of information (Outliers, Data Distribution,
Correlations are no longer hidden in aggregates and available for analysis)

12
 A new Reporting HANA Live, Fiori, Dash Boards
Forget Report Painter & ABAP reports, the future is HANA Live & Virtual Data
Models

Role based & personalized Apps with Fiori

Dash Boards with real time KPIs

13
 What might happen? New Frontier
Scenario Planning & Simulation & Prediction
What do these catch words mean in reality? Scenario analysis of fluctuating raw
material prices at Kennametal
Vision: Predicted Profitability for Manufacturing
Predicted Revenues
Predicted Cost of Goods Sold

14
 Vision: Future Oriented Actuals
New Category of Future Oriented Actuals between Actuals and Plan
based on non-financial information in the system

15
 Vision continued: Future Oriented Financial
Statement
Financial Statement includes Prediction of the Future in all dimensions

16
 Vision continued: Future Oriented COGS &
Profitability
Daily predicted raw material prices on material master
Daily Costing Run
Predicted COGS for semi-finished & finished goods on daily basis
Combine with prediction of sales quantities
Get rolling prediction of future profitability

17
 Demo with IBM S/4HANA Express Solution
Universal Journal Demonstrate CO account assignments in ACDOCA
No aggregates, Post an expense account, show entry in Universal Journal, and show
balance after posting
Optimized Transaction
FI Closing (Profit Center Allocation)
Asset Accounting (Depreciation Run)
IBM Express for SAP combines
CO Closing (Settlements, Result Analysis) the following sets of industry
Best Practices in a single
Appendix Ledger instance:
Industrial Machinery and
Components
Discrete Manufacturing
Fabricated Metals
Consumer Packaged Goods
Wholesale Distribution
High Tech Electronics and
Semiconductor/Photovoltaic
Human Capital Management
Contact; Craig Rich, KJ HANA Live, RDS and SAP Fiori
Min
18
Apps enabled
IBM developed S/4HANA
Simple Finance (Features and Differences)

Ambuj Garg

19
Key Features- What does Simple Finance Bring?
Simple and Faster
Single Source of Truth (Universal Journal)
Elimination of CO FI reconciliation
Accelerated Closing process

Innovation
Line item based Analytics provides flexibility in Reporting
Non Disruptive upgrade from New GL
Integrated Business Planning
Cash Management Powered by HANA

Improvement
Removal of redundant tables (Reduced Data Volume)
Reduction of Controlling Master Data
New Asset Accounting

Accessibility
20
Business Cockpits (Personalized Dashboard)
Simple Finance Value Proposition
Instant Insight
The new principle of ONE
Universal Journal Entry
One Chart of Account
Central Finance deployment
Leverage soft close
Better insight within the period
Accelerate hard close
21
Intuitive User Experience Non-disruptive
and Flexible
New look and feel with Fiori Non-disruptive
Traditional accounting transactions Migration Path
Analytical Accounting Apps Compatibility Views
Intuitive drill down reporting Flexibility
Balance Sheet and P&L Reporting Journal Entry is extensible
SAP ERP Traditional Finance vs SAP Simple Finance

Traditional Finance Simple Finance

22
Universal Journal

23
Universal Journal

24
Traditional SAP Architecture

Traditionally, SAP has stored GL, Customer, and Vendor balances and open item statuses in
a number of extra database tables in order to support reporting

Customer Vendor General Ledger Controlling

COSS
KNA1 LFA1 SKA1 COBK COEP
COSP
KNC1 LFC1 GLT0
Finance
Index Tables (i.e. Open Item Tracking)
BKPF BSEG BSIS BSID BSET BSIK BSAK BSAS BSAD

Legend:
Update
Insert

A vendor invoice with 3 accounting line items would update more than 10 tables at least 15 times!
25
Simplified Architecture with sFIN 2.0

Simple Finance 2.0 (powered by HANA) can achieve the same reporting directly from table
ACDOCA without the need to store balances or open item statuses separately

Customer Vendor
Vendor General Ledger Controlling

KNA1 LFA1 SKA1 COBK COEP

Finance

BKPF ACDOCA
Legend:
Update
Insert

The same vendor invoice in Simple Finance 2.0 would update at least 4 tables 5 times!
26
 Traditional Finance vs Simple Finance
Area of Traditional Finance Simple Finance
Difference
Change in Traditional SAP had Index and Totals tables The following Index Tables have been eliminated
Architecture GL-BSIS, BSAS, AR-BSID, BSAD, AP- BSIK, BSAK, New GL- FAGLBSIS,
FAGLBSAS
The Below Totals Tables have been eliminated
GL- GLT0, GLT1, GLT3, AR- KNC1, KNC3, AP- LFC1, LFC3, CO- COSP
COSS, New GL- FAGLFLEXT
Speed SAP had to update the Line items and Totals tables Only BKPF & ACDOCA tables are updated. The Update now is 3
for each document times Faster and the results for analytics are exponential
The Principle of 1 Traditionally there were Multiple Sources of Truth for Universal Journal Entry for Financial and Management accounting
Financial Accounting & Management Accounting
Master Data GL accounts, Primary and Secondary Cost elements Primary and Secondry Cost Elements are maintained in the GL
had to be separately maintained account itself.
Reconciliation Tedious FICO reconciliation process. A reconciliation CO-FI reconciation has been eliminated
document was posted each time
Parallel Valuations Leading Ledger posted in Real Time while the Non Both Leading and Non Leading Ledger posts in real time. This
Leading Ledger posted periodically avoids time consuming periodic Processing
Closing Process Traditionally The closing process was lengthy as These calculations have been pushed down to the HANA data base
complex calculations were performed at period close for an accelerated close
New Features Integrated Business Planning was not part of Cash Management and Integrated Business Planning powered by
Traditional Finanace HANA have been built in Simple Finance

27
Migration Path/Considerations

KJ Min

28
 S/4 HANA Migration Roadmap
1. System 2. Migration 3.
Prep and to Suite on Installation
Mini Close HANA of SFIN 2.0 4. Standard
Optimized
Transaction
6. SFIN 2.0 5. HANA- s
7. New
Asset Configuratio tization
Accounting n
Adjustment
s
9. Fiori 10. Go-Live Continuous
8. Migration to Improvemen
Universal Apps, HANA
Live and t in Steady
Journal State
Optimizatio
n

29
 Cost Drivers for S/4HANA Migration
1. Complexity of the Upgrade
a. Source System Version
b. OS & DB Upgrade Requirement
c. Level of Customization
d. Unicode Migration Required
e. Regression Testing Requirement
2. Size of the Database
a. Migration to Suite on HANA
b. Migration to Simple Finance Data Structure
c. Database specific features turned on

3. Business Downtime Window

a. Distribution vs. Industrial
b. # of Connected Apps and Interfaces
30 c. # of Trial Cut-overs to optimize the downtime
 Prep, Mini-close and Consistency Check
Period End-Closing Activities
Post all held documents in the system
Carry forward all previous Fiscal years for AA, A/P, A/R, GL
Close previous Fiscal Years in AA
Close AA current period (ASKB, AFAB,)
Lock periods in FI & CO to prevent any activity during Installation and Migration
Consistency Check
Consistency checks of the tables in G/L, AA, CO, ML
Check consistency of documents versus transaction figures & totals
Several reports to run and check for error

Snapshot of FI/CO/AA Data for post migration validation

Runs several reports used to compare the data after the migration
31
 Technical Migration Approach
Migration to Simple Finance involves two migrations:

1. Migration from Traditional DB to HANA DB

a. Upgrade to the latest version (for instance, ECC 6.0 EHP 7 SPS10)

b. Migrate from Traditional DB to HANA DB

2. Install SFIN 2.0 and Migrate to Simple Finance Data Model

Depending upon source release one step migration for 1 and 2 are available

32
SAP BSOH Upgrade and Migration
The database migration option (DMO) of Software Update Manager (SUM), which allows us
to reduce business downtime and risks compared to the classical procedure:

Upgrade and migration in a combined one procedure

Business Downtime is reduced compared to SWPM
Allows upgrade to the latest support packs for Fiori Apps

33
 Lessons Learned for Simple Finance 2.0 Migration
1. More than 200 OSS Notes manually deployed

2. Erroneous OSS Notes redeploying with newer versions and re-sequencing

3. Stay on the top of code corrections from SAP

4. Update HANA DB to the latest revision

5. HANA DB revision upgrade process changed

6. Latest SAP NetWeaver SPS version required for FIORI apps

7. Latest ERP 6 EhP7 SP version required

8. Documentation, documentation and documentation!

34
 What is HANA-tization?
Process of adjusting the ABAP objects (standard + custom) to avoid functional issues due
to migration to HANADB is called HANA-tization .

Without HANA-tization, many custom objects may not work properly.

There are 3 primary areas where HANA-tization is required

Technical Change
DB migration
SAP HANA architecture
ABAP code that must be checked/corrected
Native SQL, Hints, ADBC which uses DB specific features
Transparent DB Tables:
Relying on not guaranteed default sorting of DB content
Direct access and analysis of technical DB index information

Pool/Cluster Tables:
Relying on not guaranteed default sorting of DB content
Depooling/Declustering
Direct access of physical clusters/pools

35
 S/4HANA Best Practices
IBM has created Best Practices on Simple Finance 2.0 Migration in collaboration with SAP

IBM is working with SAP for upcoming s-innovations, namely, Simple Finance 3.0 and Simple
Logistics 1.0
Design review of Simple Finance 3.0 and Simple Logistics 1.0 in Q2/2015
Beta-testing of Simple Finance 3.0 and Simple Logistics 1.0 in Q3/2015

IBMs collaboration with SAP on this topic will benefit Kennametal in preparing for the next
phase after Simple Finance 2.0 migration

IBM will use S/4HANA Best Practices throughout the projects

IBM has a global community on S/4HANA which drives collaboration across all SOH and
36
S/4HANA projects, such as, Schlumberger, Cheney Bros and Carrefour
 Migration to SFIN 2.0

37
 Simple Finance 2.0 - Lessons Learned 1
# Risk
1 There is a set of customizing steps and checks, which
must be executed before technical installation of
Simple Finance. They could not be processed after the
installation of Simple Finance if they are forgotten or
neglected.
2 Technical problems during installation of Simple
Finance and migration to Simple Finance
3 Transfer prices or parallel valuations are used in
Controlling.
4 Shifted fiscal year and ledger approach are used in
new Asset accounting
5 There are add-ons used in the system not compatible
with Simple Finance
38
Root cause
Migration documentation for Simple Finance from SAP is split into
several documents (Administration guides, SAP Help, OSS notes), and
often not very consistent. We found some key steps are missing after
the migration and had to restore the database to correct the missing
steps. We have carefully documented these steps in IBM runbook.
Simple Finance has huge number of OSS notes (+200) with multiple
revisions and manual steps. We had to back out certain OSS notes to
correct the sequence of OSS notes, and carefully documented these
steps.
These are not yet supported in Simple Finance 2.0, and IBM worked
out workaround.
This functionality is supported limitedly with workaround solution.
IBM documented the add-ons that are incompatible with the Simple
Finance, and therefore will focus on mitigations plans
 Simple Finance 2.0 - Lessons Learned 2
# Risk Root cause
6 Functionality that is not compatible with Simple IBM documented the add-ons that are incompatible with the Simple
Finance is used Finance, and therefore will focus on mitigations plans

7 Values in financial reports are not reconciled before 1. Program errors in migration steps
and after migration 2. Not all pre-migration activities are executed
3. Inconsistent customizing before or after migration

8 Missed authorization for migration steps. This could 1. New authorization objects for migration activities
not only to authorization errors, but table and database 2. Execution of migration steps by the users with incorrect role
inconsistencies

9 Missing or restricted functionalities in Account based With Simple Finance 2.0 SAP is making the account based CO-PA as
CO-PA in comparison to Costing based CO-PA the core of Central Journal approach. Meanwhile it has functional
limitations, although there are some enhancements in Simple Finance

39
 S/4 HANA Migration Guide
IBM has collected past experience with S4HANA implementations in a detailed step by step Playbook.
Along with extensive SFIN 2.0 customizing documentation for G/L, CO and AA.
Phase of the migration / implementation
Steps within the phase & predecessor steps
Tools/programs/transactions necessary to complete the step
References to external sources / SAP notes / customizing documentation
Useful remarks/observations for the future
3.2 Data Migration Data Migration Migration of Cost Elements and X X CO MB Completed Application Consultant SPRO->SAP Simple Finance Add-On for SAP
Customizing Business Suite powered by SAP HANA-
>Migration->Migration of Cost Elements
and Customizing
3.3 Data Migration Data Migration Technical Check of Transaction Data X X FIN MB Completed Application Consultant SPRO->SAP Simple Finance add-on for SAP
Business Suite powered by SAP HANA-
>Migration->Technical Check of Transaction
Data
3.4 Data Migration Data Migration Migration - Enrichment of Data X X FIN MB Completed Application Consultant SPRO->SAP Simple Finance add-on for SAP
Business Suite powered by SAP HANA-
>Migration->Migration - Enrichment of Data

3.5 Data Migration Data Migration Migration of Documents and Line X X FIN MB Completed Application Consultant SPRO->SAP Simple Finance add-on for SAP
Items to the Data Structure Business Suite powered by SAP HANA-
>Migration->Migration of Line Items into
New Data Structure

3.6 Data Migration Data Migration Migration of Balances X X FIN MB Completed Application Consultant SPRO->SAP Simple Finance add-on for SAP
Business Suite powered by SAP HANA-
>Migration->Migration of Balances

40
 IBM Best Practice for S/4HANA Simple Finance 2.0
Migration

41
Deployment Models/Technical Considerations

Rocky Singh

42
Deployment Models/Technical Considerations

Rocky Singh

43
 SAP HANA Scenarios
Architectural Illustrations
HANA HANA HANA HANA BW on Business One Business Suite
apps for Suite Accelerators on Cloud HANA on HANA on HANA
Platform (inc. Reporting &
(Datamart) Analytics)
Client
Client Client SAP
Business
SAP
Suite

Apps
SAP

BW
Business One
ERP, CRM,
Business
Datamart SAP Apps SAP SCM
Suite SAP
Business Business OD/SF solutions BW SRM, PLM)
& any app Suite Suite Business
Suite

HANA DB HANA
Any DB HANA DB HANA DB HANA DB HANA DB HANA DB
MS DB
Any DB Any DB Any DB Any DB
SQL

HANA Offerings
Side-by-side (Side car) scenarios Integrated scenarios

HANA RDS
SAP HANA DB Sales analysis for CRM customer BW powered by Business One Business Suite on
Custom datamart/any retail segmentation Business HANA on HANA HANA
app Liquidity risk COPA Intelligence on Business planning & SAP Business HANA new analytics
BOBJ BI management Finance & demand consolidation on One Analytics
Visual Intelligence ERP operational controlling Sales & HANA on HANA New Applications
reporting operations HANA new Smart Meter Analytics
Text & predictive
Social sentiment planning analytics Precision retailing
analysis
intelligence Supplier InfoNet Cash
Sales pipeline Developer Access forecasting
analysis via Amazon Web
Standalone app from
Services (AWS)
partners
 Deployment Scenarios for S/4 HANA
Option 1: Greenfield Implementation Option 2: Upgrade and Migrate
(all instances, or optionally consolidate)
S/4 HANA
SAP ERP Simple
or Re-Implement Finance 2.0
(SAP ERP 6.0 SAP ERP Upgrade, S/4 HANA
SAP R/3 EhP7 on HANA) Simple
or Migrate & Finance 2.0
Or Non SAP SAP R/3 Enable SFIN (SAP ERP 6.0
EhP7 on HANA)

Option 3: Replicate into a Central Finance Option 4: HANA Migration

(and optionally reduce number of instances over time) Suite on HANA S/4 HANA
Simple
Migrate &
SLT (SAP ERP 6.0 Finance 2.0
Enable SFIN (SAP ERP 6.0
Replication S/4 HANA EhP7 on EhP7 on HANA)
Simple
SAP ERP Finance 2.0 HANA)
or
SAP R/3
(SAP ERP 6.0
EhP7 on HANA) Option 5: S/4 HANA Enablement
Suite on HANA S/4 HANA
source system(s): Real-time Central Finance Simple
SAP (any release) Reconciled instance (SAP ERP 6.0 Enable SFIN Finance 2.0
(SAP ERP 6.0
non-SAP systems
EhP7 on EhP7 on HANA)
HANA)
Option 6: Non HANA Technical Play (and Future Migration to S/4 HANA)
SAP ERP SAP ERP 6.0
S/4 HANA
EhP7 on DB2 Upgrade, SFIN 4.0
(DB2 Upgrade &
Blu (tbc) Migrate & SLOG 2.0
Database) Migrate (SAP ERP 6.0
Enable SFIN & SLOG EhP10 on HANA)

For
45
S/4 HANA there is a separate sub-option for On-Premise versus HANA on Cloud for all of the abov
 Summary of Deployment Scenarios for S/4 HANA
# Scenario As Is IT Roadmap Migration Path Considerations Options
1 Greenfield New SAP customer or 1. New Template project starting on S/4 HANA , 1. For new implementation, direction is clear For complex IT landscape in addition
Implementation old versions of SAP Simple Finance 2.0, New GL) 2. For complex as is landscape this needs a to Greenfield for core businesses,
(and highly review of options and costs, but it could be there may be an option for SAP
customised) that re-implementation has strongest BusinessByDesign for smaller
business case subsidiaries

2 Upgrade and AnyDB (Ehp7 or 1. Upgrade (to SAP ECC 6.0 Enhancement Pack 1. Migration Path Items 1&2 (Upgrade and 1. Applicable to all instances, but
Migrate before) 7) Migration) can be combined into a single can be different timescales
2. Migration from AnyDB to Suite on HANA technical release 2. Optionally consolidate instances
Database 2. Recommendation is to keep enablement of before Upgrade & Migration
3. Enablement of S/4 HANA (Simple Finance 2.0) Simple Finance as a separate functional
release

3 Replicate into a Disparate source 1. Implement new S/4 HANA Central Finance 1. Non Disruptive approach 1. Future migration of new
Central Finance systems on different system with Simple Finance 2.0 2. Needs a level of process harmonization and functionality into Central
(via Universal versions 2. Data & Process Harmonization across Source data consistency across source ERP's Finance (e.g. Full Finance,
Journal) Systems 3. Full Finance function not available on Logistics)
3. Setup SLT Replication from Source Systems Central Finance with initial release 2. Optionally reduce number of
instances over time

4 HANA Migration Already on ECC6 1. Migration from AnyDB to Suite on HANA Recommendation is to keep enablement of Based on validation of cutover
Ehp7 Database Simple Finance as a separate functional release downtime, combine HANA Migration &
2. Enablement of S/4 HANA (Simple Finance 2.0) from the technical database migration Simple Finance enablement

5 S/4 HANA Suite on HANA, 1. Enablement of S/4 HANA (Simple Finance 2.0)
Enablement SPS09

6 Non HANA DB2 Database 1. Upgrade (to SAP ECC 6.0 Enhancement Pack No immediate business case for S-Innovations 1. DB2 Blu In Memory Database not
Technical Play (Ehp7 or before) 7) dependent on as is release but IT benefits from In Memory database yet supported on ECC!
2. Migration to DB2 Blu 2. Future migration to S/4 HANA
3. Future Upgrade & Migration to HANA when all S-Innovations are
4. Future enablement of S/4 HANA (Simple available
Finance x.0, Simple Logistics x.0)

For all of the above options there is a Full Transformation Scenario from IBM offering above IT Roadmap activities,
Transformational Roadmap (e.g. Analytics, Cloud SaaS, Mobility); Application Hosting (via IBM AMS) and Cloud Hosting (via
IBM
46 CMS)
Moving to S/4 HANA
Technical Upgrade & Migration but a Transformation Opportunity with S/4 HANA
 HANA Managed Cloud Deployment Options with IBM
1. Managed Cloud 2. Managed Cloud 3. Managed Cloud
(licensed & operated by SAP) (licensed by SAP & operated by IBM) (licensed & operated by IBM)

a) Simple Finance License (SAP) a) Simple Finance License (SAP) a) Simple Finance License (IBM)

b) Hana License (SAP) b) Hana License (SAP) b) Hana License (IBM)

c) Enterprise Support (SAP) c) Enterprise Support (SAP) c) Enterprise Support (SAP)

d) Infrastructure (SAP) d) Infrastructure (IBM HEC) d) Infrastructure (IBM HEC)

e) Infrastructure Services (SAP) e) Infrastructure Services (IBM) e) Infrastructure Services (IBM)

f) Baseline AMS (SAP) f) Baseline AMS (IBM / SAP) f) Baseline AMS (IBM / SAP)

Xxx $ / User / Months Xxx $ / User / Months Xxx $ / User / Months

+ Implementation Services (IBM/SAP) + Implementation Services (IBM/SAP) + Implementation Services (IBM/SAP)

+ Migration Services (IBM/SAP) + Migration Services (IBM/SAP) + Migration Services (IBM/SAP)
+ Integration Services (IBM/SAP) + Integration Services (IBM/SAP) + Integration Services (IBM/SAP)
+ Additional AMS Services (IBM/SAP) + Additional AMS Services (IBM/SAP) + Additional AMS Services (IBM/SAP)
+ IBM Global Financing (IBM) + IBM Global Financing (IBM) + IBM Global Financing (IBM)

48
IBM SAP HANA Cloud Offerings Comparison
AMM4SAP - SL CMS4SAP
Positioning Managed PaaS Managed PaaS with high availability and high scalability

Supported Operating
Windows, RHEL Windows, RHEL, AIX
Systems

IBM DB2 , Oracle, Microsoft SQL Server, HANA, Sybase IBM DB2 , Oracle, Microsoft SQL Server, HANA, Sybase ASE
Supported DBs
ASE

Appliance: 128GB, 256GB, 512GB, 1TB, 2TB, 4TB, 6TB;

Bare Metal: 128GB, 256GB, 512GB, 1TB (Limit for BW), 2TB
scale out possible
HANA Sizes (Limit for ECC)
Virtual HANA: Planned for 2H 2015
Virtual HANA: 128GB, 256GB

vCPU: 2, 4, 8, 12, 16 Wintel 64 AIX

Cores: 2, 4, 8, 12
RAM: 4GB-256GB Wintel 512GB AIX
VM Server Sizes RAM: 4GB-64GB
Disk: 100GB-48TB
Disk: 100GB-5TB

80,000 SAPS per AIX SAP instance

15,000 SAPS per SAP instance (20 -25k SAPS being
Max SAPS 40,000 SAPS per Win/LINUX SAP instance (limit is VM size
tested); (limit is I/O in SL)
in CMS)

Max DB Size 5TB average for manageability 18 TB (can to extend to 30TB)

Storage Tier 2, Tier 3 Tier 1, Tier 3

VPN or MPLS (Customer Provided)

Connectivity options VPN or MPLS (Customer Provided)
AT&T Netbond
99.5% , 99.7% Enhanced, or 99.9 HA (AIX)
Availability 99.5% , or 99.7% Enhanced Availability

Disaster Recovery RTO=4h, RPO=1h (only with OS+DB+SAP) RTO=4h, RPO= 15 min
49
IBM Cloud for SAP HEC GTM Org Structure
Susan Teeter
Global Cloud Delivery SAP
Susan Wallace
Global SAP Marketing Leader

Bruce Otte/Rick Morgan

SAP Cloud Offering Exec

Bob Breitel / Brian Burke

Jan Jackman
Global SAP Alliance Leader
VP, Cloud for SAP
Global Cloud Services Joe Gallego
Global Cloud SAP Enablement

Madhuri Chawla
Global CTO, SAP Cloud Technical Sales

IBM SAP Solution Architects

Laura Scott NA:
Alberto Di Lallo VP, Cloud SAP HEC Sales &
Cloud BDE Stephen Melvin, Global & NA Lead
Cloud for SAP Operations
Carlos Freitas, NA Lead
Swami Mahalingam
Roger Chu
Larry Spoerl Mani Thavasi Raj Nunna Debbie Jaquins Raikumar Ivar
Global HEC Sales GBS BDE / PM Bus Proc Model Operations Ldr Martin Barbeau
Kevin Collins
Geo SAP Leaders Lauri McInnis
Alka Patel
NA: LA:
Andre Rosenthal/
Walter Merrill, Dir, SAP for Cloud Valdemir Marques, SAP Cloud Leader
Gerald Kopecky
David Aschenbach, HEC Leader Paschoal Auria, Cloud Services Leader Brazil
Europe:
Chet Vayani, HEC Leader, West Paola Becerra, Cloud Services Leader Mexico
Arne Korsgaard Meier, Lead
Angus Palmer, HEC Leader (Cloud Ldr) ) Hernan Campos, Cloud Services Leader SSA
Maik Gasterstaedt, Lead
Europe: AP: Jie Jang
Susan Volkmann, Director, SAP for Cloud Leader Levent Tavsanci,, SAP Cloud Leader LA
Francisco Alvarez - BeNeLux Daniel Wong, ANZ Cloud Svcs Leader Guillermo Ramirez, Lead
Milan Otajovic - CEE Brian Groen, Cloud Svcs Exec, IBM China/ Hong Kong Cleiton Freire
Robin Regnaud - France Samuel Tsai, Sr. Manager Cloud, IBM Taiwan Yankel Schwartz
Philipp Boltze - DACH Sudesh C Bajaj, ISA (India South Asia) Cloud Svcs AP
Henning Glegg-Soerenson - Nordic Yan Nuen Foo, ASEAN Cloud Svcs Lead, ASEAN Yuijan Yan, APJ Lead
Marta Camarero Fernandez - SPGI Tony Eng, Singapore Cloud Svcs Sales Amit Dayal
Laura Meroni - Italy GCG: Dennis Yue (Cloud Leader)
50 Manjeet Garcha - UKI Japan: Masayoshi Hoshi (Cloud Leader)
-24 additional SAP Architects
from extended team in Geo
Questions & Answers
Thank you
 Appendix

53