typical carve-out scenarios for erp landscapes

11
Business Landscape Transformation Carve-Out Scenarios For ERP Landscapes snp-ag.com/ carve -out

Upload: snp-ag

Post on 26-Jun-2015

205 views

Category:

Leadership & Management


2 download

DESCRIPTION

Especially in companies that often move or sell divisions, IT should implement so-called carve-outs software. With SNP Transformation Backbone standard software, your IT department receives an effective and time-efficient approach for ERP transformations, support in harmonizing the merged business and high audit security through the use of reviews.

TRANSCRIPT

Page 2: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Typical Scenarios Analyze Business Workflows

and System Landscape Harmonize Organizational Structures

(e.g. Profit Center, Chart of Account) Consolidate ERP Clients or Systems Split ERP Clients or Systems Move ERP Clients or Systems

Software SNP Transformation Backbone

SNP Transformation Backbone

Business Driven Triggers for Change

| 2

Carve Outs & Divestures

Mergers & Acquisitions

Reorganization

Page 3: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Typical Scenarios Analyze System Landscape Upgrade to SAP HANA or Cloud Upgrade ERP Release Migrate Legacy Systems Harmonize ERP Data Translate ERP Systems

Software SNP Transformation Backbone SNP Data Provisioning & Masking SNP Dragoman

SNP Transformation Backbone

IT Driven Triggers for Change

| 3

ERPConsolidation

DataHarmonization

Upgrade &Replatforming

Page 4: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Business Transformation

Divestitures and carve outs Mergers and aqcuisitions Restructuring, demergers and spin-offs Post-Merger-Integration

IT Challenges

These transformations lead to a mapping and adaptation needs in the underlying financial systems (SAP), which are characterized by data migration and conversation efforts.

SNP Transformation Backbone

Typical Carve Out Scenarios

ERP Transformation

Client Carve Out

Move one or more client(s)

from a single source system

to thetarget system(s)

Split by Company Code

Split by company code and move

migrate data from a single

client to a target client

Split by Org Structure

Split the existing org structure

at the company code level

and migrate data

| 4

Page 5: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Enterprise Transformation Platform: Pre-configured

transformation scenarios Re-usable workflow

and project templates Pre-defined rules and

validations sets

Technical Components: ERP System Scan and Analysis Business Process Visualization Migration and Conversion Engine Consistency & Compliance Engine Cockpits (GUI) & Portals

SNP Transformation Backbone

A Software-Based Approach For Carve-Out

| 5

Page 6: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

SNP Transformation Backbone

Transform into New Business Landscapes

| 6

Cloud

Legacy

ERP

Mobile

old

bu

sin

ess lan

dscap

e

new

bu

sin

ess lan

dscap

e

Page 7: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Auditor and vendor certifications

Off-the-shelf software and processes

Employ agile project management policies and procedures

Technical migration specialists and business process consultants

SNP Transformation Backbone

Our Factors of Success

| 7

Page 8: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Transformation software vendor due to the experience with more than 2.500 transformation projects

Over 20 years track record of excellence in the ERP market

SNP Transformation Backbone

Company Profile

| 8

Page 9: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Certified SAP Service Partner and Oracle Gold Partner

Market presence in United States, Germany, Austria, Switzerland, Spain, and South Africa with over 250 employees

SNP Transformation Backbone

Company Profile

| 9

USA GermanyAustriaSwitzerlandSpain

South Africa

Page 10: Typical Carve-Out Scenarios For ERP Landscapes

Carve-Out

Automate data migration through a centrally managed system of rules

Reduce the need for manual programming by up to 90 percent

Improve data consistency

Compliance of the data and processes

»Thanks to the transformation with SNP, we were able to consolidate our system landscape in an extremely efficient way.«

SNP Transformation Backbone

Reduce manual programming by up to 90 percent

Madeleine Petit

CIO, ABB Switzerland

| 10

Page 11: Typical Carve-Out Scenarios For ERP Landscapes

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SNP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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 SNP. 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 SNP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SNP. This document contains only intended strategies, developments, and functionalities of the SNP® product and is not intended to be binding upon SNP 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 SNP at any time without notice.

SNP assumes no responsibility for errors or omissions in this document. SNP 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.

SNP 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.

Heidelberg , Germany, 2014

DisclaimerCopyright 2014 SNP AG. 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 SNP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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 SNP. 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 SNP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SNP. This document contains only intended strategies, developments, and functionalities of the SNP® product and is not intended to be binding upon SNP 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 SNP at any time without notice.

SNP assumes no responsibility for errors or omissions in this document. SNP 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.

SNP 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.

Heidelberg , Germany, 2014

DisclaimerCopyright 2014 SNP AG. All Rights Reserved.