Release Notes for SAP NetWeaver MDM global data synchronization option 2.0

(1)

Release Notes for SAP

NetWeaver MDM global data synchronization option 2.0

M a r c h 2 0 0 9

(2)

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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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.

(3)

Icons in Body Text

Icon Meaning

Caution Example Note

Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

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 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 text 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 text Exact user entry. 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.

(4)

March 2009 3

Release Notes for SAP NetWeaver MDM Global Data Synchronization 2.0 ... 4

Bill of Material Extraction ... 5

Graphical User Interface for Hierarchies ... 6

Migration Automation ... 7

Portal User Management... 8

Process Automation ... 9

Reporting ... 10

Value Based Authorization ... 11

Workflow ... 12

(5)

SAP NetWeaver MDM GDS 2.0 Release Notes

March 2009 4

Release Notes for SAP NetWeaver MDM Global Data Synchronization 2.0

SAP NetWeaver MDM global data synchronization (GDS) 2.0 contains new functions and enhancements. Some functions have been changed or removed. These updates are

summarized below. For details, see the relevant chapters of the SAP NetWeaver MDM GDS 2.0 application help.

(6)

March 2009 5

Bill of Material Extraction

Technical Data

Function is New

Release Software Component

Component: GDS Release: 2.0

Support Package: SP0

Country Setting Valid for all countries

Use

This feature allows you to make use of pre-defined complex material hierarchies, bill of materials (BoMs), in their SAP ERP backend system.

GDS can now receive BoM information from an SAP ERP backend system via the BoM ALE (Application Link Enabling) scenario. Trade items are created automatically from this

information. The complex packages or inner packs that make up a pallet or case no longer have to be created by you in the GDS console, saving you time and effort.

The solution is delivered with a documented example of a sales BoM that you can use as an example to set up the process according to your needs.

(7)

March 2009 6

Graphical User Interface for Hierarchies

Technical Data

Function is New

Support Package: SP0 Country Setting Valid for all countries

Use

This function gives you an overview of all the packaging hierarchies where a specific trade item is used.

You can use the graphical user interface for hierarchies to:

Display on one screen all the packaging hierarchies where a trade item is used Display hierarchies in a simple tree format

Display a trade item’s most important attributes in a pop-up by placing your mouse over the trade item

These features make handling trade item hierarchies more efficient and user-friendly.

(8)

March 2009 7

Migration Automation

Technical Data

Function is New

Use

Migration automation enables you to upgrade easily from your productive GDS 1.0 SP06 solution to GDS 2.0. As well as enabling a smooth transition from GDS 1.0 to 2.0, this feature reduces the number of manual tasks required for upgrading.

The configuration tool delivered with this solution allows for the following:

Easy migration of a GDS 1.0 repository Uploading of custom XML configuration files Monitoring of the migration of trade items

(9)

March 2009 8

Portal User Management

Technical Data

Function is New

Use

You can deploy GDS 2.0 in an SAP NetWeaver Portal. This allows the deeper integration of GDS related tasks into existing roles and responsibilities, and further reduces the total cost of ownership (TCO), for example, by enabling the usage of single sign-on (SSO).

(10)

March 2009 9

Process Automation

Technical Data

Function is New

Support Package: SP0

Country Setting Valid for all countries

Use

GDS 2.0 gives you the option of automating the following processes:

Validation of trade items received from a back-end system, and assignment of the status Ready to Register to trade items

Registration of successfully validated trade items with the Global Data Synchronization Network (GDSN)

Correction of modified trade items that have already been published

Process automation significantly decreases the amount of manual work needed to prepare trade items for publication and further reduces the maintenance effort required for published trade items.

You can switch these automatic processes on and off separately, and you can also exclude items from the process with a checkbox in the Trade Item Details screen.

(11)

March 2009 10

Reporting

Technical Data

Function is New

Use

As of GDS 2.0, you can use the Master Data Management (MDM) application programming interface (API) to communicate with business intelligence (BI) solutions to gather information on GDS relevant details such as determining how many items were synchronized with a specific trading partner.

This is the foundation for cross application key performance indicator (KPI) analyses that include GDS information.

The solution is delivered with a documented example of how an extractor should be designed, and how a report could look.

(12)

March 2009 11

Value Based Authorization

Technical Data

Function is New

Use

GDS 2.0 allows you to authorize access to trade items based upon the values assigned to certain trade item attributes. This feature makes it easier for you to handle trade item

hierarchies and also makes the process more efficient. Value based authorization is available in most back-end systems where access is granted based upon responsibility for brand x, category y, sales organization z, and so on.

The solution is capable of restricting access on the basis of specific values for the following selected attributes:

Target Market Brand Name Brand Owner Information Provider

(13)

March 2009 12

Workflow

Technical Data

Function is New

Use

As of GDS 2.0, you can use the MDM workflow engine to assign tasks to others in your organization, and monitor the progress of tasks. A workflow cockpit has been added to the user interface of the GDS console.

Standard workflow templates are available for the following:

Import Trade Item Trade Item Creation Item Modification Automation Process

Unprocessed Messages (Registration, Publication, Link, and Import Error) Manual Assignment

The following capabilities are also available:

Existing workflow templates can be extended New workflow templates can be created

For the enhancement and modification of workflows, a Microsoft Visio Developer license is required.