Post on 20-May-2020
transcript
SAP NetWeaver How-To Guide
How To... Transport MDM Objects between MDM 5.5 Systems
Applicable Releases:
SAP NetWeaver Master Data Management 5.5 SP05
SAP NetWeaver Master Data Management 5.5 SP06 Patch 1
IT Practice: Data Unification
IT Scenario: Master Data Management
Version 1.10
February 2008
© Copyright 2008 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, Informix,
i5/OS, POWER, POWER5, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
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.
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.
These materials are provided “as is” 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 shall not be liable for damages of any kind including
without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained
within these materials. SAP 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.
SAP NetWeaver “How-to” Guides are intended to simplify
the product implementation. While specific product
features and procedures typically are explained in a
practical business context, it is not implied that those
features and procedures are the only approach in solving a
specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification or
support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
included in this documentation are only examples and are
not intended to be used in a productive system
environment. The Code is only intended better explain and
visualize the syntax and phrasing rules of certain coding.
SAP does not warrant the correctness and completeness of
the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, except
if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java™. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only
to be used by SAP’s Support Services and may not be
modified or altered in any way.
Document History Document Version Description
1.10 Updated version for SAP NW MDM 5.5 SP06 Patch 1
1.00 First official release for SAP NW MDM 5.5 SP05
Typographic Conventions Type Style Description
Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation
Example text Emphasized words or phrases in body text, graphic titles, and table titles
Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
Icons Icon Meaning
Caution
Note / Important
Example
Recommendation / Tip
Table of Contents
1. Business Scenario............................................................................................................... 1
2. Background.......................................................................................................................... 1
3. Prerequisites ........................................................................................................................ 1
4. MDM Transport Mechanisms.............................................................................................. 2 4.1 Business Objects Model (Repository Schema) ............................................................ 3 4.2 Manual Upload of XML Schemas (for SAP MDM 5.5 SP05 only)................................ 5 4.3 Maps ............................................................................................................................. 6
5. Best Practices ...................................................................................................................... 9 5.1 Initial Transport ............................................................................................................. 9 5.2 Subsequent Transports .............................................................................................. 10 5.3 Ports and Remote Systems........................................................................................ 15 5.4 User Management ...................................................................................................... 17
How To... Transport MDM Objects between MDM 5.5 Systems
1. Business Scenario Even if you run your MDM system productively, you might have to make changes from time to time, for example if you upgrade to the latest release. In order to ensure that your productive system still runs properly after changes were made, SAP recommends a multiple stage landscape consisting of at least a Development (DEV), a Quality Assurance (QA), and a Production (PROD) system environment. So, you develop and modify only in the DEV landscape, and transport your changes to the QA landscape where tests are carried out. Finally, only after tests were successful, you apply the changes to the PROD environment.
DevelopmentDevelopment
TestData
TestData
MDM ObjectsMDM Objects
Transport onlyif tested with Ok
QualityQuality
TestData
TestData
MDM ObjectsMDM Objects
ProductionProduction
ProdData
ProdData
MDM ObjectsMDM Objects
DevelopmentDevelopment
TestData
TestData
MDM ObjectsMDM Objects
Transport onlyif tested with Ok
QualityQuality
TestData
TestData
MDM ObjectsMDM Objects
ProductionProduction
ProdData
ProdData
MDM ObjectsMDM Objects
2. Background This paper deals with the transport of MDM objects between MDM 5.5 systems. Currently, SAP MDM does not come with a comprehensive transport system, so this paper describes which transport mechanisms are supported right now, and outlines the steps that must still be done manually.
3. Prerequisites For SAP MDM 5.5 SP05, most of the MDM objects can be transported applying the mechanisms described in this how to guide, however there are some limitations for the export/import of repository schemas. As of SAP MDM 5.5 SP06 Patch 1, the repository schema transfer has been enhanced, as will be outlined in the following chapter.
March 2008 1
How To... Transport MDM Objects between MDM 5.5 Systems
4. MDM Transport Mechanisms In the following, different transport mechanisms are described depending on the respective MDM objects. The table below shows which transport mechanism has to be applied to the respective objects.
Note Where nothing is indicated, a transport of the respective object is not supported yet. In this case, any changes in the development repository have to be tracked and manually maintained in the target systems.
Tip For manual changes of validations and assignments for instance, please note that Ctrl-c/Ctrl-v only works between two MDM repositories but not between an MDM repository and notepad.
Table: Supported transport mechanism
Object Export/Import Repository Schema
Export/Import Maps Import Manually
Repository Structure
Main Table
Lookup Tables (any type)
Image Variants
Relationships
Calculated Fields
System Tables
Roles
Users
Remote Systems ≥ SP06
Ports ≥ SP06
Links (URLs) ≥ SP06
XML Schemas (XSDs) ≥ SP06 SP05
Workflows
Validations ≥ SP06
Assignments ≥ SP06
Matching Strategies
Maps
Import Maps
Syndication Maps
March 2008 2
How To... Transport MDM Objects between MDM 5.5 Systems
4.1 Business Objects Model (Repository Schema) ...
1. Start the MDM Console. Mount the development repository, and export the repository schema.
Note The repository is described in XML format, however the generated XML format is not a W3C-compliant XSD.
March 2008 3
How To... Transport MDM Objects between MDM 5.5 Systems
2. In MDM Console, mount the transport target repository (here QA), and import the repository schema.
3. This brings up a screen where you have to reject/accept the changes. When finished, select button OK.
March 2008 4
How To... Transport MDM Objects between MDM 5.5 Systems
4. A dialog screen appears that warns you that importing changes may result in data loss. Confirm with OK. However, it is recommended that you back up the master data beforehand so you can recover data in case the data becomes corrupted during the import process, see also chapter 5.2 [page 10].
Tip In case of structural enhancements only, data is preserved. When changing field type or table type for instance, data could get lost (such as from text to integer, or from qualified table to flat lookup table).
4.2 Manual Upload of XML Schemas (for SAP MDM 5.5 SP05 only)
For SAP MDM 5.5 SP05, XML Schemas are not included when the repository schema is exported and imported. XML schema files (XSDs) have to be uploaded to the MDM Console anyway. So, whenever a new schema is uploaded to the development repository, keep track of it, and upload the same file to the target systems (QA and PROD).
For SAP MDM 5.5 SP06, XML Schemas are included in the export and import of the repository schema, see chapter 4.1 [page 3].
March 2008 5
How To... Transport MDM Objects between MDM 5.5 Systems
4.3 Maps Note
Only import maps are shown here, similar applies to syndication maps. ...
1. Launch MDM Import Manager [MDM Syndicator], and connect to the development repository. Create (not shown here) and save a map.
2. Export the map. A file with suffix map [syn] is created.
March 2008 6
How To... Transport MDM Objects between MDM 5.5 Systems
3. Start MDM Import Manager [MDM Syndicator]. For the MDM Import Manager, connect to the target system. For the MDM Syndicator, you have to maintain the destination properties.
4. Import the map.
March 2008 7
How To... Transport MDM Objects between MDM 5.5 Systems
5. Select the map file.
6. Save the map.
March 2008 8
How To... Transport MDM Objects between MDM 5.5 Systems
5. Best Practices
5.1 Initial Transport The very first transport is done by copying the development repository.
Tip You may want to minimize the manual maintenance effort, and if possible create all those objects in the development repository that are not supported yet by any transport mechanism (see table in chapter 4 [page 2)) before you run the initial transport.
Tip You may want to import all lookup tables already in the development repository before copying it, to avoid having to do it again for the target repositories. Technically, this is possible. However, it is not recommended, at least for lookup tables with key mapping. During import, a remote key is generated depending on the remote system. However, remote systems of the different landscapes differ. So, wrong remote keys would be created. Instead, copy the development repository without any master data, and apply the standard import mechanism to fill the lookup tables.
In MDM Console, duplicate the repository. Select the target server and the name of the target repository. Optionally, you could also duplicate the repository by archiving and unarchiving it.
...
March 2008 9
How To... Transport MDM Objects between MDM 5.5 Systems
5.2 Subsequent Transports In some cases, depending on the extent of modifications done in the development repository, it might be necessary to syndicate/import the complete master data before/after upgrading the repository schema. Besides this, it is recommended that you back up the data anyway, just in case. ...
1. In MDM Console, connect to the target repository, and back up the complete repository by archiving it.
March 2008 10
How To... Transport MDM Objects between MDM 5.5 Systems
2. Export the repository schema, and convert it to XSD. For more information about XSD conversion, see the how-to paper How To Generate XSD Schemas from existing MDM Repositories, available on SDN.
March 2008 11
How To... Transport MDM Objects between MDM 5.5 Systems
3. In MDM Syndicator, maintain the destination properties.
4. Choose type XML Schema File, and select the XSD schema of the current version of your target repository that was generated beforehand.
Note The data has to be syndicated for each remote system. Otherwise the remote key would be lost.
March 2008 12
How To... Transport MDM Objects between MDM 5.5 Systems
5. All master data records should be written in one single file. So, switch to tab Map Properties, and set XML File Output to Single File.
6. When all items are mapped (not shown here), execute the syndication.
7. Optional step: Only after a backup of the repository was done and the master data was syndicated, you can delete the data in the MDM Data Manager.
Note Depending on the extent of schema modifications, this step could be skipped.
March 2008 13
How To... Transport MDM Objects between MDM 5.5 Systems
8. In MDM Console, unload the target repository, and import the new source schema.
9. In MDM Import Manager, connect to the target repository, and create an import map to re-import the complete master data. Choose type XML, and select the file that was syndicated beforehand.
Note In order to preserve remote keys, data has to be imported for all remote systems.
March 2008 14
How To... Transport MDM Objects between MDM 5.5 Systems
10. Map all required fields and values (not shown here), and execute the import.
5.3 Ports and Remote Systems For MDM 5.5 SP05, there is no transport mechanism provided for Remote Systems and Ports, so they have to be manually maintained in the target systems.
As of MDM 5.5 SP06, Remote Systems and Ports are included in the export and import of the repository schema.
However, remote systems and ports within different landscapes (DEV, QA, and PROD) usually differ. So far, there is no mechanism in place that automatically maps remote systems across the different landscapes.
This leads us to two options: either maintaining remote systems and ports in the target systems or maintaining them in the source system and transport the same by exporting and importing the repository schema, for latter see chapter 4.1 [page 3]. ...
1. Option 1 (mandatory for MDM 5.5 SP05): In MDM Console, connect to the target systems, and add remote systems and respective ports.
March 2008 15
How To... Transport MDM Objects between MDM 5.5 Systems
2. Option 2 (supported in MDM 5.5 SP06 only): In MDM Console, maintain all remote systems and ports of the target landscape in the development system, and transport the same by exporting and importing the repository schema.
March 2008 16
How To... Transport MDM Objects between MDM 5.5 Systems
When importing the repository schema, you might have to reject adding remote systems and respective ports of the development landscape.
5.4 User Management You might like to have a dedicated user who is responsible for MDM transports only. This chapter shows which authorizations are necessary to carry out the respective transport tasks that were discussed in the previous chapters. ...
1. For duplicating/unarchiving repositories, you require DB access.
2. In MDM Console, create respective transport roles.
Tip You may create different roles for QA and PROD to distinguish between different transport requirements.
March 2008 17
How To... Transport MDM Objects between MDM 5.5 Systems
For exporting/importing repository schemas, grant Execute access for functions Import Schema, and Export Schema.
Note On OS level, you might have to grant read-only access to prevent the role definition in the repository schema file from being manipulated in order to bypass role restrictions.
3. For manually maintaining schema objects (such as remote systems, ports, links, XML schemas in MDM 5.5 SP05), grant Execute access for functions Add Schema Object, Modify Schema Object, and Delete Schema Object.
Switch to tab Tables and Fields, and grant Read/Write access to the respective tables.
March 2008 18
How To... Transport MDM Objects between MDM 5.5 Systems
4. For maintaining maps, at least grant Execute access to functions Add Import Maps, Modify Import Maps, Add Syndication Maps, and Modify Syndication Maps.
5. For manually maintaining validations, assignments, matching strategies, and workflows, grant Execute access to functions Add Records, Modify Records, and Delete Records.
Switch to tab Tables and Fields, and grant Read/Write access to the root node Tables and Fields.
In the upcoming pop-up you are asked whether you want to change the access setting for all tables and fields to the new default. By choosing No you do not inherit the setting to the child nodes.
For workflows, you also have to grant Read/Write access to table Workflows.
March 2008 19
www.sdn.sap.com/irj/sdn/howtoguides