SAP NetWeaver
Master Data Management (MDM)
Product Information Management with MDM
SAP NetWeaver Product Management, SAP AG
July 2009
1. What is Product Information Management (PIM)
1.1. Definition and Business Drivers
1.2. SAP’s Take and Positioning
2. PIM Capabilities of SAP NetWeaver MDM
2.1. Product Data Management
2.2. Data Outbound Channels
3. Print Publishing: Overview and Outlook
4. Summary
Legal Disclaimer
This presentation outlines our general product direction and should not be relied on in
making a purchase decision. This presentation is not subject to your license
agreement or any other agreement with SAP. SAP has no obligation to pursue any
course of business outlined in this presentation or to develop or release any
functionality mentioned in this presentation. This presentation and SAP's strategy and
possible future developments are subject to change and may be changed by SAP at
any time for any reason without notice. This document is provided 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 assumes no responsibility for errors or omissions in this document and shall
have no liability for damages of any kind that may result from the use of these
materials, except if such damages were caused by SAP intentionally or grossly
negligent.
“
Definition
Product Information Management
or PIM refers to
processes and
technologies focused on centrally managing information about
products, with a focus on the data required to market and sell
the products through one or more distribution channels
. A
central set of product data can be used to feed consistent, accurate
and up-to-date information to multiple output media such as web
sites, print catalogs, ERP systems, and electronic data feeds to
trading partners. PIM systems generally need to support multiple
geographic locations, multi-lingual data, and maintenance and
modification of product information within a centralized catalog to
provide consistently accurate information to multiple channels in a
cost-effective manner.
Complex product and
relationship management
Key Mapping management
Print/web publishing including
layout and production
GEAR
Parts
1038-GID
Product Information Management
One view of product information anytime anywhere
A124K
Parts
GEAR
Publish
Gears
BR-2K
SPIDER
GEAR
Drivers for Product Information Management
Product Data Management (High Tech)
Maintaining a single part master code costs an average of $1000 per year.
For a company with 10,000 part masters, 10% duplicate data, and 10 connected systems,
each of which costs $50k per year to connect, the total savings potential is at least $1.5
million per year.
Publication (Industrial Catalogs)
An industrial catalog with 3000 pages, 200,000 items,
and a 65-person production staff costs about $1 million
to layout and $30 to print for each copy.
For a catalog published once a year, the savings are
between $1 million and $2 million.
PIM Requirements
Objectives for a product catalog and publishing system
Store and structure rich product data content
Create a classification taxonomy with category-specific attributes
Store and manage product relationship information
Store images and unstructured content
Import raw data from a variety of sources
Maintain data integrity
Syndicate and publish content to a variety of formats
Obtain a high performance when searching and locating products in
a variety of ways, even in very large catalogs containing millions of
products.
Provide a user-friendly application whose features are
comprehensive and intuitive to use.
Master Data Management Cycle
with Special Focus on Product Information Management
Import and integrate
XML, Excel, Access,
ODBC, Oracle, SQL,
Manual and automated
field mapping
Organize
Model product
repository
Maintain taxonomies
and attributes
Support exchange
formats and
classification systems
(BMEcat, UNSPSC
etc.)
Publish and syndicate
Define product families
Define publication layout
Transfer to Adobe
InDesign or Web shop
Populate client systems
Enable buy-side/sell-side
Optimize
De-duplicate
Control key mapping
Compare records
Edit records
Enrich records
Organize
Optimize
Import and
integrate
Publish
and
syndicate
SAP
NetWeaver
MDM
1. What is Product Information Management (PIM)
1.1. Definition and Business Drivers
1.2. SAP’s Take and Positioning
2. PIM Capabilities of SAP NetWeaver MDM
2.1. Product Data Management
2.2. Data Outbound Channels
3. Print Publishing: Overview and Outlook
4. Summary
Import Product Data
Key Capabilities to Manage Product Content
Complex Data Modeling Elements
Hierarchies
Categories and Attributes
Tables and Fields
Support for multi-object repositories
Multiple business objects (=main tables) can reside in one and the same repository
E.g. supplier and product data can be stored in one repository
Records of different main tables can reference each other
(
new field type “Lookup [Main]”)
E.g. a supplier can be related to several products
Main tables can share the same customizing/lookup tables
E.g. the main tables “customers” and “suppliers” can be connected to the table “countries” in
order to ensure consistent information about the country of origin of both business partners
Support for nested structures
Composite data type
tuple
allows modeling of nested structures
E.g. product capacity information depending on plant and location or
multiple addresses of a business partner can hold
multiple phone numbers
© SAP 2008 / Page 12
Key Capabilities to Manage Product Content
Supports external and internal classifications
SAP CRM, SAP SRM, SAP R/3 categories/hierarchies
eClass
UNSPSC
Assignment of product records to multiple classes (especially
within the same class of SAP R/3)
Assignment of product records to inner node classes in SAP R/3
(hierarchy fields)
Supports standard catalog data exchange formats like BMEcat
Classification Support
Key Capabilities to Manage Product Content
Key Capabilities to Manage Product Content
Data Management Workflow
Enables the orchestration of parallel
and sequential activities at the data
management level, including user
tasks, validations and approvals
User-friendly design-time environment
allows quick and easy creation and
manipulation, even by end users
Groups of records can be moved
through the workflow at runtime as
logical packages, providing quick
access to the relevant data
Flexible agent assignment based on
users or roles
Embedded validations for data quality
checks at any time in the process
Key Capabilities to Manage Product Content
Mass maintenance
Validations
Updates
Interactive record comparison
Rules-based matching/Key mapping
Data enrichment
Digital asset management
PartsRiver, Inc. – Focusing on product
master data; industry-specific data
classification services
Product masks
Access Option: Portal or UI clients
SAP NetWeaver MDM allows you to
Access your central product repository using SAP Portal
to create, read, update, or delete data
Use the SAP Data Manager as a data steward’s fully administrative environment for data
processing
Outbound Channels
Open Catalog Interface
Standard interface to connect SAP Business
Suite applications (e.g. SAP SRM)
Portal-based iView or
Web Dynpro-based UI
Print Publishing
MDM Publisher, DTP-Plug-in
DTP Finalization
Print APIs for third party publishing
Syndication
MDM Syndicator
Process Integration
Web
OCI
Syndication
Web publishing
APIs to provide Web access to repository
For use in a non-SAP environment
Web Publishing (APIs)
APIs to retrieve repository data and expose it as a Web application
Visit
Print Publishing
From Table View to Final Pages…
Partitioning
Promotion / demotion
Pivots
Styles
Reordering
Manual adjustments
Syndication
Record Selection and Target Determination
SAP Open Catalog Interface
Communication between SAP system and catalog (MDM repository)
iViews to integrate MDM
repository with SAP
NetWeaver Portal
Portal-independent Web
Dynpro-based UI
OCI to enable shopping
mode
1. What is Product Information Management (PIM)
1.1. Definition and Business Drivers
1.2. SAP’s Take and Positioning
2. PIM Capabilities of SAP NetWeaver MDM
2.1. Product Data Management
2.2. Data Outbound Channels
3. Print Publishing: Overview and Outlook
4. Summary
MDM Publisher – Creating Complex Page
Layouts for Print Catalogs
Consolidate
Product Data
Import
Product Data
Enable
Catalog Publishing
Manual import
Automated import
Field and value
mapping
Validate
Enrich
De-duplicate
Manage images
Define families
(catalog partitioning)
Transfer to DTP
Create default
layouts
Assign style to
fields and attributes
Create publication
structure
Create publication
layouts and styles
Define
Print Layout
Finalize
composition
Print Process: Main Steps 1/6
MDM Console – Family Field Settings
Family Field –
Determines
initial
partitioning of
products.
Family Field –
Determines
initial
partitioning of
products.
Print Process: Main Steps 2/6
MDM Data Manager – Family Mode
Family
Hierarchy
Pane
Family
Hierarchy
Pane
Family
Results
Pane
Family
Results
Pane
Family
Partitioning
Tab
Family
Partitioning
Tab
Print Process: Main Steps 3/6
MDM Publisher – Family Hierarchy
Family
Hierarchy
Pane
Family
Hierarchy
Pane
Print Process: Main Steps 4/6
MDM Publisher – Publication Hierarchy
Publication
Hierarchy
Pane
Publication
Hierarchy
Pane
Families –
Sources Pane
Families –
Sources Pane
Print Process: Main Steps 5/6
MDM Publisher - Spread Editor
Spread Editor
Pane
Spread Editor
Pane
Section/ Page
Thumbnail
Hierarchy Pane
Section/ Page
Thumbnail
Hierarchy Pane
Master Pages
Pane
Master Pages
Pane
Template
Sources Pane
Template
Sources Pane
Measurements
Palette
Measurements
Palette
Print Process: Main Steps 6/6
MDM Adobe InDesign Plug-in
MDM
InDesign
Plug-in
MDM
InDesign
Plug-in
Consolidated Data for Print Publications
Printed catalogs made easy
Automation
Creative
Design
Final
DTP
Clean
data
Publishing features include:
Clean data basis
By seamlessly integrating with
MDM repository
Leverage MDM data quality features
Semi-automation in data publishing
Predefined output
and page layout
Page maximization
Creative design
Manual intervention for
layout definition and adjustments
Adobe InDesign Plug-in
DTP Finalization
Open interface to third-party
publishing software
Adobe
InDesign
3rd party
publishing
SW
3rd party
publishing
SW
MDM
© SAP 2007 / Page 32
MDM Publisher - Key MDM 7.1 Features
Publisher Java API
To further leverage XML print output based on MDM Publisher settings (e.g. for further use in 3rd party Web
publishing)
To provide the foundation for comprehensive print publishing alternatives (connect to 3
rdparty publishing software)
Copy/paste properties from one node to another
Enables copy/paste of node properties (item properties, table layout, item ordering, etc.), on a granular level from one
family/publication node to another and/or to parent nodes/publication root
Free-form Styling
Possibility to directly access each text object on spread to make character style edits/overrides to individual objects
Record Set Publications
Possibility to select “random” records to display in a single presentation
In addition, these record-set presentations may be sequenced in accordance with an existing hierarchy which is
different than the look-ups used in partitioning the family hierarchy
Image Links Palette
Pane providing the user with information about images used in each presentation
Information provided is the same as listed in the images table in MDM Data Manager
Percentage Field in Measurements Palette
Setting an exact percentage for decreasing or increasing the size of a particular image on the spread
Refresh Reconciliation – Enhancing DTP Refresh Features
Specifically applies when deleted and purged objects are regenerated on the spread
Ensures reliable refreshing of these objects in the DTP
© SAP 2007 / Page 33
MDM Publisher - Key MDM 7.1 Features
Publisher Java API
Publisher Java API
Allows the user to follow some basic scenarios for setting and/or retrieving layout properties and existing publication
information. The final output for this is XML which is based on publication information existing within MDM Publisher.
Enables non-MDM Publisher based publication creation using third party software.
API
XML
API
3rd Party
Publishing
SW
Output
channel
Output
channel
Output
channel
MDM
Publisher
Output
channel
MDM
XML
© SAP 2007 / Page 34
MDM Publisher - Key MDM 7.1 Features
Copy/paste properties from one node to another
Enables copy/paste of node properties (item properties, table layout, item ordering, etc.), on a granular level from one
family/publication node to another and/or to parent nodes/publication root
© SAP 2007 / Page 35
MDM Publisher - Key MDM 7.1 Features
Free-form Styling
© SAP 2007 / Page 36
MDM Publisher - Key MDM 7.1 Features
Record Set Publications
Possibility to select “random” records to display in a single presentation
In addition, these record-set presentations may be sequenced in accordance with an existing hierarchy which is
different than the look-ups used in partitioning the family hierarchy
© SAP 2007 / Page 37
MDM Publisher - Key MDM 7.1 Features
Image Links Palette
Pane providing the user with information about images used in each presentation
Information provided is the same as listed in the images table in MDM Data Manager
© SAP 2007 / Page 38
MDM Publisher - Key MDM 7.1 Features
Percentage Field in Measurements Palette
1. What is Product Information Management (PIM)
1.1. Definition and Business Drivers
1.2. SAP’s Take and Positioning
2. PIM Capabilities of SAP NetWeaver MDM
2.1. Product Data Management
2.2. Data Outbound Channels
3. Print Publishing: Overview and Outlook
4. Summary
Product Information Management Checklist
Essential Capabilities
SAP NetWeaver MDM
Centralized repository
Flexible repository schema and taxonomy editing
Rich product content (parametric data, product relationships, etc.)
Intelligent image management
Integrated product search engine (with performance acceleration)
Powerful aggregation and cleansing
Cross-media publishing (including both Web and print)
Syndication and synchronization
Enterprise integration (APIs)
Integrated workflow and validation engine
Horizontal applicability (sell-side, buy-side, etc.)
Role-based security and user rights management (including LDAP)
Cross-platform compatibility (O/S, DBMS, API)
Summary
SAP NetWeaver Master Data Management
Facilitates flexible product information management
For use in SAP and non-SAP environments
Featuring multi-channel publication (e.g. syndication, electronic catalogs, print catalogs)
Offering a complete end-to-end solution from data input, data processing and data output
Is a player in the print market
Featuring own print solution and ability to integrate 3rd party offerings
Relevant Links:
SAP NetWeaver MDM 7.1 Information on SDN
(https://www.sdn.sap.com/irj/sdn/nw-masterdatamanagement)
eBook Featuring Preview of Print Publishing with SAP NetWeaver MDM 7.1
(https://www.sdn.sap.com/irj/sdn/nw-mdm?rid=/library/uuid/e06b0fda-ca6a-2b10-adad-cc539e2634f0)
eBook Featuring Print Publishing Novelties with SAP NetWeaver MDM 5.5 SP6 Patch 1
(https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a04b8c34-6fd2-2a10-76b7-a4a4120883bb)
How-to Guides on Print Publishing
Part one
(https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90f05885-162c-2c10-fba6-fffae9623388)
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.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. 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
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.
