Anda di halaman 1dari 17

Master Data

Synchronization

Reiner Herde, Joachim Claus


Master Data Framework
SEM-BCS data storage architecture

Issues with automatic data synch

Manual synch – Master Data

Manual synch - Hierarchies


SEM-BCS data storage architecture

Issues with automatic data synch

Manual synch – Master Data

Manual synch - Hierarchies


SEM-BCS data storage architecture

Requirements:
 Fast read access to master data & hierarchies
1. In Consolidation Monitor and Consolidation workbench
2. In BW BEX reporting
 Write performance of master data is less important
 data change rarely, can be uploaded in batch, over night etc.

Limitations:
 Read access to BW MD via BW BAPI’s (RFC) proved too slow
 BW is less intelligent:
 Does not know SEM-BCS logic and limitations
 Tolerates data which are not acceptable for SEM-BCS, esp. in hierarchies

Solution:
 SEM-BCS needs an own, intelligent , leading data storage
 BW data must stay in synchrony, however.

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


SEM-BCS data storage & automatic synch
All data changes only here!

Consolidation Workbench BW admin.


BW WB
Application layer:
SEM-BCS
•MD maintenance  •Only
•MD maintenance?
read access 
•Flexible upload  •BEX
•BW upload?
reporting 
•Transport  •No
•BWchanges 
transports?
•Data checks  •No
•Nouploads 
data checks!

4711 4712

Data management Master Data Framework BW WHM

4711
 ??? 4711 4712

Local DB tables BW info & ODS objects


Storage layer • Master data • Master Data
• Hierarchies • Hierarchies

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


SEM-BCS data storage architecture

Rules for automatic synch

Manual synch – Master Data

Manual synch - Hierarchies


Rules for automatic synch – customizing 1

1. Customize your Leading Fiscal Year Variant for MDF:


 Needed for correct synch of time-dependent data to BW, see note 676337

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


Rules for automatic synch – customizing 2

2. Activate automatic BW synch during import of transports:

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


Rules for automatic synch – handling

3. SEM-BCS has to have full control over ALL master data changes
 Use Cons. workbench (manual changes or upload) and transports only
 No direct changes by BW means + manual synch:
1. Manual steps required, else asynchrony!
2. No consistency checks on data by SEM-BCS during manual synch!

4. For time-dependent data / hierarchies:


 Maintain data in chronological order always

5. When following these rules, manual synch normally is not necessary.


The need to run synch reports points either on:
 Customizing errors
 Handling errors or bad internal processes
 Intermediate communication / RFC errors
 Program errors in automatic synchronization
6. Implement latest support packages of FINBASIS and SEM_BW.
7. Further information: See OSS notes 689229 and 578348.

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


SEM-BCS data storage architecture

Issues with automatic data synch

Manual synch – Master Data

Manual synch - Hierarchies


Manual synch of Master Data 1

 Report UGMD_BATCH_SYNC:
 For unattended synch of Master data & hierarchies
 Replication Local  BW
 All input selections entered on selection screen
 Error display of all collected messages afterwards
 Selection screen inputs:

Appl. 10 = SEM-BCS

Appl.area = cons.data basis


Limit by fieldnames or not

Synch.modes:
•Write only (add, change)
•Full (replace all BW data)

Synchronize what?
• master data
• hierarchies
 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›
Manual synch of Master Data 2

 Report UGMDSYNC:
 For interactive synch of Master data, texts and attributes only
 Some input selections on selection screen, rest on detail screen
 Display of differing values (asynchronies) in ALV grid control
 Replication Local  BW (default) or vice-versa
 Collected messages displayed after synch
1. Choose field for synch
2. Check/set source / target:
•LOCAL = SEM-BCS
•All BW = all connected BW‘s
•RFC-dest or SysID = distinct BW

3. Refresh display

4. Select values for synch

5. Press Save icon

6. Check for errors


 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›
SEM-BCS data storage architecture

Issues with automatic data synch

Manual synch – Master Data

Manual synch - Hierarchies


Manual synch of Hierarchies 1

 Report UGMD_BATCH_SYNC:
 For unattended synch of Hierarchies & Master data
 Replication Local  BW
 All input selections entered on selection screen
 Error display of all collected messages afterwards
 Selection screen inputs:

Appl. 10 = SEM-BCS

Appl.area = cons.data basis


Limit by fieldnames or not

Synch.modes:
•Write only (add, change)
•Full (replace all BW data)

Synchronize what?
• master data
• hierarchies
 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›
Manual synch of Hierarchies 2
 Report UGMDSY20:
 For interactive synch of hierarchies in one distinct version/period only
 Sel.screen: Enter field, Hierarchy version, period/year of synch
 Replication Local  BW (default) or vice-versa
 Slow: Calculation & display of differences in hierarchies node-by-node
 Tricky, not user friendly – avoid using it! -> UGMD_BATCH_SYNC!
1. Check/set source / target:
•LOCAL = SEM-BCS
•ALL BW = all connected BW‘s
•RFC-dest or SysID = distinct BW

2. Select hierarchy top nodes


3. Press Save icon
4. Leave & re-enter report for
refresh (only FinBasis<2.0)
5. Check synch result
6. Run report chronologically
for all later change periods
too, if necessary

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


Conclusions

1. Make maximum use if automatic synchronization by following its rules


 Complete customizing
 Leading fiscal year variant
 Automatic replication in transport
 Correct procedures
 All changes under control of SEM-BCS, not via BW directly
 Work chronologically

2. If manual synch is necessary, use one of the following reports:


 UGMD_BATCH_SYNC for hierarchies and master data preferably,
easiest, fastest and safest way to synchronize, also for mass synch.

 UGMDSYNC for master data occasionally, mainly for visual comparison

 UGMDSY20 for hierarchies – avoid using, node-by-node comparison is slow,


tricky, requires deeper insight by user, bad usability

3. Further information: See OSS notes 689229 and 578348.

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›


Copyright 2004 SAP 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 SAP 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.
 These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.

 SAP AG 2004, Title of Presentation / Speaker Name / ‹#›