SAP NetWeaver Master Data Management · PDF fileSAP NetWeaver Master Data Management GDS 2.1...
Transcript of SAP NetWeaver Master Data Management · PDF fileSAP NetWeaver Master Data Management GDS 2.1...
Best Practices
SAP NetWeaver Master Data Management GDS 2.1
Document Version: 1.0 – 2015-11-12
CUSTOMER
SAP NetWeaver Master Data Management GDS Data Migration Based on the MDM Syndication Tool and Import Manager
2
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Typographic Conventions
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .
SAP NetWeaver Master Data Management
Document History
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You can
find the latest version at the following location http://service.sap.com/instguides.
The following table provides an overview of the most important document changes.
Version Date Change
1.04 2015-11-12 Initial version.
4
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Contents
Contents
1 Introduction .................................................................................................................................................... 5 1.1 Attributes to be Migrated ........................................................................................................................................ 5 1.2 Prepare the Destination Data Structures in the Repository ................................................................................ 5
2 Export Existing Data ...................................................................................................................................... 6 2.1 Exporting Lookup Tables with a Remote Key ....................................................................................................... 7 2.2 Exporting with the Syndicator Tool from the Source Repository ....................................................................... 8
3 Import Data .................................................................................................................................................... 11 3.1 Copy Mode: Copying all Full Trade Items ............................................................................................................ 12 3.2 Copy Mode: Delta Changes Only .......................................................................................................................... 13 3.3 Import Multilingual Fields ..................................................................................................................................... 14 3.4 Importing Lookup Tables ...................................................................................................................................... 15 3.5 Define Key Fields ................................................................................................................................................... 15 3.6 Actions on Match ................................................................................................................................................... 16
4 Frequently Asked Questions - FAQs .......................................................................................................... 17
5 Non-Flex to Flex Data Transport Use Case – Field: Stacking Factor .................................................... 18 5.1 Existing Source from the MDM Console .............................................................................................................. 18 5.2 Destination Structure from the 1WS Datasource Guide .................................................................................... 18 5.3 Copy Plan Stacking Factor.................................................................................................................................... 19 5.4 Copy Plan Maximum Stacking Weight ................................................................................................................. 19
6 Import to Stacking Factor .......................................................................................................................... 20
7 Non-Flex to Flex Data Transport Use Case – Field: EANUCC ................................................................. 21 7.1 Existing Source from MDM Console .................................................................................................................... 21 7.2 Destination Structure from the 1WS Datasource Guide .................................................................................... 22 7.3 Copy Plan EANUCC Fields .................................................................................................................................... 23
8 Import EANUCC ........................................................................................................................................... 24
9 Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per
Trade Item ..................................................................................................................................................... 25 9.1 Existing Source from the MDM Console .............................................................................................................. 25 9.2 Destination Structure from the 1WS Datasource Guide .................................................................................... 26 9.3 Copy Plan PiecesPerTradeItem/UnitsPerTradeItem Fields ............................................................................. 28
10 Import UnitsPerTradeItem AQM ................................................................................................................29
SAP NetWeaver Master Data Management
Introduction
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
1 Introduction
This guide outlines the required steps for moving data from a source MDM repository to a destination MDM
repository using the following MDM standard tools:
MDM Console (at least SP10)
MDM Syndicator Tool (at least SP10)
MDM Import Manager (at least SP10).
More Information
See the following guides:
MDM Syndicator Reference Guide
MDM Import Manager Reference Guide.
1.1 Attributes to be Migrated
Prepare a list of attributes to be migrated to a new structure. This list depends on the modules that you want to
implement in the system. After the migration is confirmed to be successful and the data is in the destination
structure, it is recommended that you remove the source attribute.
1.2 Prepare the Destination Data Structures in the Repository
Deploy the modules to create the data structures in the MDM repository. This step is necessary for data
migration. Note that we consider the source and the destination to be the same in the MDM repository. For new
customers the source is the initial repository.
After this step, data is available in the existing old structure and the new data structures are deployed but empty.
6
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Export Existing Data
2 Export Existing Data
A definition.xsd is necessary for the MDM Syndicator Tool to export data in a structured way. It can be generated
from the repository definition through MDM Java API or can be created manually. As for the Java API, see the
MDM Java API documentation at http://help.sap.com/javadocs/mdm71/.
For simple cases manual creation is recommended.
The xsd should list the attributes that are affected by the migration in the following syntax:
Syntax
<element name="FieldCode" type="string"/>
For complex types it is (please see example in TMData.xsd attached):
<element name="ComplexFieldCode" minOccurs="0"
maxOccurs="unbounded"><complexType><sequence>
<element name="FieldCode1" type="string"/>
<element name="FieldCode2" type="string"/>
<element name="ComplexFieldCode2"><complexType><sequence>
<element name="SubFieldCode1" type="string"/>
<element name="SubFieldCode2" type="string"/>
</sequence></complexType></element>
For multi-language fields:
Syntax
<element name="MultiLangFieldCode" minOccurs="0" maxOccurs="unbounded">
<complexType>
<sequence>
<element name="Value" type="string"/>
<element name="Language" type="string"/>
</sequence>
</complexType></element>
SAP NetWeaver Master Data Management
Export Existing Data
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
MDM Syndicator Tool – Split Field by Value
MDM Syndicator Tool – Mapping to xml Format
The data will be moved to the xsd/xml structure. See the TMData.xsd file in SAP Note 2228174.
2.1 Exporting Lookup Tables with a Remote Key
You must have a remote key element in the xml schema file. See the Parties.xsd file in SAP Note 2228174.
You can select the remote key values for exporting.
8
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Export Existing Data
MDM Syndicator Tool – Remote Key Settings
2.2 Exporting with the Syndicator Tool from the Source Repository
Procedure
1. Start the MDM Syndicator Tool.
2. Choose File→New.
3. Select the xml schema file and specify the xml definition (.xsd). The following illustration shows an example
of the MDM_MappingStacking.xsd:
SAP NetWeaver Master Data Management
Export Existing Data
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
MDM Syndicator Tool – New Export Mapping
4. You must identify the trade item under the GTIN, Target Market, and Information Provider fields (these three
values represent the key to uniquely identify a trade item).
This is the minimal set of information required.
5. You must also decide what should be exported from the source repository. Use the Syndicator Tool for item
mapping.
Example of Syndicator Tool Key-Based Mapping
The use of a single export file is recommended because it simplifies the import process later on. The single file
contains all of the MDM entries that can be handled by a single import process.
You can perform this task multiple times. If at a later date any further data migration is necessary, then you
can execute this step again. You can enter the starting characters of an attribute and the tool will select the
attribute in Item Mapping.
10
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Export Existing Data
MDM Syndicator Tool – Output to One File
SAP NetWeaver Master Data Management
Import Data
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
3 Import Data
Prerequisites
You have imported the xsd schema to the repository from the MDM Console. For example, TMData.xsd.
MDM Console – Add xml Schema
Procedure
1. In the MDM Console, configure the XML Schema Name. For example, TradeItem Stacking factor migration.
2. Start the MDM Import Manager.
3. Select the xml schema with the same name as the one in the MDM Console. For example, TradeItem Stacking
factor migration. The source file in the File Name field is the output of the Syndicator Tool that you exported at
the end of the export process.
12
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import Data
MDM Import Manager – New Import Source
4. Select the source and the destination tables. In most cases you will use TM Data.
MDM Import Manager – Destination Table Selection in the Repository
3.1 Copy Mode: Copying all Full Trade Items
Procedure
1. Copy all trade items and attributes to a new, empty repository.
2. On the Configuration menu, choose Options. Change the Find Matching Field Type to Normalized.
SAP NetWeaver Master Data Management
Import Data
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 13
MDM Import Manager – Type Must be Normalized
When you import all of the attributes, then you can use the auto map feature of MDM Import Manager. Configure
the following:
1. Select the Map Fields/Values tab and choose AutoMap as the initial mapping. The Qualified tables may have
invalid mapping. Review as required.
MDM Import Manager – Mapping Fields
3.2 Copy Mode: Delta Changes Only
When you only want to copy some fields to a new destination, map the delta changes only.
Note
For mapping lookup values each single value must be mapped.
14
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import Data
MDM Import Manager – Mapping Fields and Lookup Values
3.3 Import Multilingual Fields
MDM Import Manager – Configuration: Multilingual Text Fields as Repeating Structures
SAP NetWeaver Master Data Management
Import Data
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15
MDM Import Manager – Mapping Multilingual Fields
3.4 Importing Lookup Tables
Select the destination lookup table and create mapping for values and lookups.
MDM Import Manager – Lookup Tables
3.5 Define Key Fields
TMData uses a combined key consisting of GTIN, Information Provider, and Target Market; lookup tables use a
simple key that can be a remote key or a name.
16
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import Data
MDM Import Manager – Key Fields for Identifying Records
3.6 Actions on Match
MDM Import Manager – Match Records
Procedure
1. In Copying All Trade Items mode, use None, Match, and Create.
2. In Delta Changes Only mode, use Exact, Match, and, Update (all mapped fields).
3. Execute the import after the above steps.
4. After the successful and confirmed migration of data to the destination data structure, it is highly
recommended that you remove the source attribute.
SAP NetWeaver Master Data Management
Frequently Asked Questions - FAQs
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 17
4 Frequently Asked Questions - FAQs
You cannot execute the import
The Import Status tab displays the message Action Items…. It describes the blocking point in the import.
Check the following:
o the qualified lookup mapping (qualifiers and qualified fields mapped in two different mapping nodes)
o the lookup value mapping.
Import Manager – Action Items to Finish the Import
What should I do with the old unused source data fields?
o After the successful and confirmed migration of data to the destination data structure, it is highly
recommended that you remove the source attribute.
18
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Non-Flex to Flex Data Transport Use Case – Field: Stacking Factor
5 Non-Flex to Flex Data Transport Use Case – Field: Stacking Factor
Prerequisites
See sections 2 Export Existing Data and 3 Import Data above.
5.1 Existing Source from the MDM Console
TMData - StackingFactor
MDM Console – Current (Source) Stacking Factor Field
5.2 Destination Structure from the 1WS Datasource Guide
TMData – TradeItemStacking: StackingFactor
SAP NetWeaver Master Data Management
Non-Flex to Flex Data Transport Use Case – Field: Stacking Factor
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 19
5.3 Copy Plan Stacking Factor
Source: TMData→StackingFactor
Destination: TMData→TradeItemStacking→Stacking Factor
5.4 Copy Plan Maximum Stacking Weight
Source: TMData→MaxStackingWeight & MaxStackingWeightUOM
Destination: TMData→TradeItemStacking→StackingWeightMaximum→Value & Qualifier
Export (Mapping in Syndicator Tool)
Syndicator Tool - Mapping
You can execute the export after the steps in the StackingFactor.xml file. See the StackingFactor.xsd
file in SAP Note 2228174.
Save the mapping in the Syndicator Tool Output.
20
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import to Stacking Factor
6 Import to Stacking Factor
Prerequisites
See section 3 Import Data.
Procedure
1. Create the import field and value mapping for the fields.
Import Manager – Import Mapping to the Destination Structure
2. Execute the import.
3. Verify the data in the destination structure.
SAP NetWeaver Master Data Management
Non-Flex to Flex Data Transport Use Case – Field: EANUCC
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 21
7 Non-Flex to Flex Data Transport Use Case – Field: EANUCC
Prerequisites
See sections 2 Export Existing Data and 3 Import Data
See the TMData.xsd file in SAP Note 2228174.
o TMData definition for Eanucc codes.
7.1 Existing Source from MDM Console
TMData – EANUCCodes
MDM Console – Current (Source) EANUCC Fields
22
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Non-Flex to Flex Data Transport Use Case – Field: EANUCC
7.2 Destination Structure from the 1WS Datasource Guide
TMData – GS1TradeItemIdentificationKey – Code,Type isBarcodeSymbologyDerivable
1WS Datasource Guide – EANUCC Fields
MDM Console – Destination Structure
SAP NetWeaver Master Data Management
Non-Flex to Flex Data Transport Use Case – Field: EANUCC
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 23
7.3 Copy Plan EANUCC Fields
Source: TMData→EANUCCCodes→Code,Type isBarcodeSymbologyDerivable
Destination: TMData→GS1TradeItemIdentificationKey→Code,Type isBarcodeSymbologyDerivable
Export (Mapping in Syndicator Tool)
Syndicator Tool - Mapping
Execute the export after the steps in the ExportEanucc.xml file. See the ExportEanucc.xml file in SAP
Note 2228174
Save the mapping in the Syndicator Tool Output.
24
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import EANUCC
8 Import EANUCC
Prerequisites
See section 3 Import Data.
Procedure
1. Create the import fields and value mappings for the fields.
Import Manager – Import Mapping to the Destination Structure
Import Manager – Mapping of Lookup Values
2. Execute the import.
3. Verify the data in the destination structure.
SAP NetWeaver Master Data Management
Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per
Trade Item
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 25
9 Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per Trade Item
Prerequisites
See sections 2 Export Existing Data and 3 Import Data
See the TMData.xsd file in SAP Note 2228174.
o TMData definition for Units Per Trade Item.
9.1 Existing Source from the MDM Console
TMData – Pieces Per Trade Item, UOM
MDM Console – Current (Source) Pieces Per Trade Item fields
26
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per
Trade Item
9.2 Destination Structure from the 1WS Datasource Guide
TMData – Units Per Trade Item - AQM
1WS Data Source Guide – Units Per Trade Item
SAP NetWeaver Master Data Management
Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per
Trade Item
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 27
MDM Console – Destination Structure
28
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Flex AQ to Flex AQM Data Transport Use Case – Field: Pieces Per Trade Item to Units Per
Trade Item
9.3 Copy Plan PiecesPerTradeItem/UnitsPerTradeItem Fields
Source: TMData→PiecesPerTradeItem,UOM
Destination: TMData→UnitsPerTradeItem→Value,Qualifier
Export (Mapping in Syndicator Tool)
Syndicator Tool - Mapping
Execute the export after the steps in the ExportUnitsPerTradeItems.xml file in SAP Note 2228174
Save the mapping in the Syndicator Tool Output.
SAP NetWeaver Master Data Management
Import UnitsPerTradeItem AQM
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 29
10 Import UnitsPerTradeItem AQM
Prerequisites
See section 3 Import Data.
Procedure
1. Create the import field and value mappings for the fields.
Import Manager – Import Mapping to the Destination Structure
30
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Master Data Management
Import UnitsPerTradeItem AQM
Import Manager – Lookup Value Mapping
2. Execute the import.
3. Verify the data in the destination structure.
SAP NetWeaver Master Data Management
Import UnitsPerTradeItem AQM
CUSTOMER
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 31
MDM Data Manager – Data is Copied to the Destination
www.sap.com/contactsap
© 2015 SAP SE or an SAP affiliate company. 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 SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see http://www.
sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.