13
Customizing Synchronization between ERP and Master Data Governance (MDG) Juergen Bold / Michael Boettcher - MDG Product Management November 2012

Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

  • Upload
    others

  • View
    14

  • Download
    2

Embed Size (px)

Citation preview

Page 1: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

Customizing Synchronization between

ERP and Master Data Governance (MDG)

Juergen Bold / Michael Boettcher - MDG Product Management

November 2012

Page 2: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 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.

Page 3: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 3

SAP SCM

3rd party,

NWAs

SAP SRM

SAP ERP, SCM,

CRM, SRM …

3rd party,

NWAs

SAP MDG deployment options Consciously decide for a central hub or co-deployment

Deploy SAP MDG…

… as standalone system /

master data hub

… on top of an

operational ERP

Customers typically choose to…

… create a dedicated master data hub and distribute to all operative systems from there, or

… co-deploy*) with their single instance SAP ERP (or pick one of their SAP ERP’s as the

master for a particular domain) and create and distribute master data from there

SAP MDG SAP ERP

SAP MDG

& SAP ERP

*) if speed of innovation in their ERP systems does not allow for quick introduction of SAP MDG, some customers create a separate system first, and re-combine later

prerequisite: synchronized customizing

Page 4: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 4

Synchronized Customizing

Basic Assumptions

If a transfer of customizing data takes place, customizing data must be

identical in specific areas in the two systems*.

Customizing data should be maintained only

once but the sender might be different based

on the type of customizing data

Automation and Synchronization of customizing data transfer is preferable.

Customizing Transfer

Master Data Replication

SAP MDG SAP ERP

* Value Mapping in Data Replication can be used to overcome differences

Page 5: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 5

Synchronized Customizing

Two Important Aspects

What are the sets of customizing

data to be transferred?

How to transfer the customizing and how to keep it synchronized?

SAP MDG SAP ERP

Page 6: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 6

Synchronized Customizing

Which set of customizing data needs to be transferred?

Types of Customizing data

• Reference data (ISO codes … )

• Project specific customizing defined in an implementation project (IMG based)

• Master data related customizing

• MDG Customizing

Object list of relevant customizing tables

Page 7: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 7

How to synchonize customizing data?

Basic Assumptions

System roles

• Source system – target system

Process

• Customizing Maintenance Filter Export Import Activate

• Transport within D-Q-P system landscape

Types of Customizing Synchronization

• Initial Synchronization

• Explicit

• Implicit

• Ongoing Synchronization

• Automatic

• Manual

Page 8: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 8

Manual Maintenance in connected systems

• Transports / BC Sets (Business Configuration Sets)

• ALE Customizing Distribution

• Customizing Synchronization

• Change Request Management (CHaRM)

• Retrofit

• Reference Data Governance

Customer specific implementation

SAP Basis

SAP Solution Manager

SAP MDG – Custom Objects

Synchronized Customizing

Tool support

Page 9: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 9

Customizing Synchronization-Process

Example

Time zones

Transport zones

Currencies

Customer groups

...

Save customizing into

transport request

1

SAP

Solution

Manager

SAP

ECC

DEV

SAP

MDG

DEV

SAP

ECC

QAS

SAP

ECC

PRD

SAP

MDG

QAS

SAP

MDG

PRD

Notify Solution Manager

about customizing changes 2

Map source into target customizing

after importing changes 3

Send target settings

to target system 4

Time zones

Transport zones

Currencies

Customer groups

...

Activate BC Set and write target

settings into transport request 5

Log

Generate distribution logs 6

Page 10: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 10

Reference Data Governance

With SAP MDG Custom Objects

SAP Master Data Governance extends the existing process with governance

Start business-driven governance process on some attributes in MDG (ID, description, some

“global” attributes)

Add all “SAP Template” attributes in the IMG in the customizing master system

Complement local attributes (that are different per system landscape)

Customizing Template

MDG Reference Data

ID

Description

Cust.Attribute 1

Cust.Attribute 2

Cust.Attribute 3

IMG ID

Description

Cust.Attribute 1

Cust.Attribute 2

Cust.Attribute 3

WebUI

Transport Data Replication

Framework

Cust.Attribute 3

IMG

Solution Mgr. (optional)

Page 11: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

Thank You

Juergen Bold Product Management

Master Data Governance

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf, Germany

E [email protected]

Please visit www.sap.com/mdg

Michael Boettcher Product Management

Master Data Governance

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf, Germany

E [email protected]

Please visit www.sap.com/mdg

Page 12: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

Appendix

Page 13: Customizing Synchronization between ERP and MDG...This in particula r is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational

© 2012 SAP AG. All rights reserved. 13

© 2012 SAP AG. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu

welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche

Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen

können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können

Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken der

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,

Informix und Smarter Planet sind Marken oder eingetragene Marken der IBM Corporation.

Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Ländern.

Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene

Marken von Adobe Systems Incorporated in den USA und/oder anderen Ländern.

Oracle und Java sind eingetragene Marken von Oracle und/oder ihrer

Tochtergesellschaften.

UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin

sind Marken oder eingetragene Marken von Citrix Systems, Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®,

World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri und Xcode sind Marken oder eingetragene Marken der Apple Inc.

IOS ist eine eingetragene Marke von Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry

Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook und BlackBerry App

World sind Marken oder eingetragene Marken von Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,

Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik und Android sind

Marken oder eingetragene Marken von Google Inc.

INTERMEC ist eine eingetragene Marke der Intermec Technologies Corporation.

Wi-Fi ist eine eingetragene Marke der Wi-Fi Alliance.

Bluetooth ist eine eingetragene Marke von Bluetooth SIG Inc.

Motorola ist eine eingetragene Marke von Motorola Trademark Holdings, LLC.

Computop ist eine eingetragene Marke der Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, SAP HANA und weitere im Text erwähnte SAP-Produkte und -

Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken

der SAP AG in Deutschland und anderen Ländern.

Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports,

Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwähnte Business-

Objects-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken

oder eingetragene Marken der Business Objects Software Ltd. Business Objects ist ein

Unternehmen der SAP AG.

Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und weitere im Text

erwähnte Sybase-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind

Marken oder eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der

SAP AG.

Crossgate, m@gic EDDY, B2B 360°, B2B 360°Services sind eingetragene Marken der

Crossgate AG in Deutschland und anderen Ländern. Crossgate ist ein Unternehmen der

SAP AG.

Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen

Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informations-

zwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und

Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und

in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch

SAP AG gestattet.