Upload
rafe-sanders
View
219
Download
0
Tags:
Embed Size (px)
Citation preview
Network Services’ Journey to HANA:Suite and BW on HANA
Tom Thein, Network Services Company
LEARNING POINTS
How we approached our Journey to HANA: Cloud approach vs. hardware investment => consider
hosting / cloud ECC EHP Upgrade (our first one) Migration to HANA – Suite on HANA, BW Other SAP/Third Party System Upgrades
Best Practices / Lessons Learned Improvements / Results
Company Profile – Network Services
NETWORK® is a major national distribution company providing:
Over 40 years of experience as a category specialist
Expertise in cleaning and sanitation, industrial packaging, disposable products, and printing paper
A vast infrastructure Customizable programs A wide product selection from leading
suppliers
NETWORK® delivers focused expertise within core product categories
Focused Expertise
Janitorial supplies
Foodservice disposables
Industrial packaging supplies
Printing paper
Equipment
And more
Yielding proven solutions based on deep experience and insight
Focused Range of Industries
Healthcare
Commercial Real Estate
Foodservice
Industrial
Public Sector
Commercial Printing
itelligence SAP HANA | The continuous progress of SAP HANA@itelligence
itelligence has walked the Road To SAP HANA with SAP
And we have the customers to prove it
SAP ECC 6.0 EHP 3
SAP PI 7.1
SAP Portal
All reporting, Visual Composer Apps SAP BI (BOBJ Enterprise)
SAP BW 7.3
SAP MDM – Material and Customer Master
SAP Solution Manager
Technical Monitoring, ITSM, Change Management SAP Router
SAP Landscape (Before)
Business Case for Suite on HANA
Performance Improvements- ECC – AR, GL, Agency Business t-codes running 3-6 minutes- BW/BI – long running reports, Webi’s- High Transaction Volumes – day/month/year invoice lines, pricing records
Recognized Need to get to HANA to use New SAP Apps- Most new applications (i.e. Lumira, Mobile, etc.) only written for HANA
SAP Upgrades Needed – Core SAP and Interfaced Systems- OS, DB Upgrades Needed (Windows Server 2003, SQL Server 2005)- SAP ECC, PI, MDM- Interfaced Systems (Vertex, Paymetric, Esker)
Leverage Licensing Opportunity- Needed PI, FSCM, Developer, other Licenses in late 2013- What’s the best time to buy SAP Licenses? “Let’s Make a Deal”
Evaluation Process – VERY Complex Defining scope was surprisingly difficult:
HANA - Hosting vs. On Premise Hardware Decision ECC EHP Upgrade All other SAP – BI, PI, Portal, CS, MDM, SOLMAN, SAPRouter…. All SAP Partner Systems – Vertex, Paymetric, Esker… HANA Migration Tasks – Consulting vs. AMS/BASIS
Ongoing HANA multi-tenancy and virtualization changes and announcements were monthly during our selection – what what was allowed constantly changing, huge hardware implications ($$$)
Evaluation – HANA Approach
Evaluation Process – VERY Complex Apples to apples comparisons were very difficult to get to
with so many variables
Narrowed down to three finalist HANA HW providers, and three HANA Hosting providers
Took seven months to size and finalize the comparison across six quotes, develop our financial comparison models to evaluate them fully
No HANA cloud vendor would effectively commit to the calculations for bandwidth requirements for our Primary Data Center to Hosting Data Center
Evaluation – HANA Approach
Evaluation and Selection Challenges How to do a true comparison including all other variables
included for on premise vs. cloud (telecom, cost per server of maintaining existing systems, etc.)
Differing opinions on what other systems required upgrades to be compatible with HANA / ECC EHP levels (i.e. PI, and third party systems)
Differing opinions on what other SAP systems should also be moved to Cloud, if Cloud approach chosen
Lack of references live on Suite on HANA
Evaluation – HANA Approach
Evaluation – HANA Approach
HANA On-Premise
HANA Cloud / Hosted
Operating Expense
Speed to Create Environment
Flexibility for Add-On’s, POC’s, Mock Conversions, etc.
HANA Administration Expertise & Availability
Capital Investment
Control over Environment
Cost: Neutral Over 10 Years
Migration to Hosting
Enhancement Pack Upgrade
Testing / Migration
Steps / Go Live
Ongoing Support of
Environment
(Hosted)
(Remaining on-Prem)
Evaluation – Chosen Partners
NETWORK SAP Landscape
ECC – 1.5TB pre-HANA SQL Server DB size BW – 400GB pre-HANA SQL Server DB size Other systems recommended to move to Cloud:
BI / BOBJ Content Server (SAP Attachments & Archiving) Solution Manager (integrate into Service Provider’s)
Other systems requiring upgrades: PI, Portal, Vertex, Esker, Paymetric, CDI
(eCommerce) – all times 3 (Dev/QA/Prod) Panaya – Implementation and setup for use
Project Planning – Components
VMWare Replication used to move systems to Hosting Center pre-cutover, then ongoing replication after initial replication completed for each system
Needed to manage dual-maintenance across development landscapes (on-premise & hosting DEV/QA), and minimize new development efforts
Cutover weekend a complex endeavor; managed 90 cutover tasks between Friday night 8pm – Sunday 1pm
Project Planning – Phase 1 Hosting
Aug-14
Sep-14 Oct-14 Nov-14 Dec-14 Jan-15 Feb-15
Project Prep
DEV to Hosting
QA to Hosting
Integration Tests & Mock RunsPROD Cutover
PROD Support
ECC Upgrade/HANA Migration and BW HANA Migration executed in parallel
Basis Team utilized SAP DMO (DB Migration Option) to migrate SQL to HANA
Remediation Tasks – 408 Correction Tasks and 585 Unit Tests
2 Integration Test Cycles – 196 Scenarios and 920 Steps
Cutover weekend: managed 80 tasks between Friday night 8pm – Sunday 2pm
Project Planning – Phase 2 EHP/HANADec-14 Jan-15 Feb-15 Mar-15 Apr-15
Project Prep
Initial Upgrade
Code Remediation
Integration Testing & Mock CutoverFinal Prep & Cutover
PROD Support
Team Size: 13 external resources at peak (6 Onsite and 7 Offsite) 1 Project Lead (Onsite) 3 Functional Resources (Onsite) 4 ABAP (1 Onsite) 2 BW (1 Onsite) 1 Security 2+ Basis resources (itelligence Hosted site)
~10 NETWORK IT resources Core IT Team executed Integration Test Cycle 1 Business Team executed Integration Test Cycle 2
The Project Team
Learnings on Approach: Archive First
HANA Appliances are sized based on your DB size, so complete archiving prior to sizing your equipment (also to better know what your annual growth rates are)
Plan to spend a lot of time on Hosted / Cloud vs. On Premise Decision Move to cloud requires that you understand every detail
of the cloud provider offering What’s included for: Local hardware failure, Backup /
Recovery, DR process, system copies, etc. Talk through the migration approach – if VMWare
replication desired, confirm and price (extra temp. storage and servers)
KEY LEARNINGS / BEST PRACTICES
Learnings on Approach: Leveraged VMWare – allowed migration of
servers to cloud provider using VMWare snapshots and replication tools Many providers wanted to use USB disks and
physical media – takes too long for weekend cutover
Combined EHP Upgrade and HANA Migration into one single testing process for end users IT did the initial unit and integration testing End users were only involved in the final Integration
Test Cycle
KEY LEARNINGS / BEST PRACTICES
Learnings on Approach: Leveraged Panaya Upgrade Tool to make
process easier to do this time (and in future) Panaya features: initial environment review, scope
setting, remediation analysis, testing planning, workflow, results capture, dashboards and status, re-use for training materials
Pays for itself in project cost savings…
KEY LEARNINGS / BEST PRACTICES
Panaya – Project Management
Learnings on Approach: EHP7/HANA New T-codes – some of the HANA optimized T-
codes do not work “out of the box” Requires OSS Note(s) to activate switch framework These are not called out and we had to “find” these on
our own (i.e. FBL5N => FBL5H) SAP Notes
List of Optimizations for SAP Business Suite on HANA http://scn.sap.com/docs/DOC-59889 1761546 - SAP ERP powered by SAP HANA – Optimizations
SQLM – new tool available to identify performance improvement opportunities; have utilized already
KEY LEARNINGS / BEST PRACTICES
Learnings on Approach: Timelines Duration: migrating to a new cloud provider from
an existing on-premise installation likely requires at least 4-5 months
Why? Telecom lead times are BRUTAL 3-4 month lead time on new telecom circuits Can do DEV and even some QA on existing internet
(if you have enough bandwidth on both sides) Cannot do true load test or safely go to PROD until
new circuit is live and tested
KEY LEARNINGS / BEST PRACTICES
Learnings on Approach: HANA DB Levels HANA Release Level Challenges – very frequent,
often with known issues Project decisions on which is better/worse SAP Guidance – go to each revision up until the
next “Datacenter ServicePoint” (SAP production system verified SAP HANA Revision)
See SAP Note for guidance: 2021789 - SAP HANA Revision and Maintenance Strategy
We started on v93, have patched 2x already
KEY LEARNINGS / BEST PRACTICES
Learnings on Approach: Hosting Providers Cloud providers will require a host domain
change for all hosted servers Never came up presale In a hybrid environment this is a big challenge Became the single biggest issue in our project – has
nothing to do with HANA Cross domain trusts SSO / SNC issues Portal, BW, BOBJ, other Certificates
Increased frequency of communications and dependence on our Hosted Basis Team, especially with HANA
KEY LEARNINGS / BEST PRACTICES
Significant reductions in DB sizes:
RESULTS
Pre-HANA
ECC – 1.5TB
BW – 375GB
On HANA
ECC – 275GB
BW – 90GB
81.7%
76.0%
Improvements (huge) in ECC Performance: Significant improvements for our most commonly
used T-codes FBL5N: 360 seconds for 115,000 records => 10 seconds FBL1N: 300 seconds for 247,000 records => 30 seconds ZEDINEW: 85 seconds for 11,409 IDOCS => 15 seconds
Overall speed improvements for AR, AP, GL and IDOC list and processing screens averaging 200 to 3,000 times performance improvement
Some long running jobs finish much faster (e.g. Monthly AR Statements: 35,000 seconds to 2,000 seconds)
RESULTS
Improvements in BW Performance: 43 Queries analyzed before/after Overall 93% improvements in speed Average time of 38.275 seconds down to 2.485
seconds
Many of our most painful: SD Invoices – 284 seconds to 0.997 seconds Business Reviews – 445 seconds to 1.9 seconds
Nightly Process Chains reduced from 6 hours to 3 hours.
RESULTS
Improvements in BW Performance:
RESULTS
Improvements in BW Performance:
RESULTS
First Year Pricing Analysis – customer segments/product
categories over time Optimize key programs (ZEDINEW, etc) New Analytics, HANA Live Fiori and UI5 apps Lumira – Visualization analyses Other things we would not try before today Implement a more frequent HANA DB patching
approach Further down the road:
Simple Finance… S/4
NEXT STEPS
QUESTIONS