Consolidate your SAP System landscape Teched && d-code 2014

©  2013 DataVard GmbH # 1

Goetz Lessmann, DataVard Inc.

10/22/2014

Consolidate Your SAP Landscape


At DataVard, we help our customers run their SAP landscapes better. u  SAP only u  Specialized in Data Management u  ILM / Archiving / NLS u  System Landscape Optimization

©  Copyright DataVard GmbH / 2


SAP System Consolidation Step 1: Discover the savings potential

Reduced TCO -  Hardware -  Running the system (e.g. upgrades,

notes, support packages)

Be faster in implementing new functionality, change, and upgrades

Develop once and use-for all

ERP

BW

ERP

BW get ready to go to

HANA or to the cloud

or

consolidate directly

into HANA


SAP System Consolidation Step 2: Forget (most of) what you know about migrations

Consolidations include a move of data from system to system. -  All data or partial move (“carve out”) of master data + open items.

-  Historical data possible (LSMW cannot do this!).

Consolidations don’t mean a huge process break: moving historical data is entirely possible!

Consolidations are not key-date dependent. -  You can do this at any time of the year.

There is no need for long parallel operation of old and new systems.

You don’t need to keep legacy systems for the next 10+ years. -  You can be SOX compliant in the consolidated system!

Data migrations can be cross-release and cross-OS/DB. -  Examples: You can move from R/3 4.7 into ECC 6 or from BW 3.5 into 7.3 on HANA!


SAP System Consolidation Step 3: find out what needs to be harmonized

Relevant data areas u  ABAP code: custom development, modifications, enhancements, Z-developments u  Other repository objects (DB table definitions, fields, search helps, …) u  Customizing

u  Client independent customizing (ERP: factory calendar) u  Client dependent customizing: Org. units and application customizing

u  ERP-only: Number ranges u  BW-only: Data model (DSO, info cube definitions, info objects, attributes, ETL, data flows) u  Other areas

u  System sizing and performance u  users & authorizations

Important: exclude SAP standard from the comparison!

Two-step approach: 1.  Tool based assessment to discover relevant conflicts. 2.  Interpretation of results to build work packages and plan

harmonization approach (manual <> automated)


SAP System Consolidation Step 3: find out what needs to be harmonized (examples)


SAP System Consolidation Step 4: Do the harmonization

BW data model and Info cubes n  Before: same info provider used in both BW systems n  Solution: tool-based refactoring of info providers n  After: Two providers with different names

n  Refactoring includes data flow and queries n  Possible for complete data models to create a

“client dependent BW” n  Alternative: implementation of compounding or

prefixing

ERP Data n  Before: plant 1200 is used in both systems n  Solution: mapping 1200 => 1300 n  After: plants 1200 & 1300 are used in one ERP system

n  All documents including history are moved to plant 1300

n  Business processes work exactly as before n  Note: All hard coded values in programs need to

be changed as well!

Tool-based harmonization approach n Conflict resolution has to be tool based: huge # of conflicts, completeness, workload n  Implementation

n  Refactoring: Repository name changes n  ABAP changes (hardcoded values, forks) n  LT & SLO (System Landscape Optimization)


SAP System Consolidation Step 5: Perform test consolidations

Cu

tove

r

System comparison & analysis

Implementation & harmonization

Unit test

Pre

pa

rati

on

Test #1

Test #2

Test #3 (optional)

Dry run (optional)

Going live

Te

st

cycle

s

•  Test cycles with stepwise refinement •  Ideally in separate project systems •  Several full iterations of data move

•  Testing of data move •  Performance test •  Tests of harmonization •  Functional tests

•  Tests are similar to upgrade projects •  Functional tests should be automated


SAP System Consolidation Step 6: going live (just do it!)

Discover the savings potential

Forget (most off) what you know about

SAP data migrations

Find out what needs to be harmonized

Implement harmonization Test cycles

Step 6 Go live – some recommendations: -  Big bang: use a (long) weekend – no lengthy bit by bit consolidation -  For #n-way consolidations perform roll-ins spaced 4 to 8 weeks apart -  Prepare the weekend well (e.g. move new ABAP development into production up

front where possible) -  Development freeze between dry run and golive -  System lock (“downtime”) during the golive -  Refresh non-production systems after golive

1 2 3 4 5

6


SAP System Consolidation Toolset used in projects

Conflict analysis: System Comparison §  SAP LT‘s analysis tools §  DataVard ERP Fitness Test, BW Fitness test

Harmonization: Solving conflicts §  Refactoring: DataVard Chameleon (ERP repository, BW

including data flows) §  Hard coded value scan & semi-automated replacement §  Mass delta transports (for ERP and BW): SAP TMS,

DataVard Shuttle

Testing §  SAP on-board test tools: CATT, eCATT §  DataVard KATE: automated testing for ERP and BW

Data Move ERP §  SAP LT (SAP Landscape Transformation) §  DataVard Canary Code

Data Move BW §  DataVard ReLine §  DataVard Canary Code

Tools are important to finish consolidations in time & budget, but:

“A fool with a tool … is still a fool.”

(A wise SAP project manager)


SAP System Consolidation DO’s and DON’T’s

1.  Go for a big bang – avoid lengthy parallel operation

2.  Pick the target platform wisely (OS/DB), but also re-use existing source system.

3.  Avoid manual work and use tools & automate as much as possible.

4.  Step by step: go for a technical consolidation first, and then start with process harmonization

u  Forget Greenfield and LSMW. This works, but tons of disadvantages. u  Don’t fall for process redesign discussions. They will never end.

5.  Automate testing (up to a healthy degree)

6.  Go for production – don’t do “dev system only” consolidations.

7.  Consider BW-only consolidations if you have several BW systems

8.  Switch off: don’t keep old systems running – migrate all data instead. If that’s too much data, consider NLS or ILM.

9.  Do more with less & accelerate your IT roadmap: Consolidation is possible cross-release and cross-OS/DB. You can kill two consolidate directly into HANA!

Thank you for your attention!


© 2014 DataVard Inc. 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 DataVard. The information contained herein may be changed without prior notice. Some software products marketed by DataVard GmbHand its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to DataVard. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of DataVard. This document is a preliminary version and not subject to your license agreement or any other agreement with DataVard. This document contains only intended strategies, developments, and functionalities of the DataVard® product and is not intended to be binding upon DataVard to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by DataVard at any time without notice. DataVard assumes no responsibility for errors or omissions in this document. DataVard does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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. DataVard shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. DataVard has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Date post:	11-Jul-2015
Category:	Technology
Upload:	goetz-lessmann
View:	650 times
Download:	1 times