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.

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.

http://service.sap.com/instguides

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.

http://help.sap.com/saphelp_nwmdm71/helpdata/en/b1/6a72de6f0f445ab3c8eabc9b7e740f/frameset.htmhttp://help.sap.com/disclaimer?site=https://service.sap.com/%7Esapidb/011000358700001204292013E

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

For complex types it is (please see example in TMData.xsd attached):

For multi-language fields:

Syntax

http://help.sap.com/javadocs/mdm71/

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