Business Scenarios Powered by SAP NetWeaver MDM

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nwmdm71/helpdata/en/5c/d3af42a6f6cb6ae10000000a155106/content.htm
Created on July 30, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 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. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 5
Table of content
1 Business Scenarios Powered by SAP NetWeaver MDM
1.1 Rich Product-Content Management
1.1.1 Importing Product Data
1.1.2 Re-categorizing and Enriching Product Data
1.1.3 Providing Catalog Content
1.1.4 Enabling Print Publishing
1.2 Customer Data Integration
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 5
1 Business Scenarios Powered by SAP NetWeaver MDM
In addition to the Master-Data Consolidation, Master-Data Harmonization, and Central Master-Data Management IT scenario variants, SAP NetWeaver Master Data
Management also features the business scenarios described in the following sections.
1.1 Rich Product-Content Management
Purpose
Rich product-content management with SAP NetWeaver MDM targets specifically at centralized product content management and multi-channel publishing. It
allows you to import and export product data, centrally manage content, and create custom print catalogs, Web catalogs, or expose an MDM product repository to
a business application through the Open Catalog Interface (OCI). As a result, MDM capabilities are extended with business processes such as product
introduction, cataloguing and publishing.
Process Flow
This business scenario includes the following processes:
1. Importing Product Data
2. Re-categorizing and Enriching Product Data
3. Providing Catalog Content
4. Enabling Print Publishing
1.1.1 Importing Product Data
Purpose
Using this process, you start the upload of product master data (flat files) from the specified remote system, or product information from suppliers (Excel, TXT) to
MDM.
Prerequisites
The following basic requirements must be fulfilled:
Repository has been set up and import maps have been created
Inbound port has been defined (MDM Console)
Inbound source data is staged in the inbound port
Process Flow
The process runs in the MDM Import Server*
1. System imports data from inbound port
Once the data has been delivered to a specific inbound port, it will automaticallybe picked within a configurable time interval and queued up for import
processing.
2. System transforms, maps, and matches data
The MDM Import Server maps and matches imported data to the repository structure.
* MDM Import Server enables fully automated data imports. It is an additional component to MDM Import Manager (used for manual imports) and MDM Import
Manager Batch (used for batch imports).
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 5
1.1.2 Re-categorizing and Enriching Product Data
Purpose
Using this process, you re-categorize product categories and complete product information in MDM.
Process Flow
This process runs as follows:
1. Search and merge identical records interactively (MDM Data Manager)
The MDM Data Manager provides different search patterns for the end user (tree search, keyword search, free search). Based on the search results,
identical records can be determined and merged interactively.
2. Re-categorize and enrich records (MDM Data Manager)
In the MDM Data Manager you can check if new data has been attached to the correct category in taxonomy, and re-categorize it if necessary. In addition,
you can enrich data with additional information
In the MDM Data Manager, custom validations can be applied to check master data updates. In addition, a workflow can be triggered to support change
processes
3. Add images to catalog (MDM Image Manager)
4. If images are needed as additional information for repository items, they can be imported and processed using the Image Manager.
5. System creates image variants (MDM Image Manager)
For each image imported into the repository, image variants (which can be predefined in the MDM Console, for example, thumbnails 300x300) are created
and stored in the repository in addition to the original image.
6. Connect image variants to products (MDM Data Manager)
In the MDM Data Manager, you connect the image to the product (via copy or link).
1.1.3 Providing Catalog Content
Purpose
Using this process, you can choose optional means of syndication instead of print publishing, for example Web publishing or exposure of an MDM product
repository to a business application (such as mySAP SRM) through the Open Catalog Interface (OCI).
Process Flow
This process runs as follows:
1. Provide content via OCI
This is an optional step which applies when an MDM product repository is to be exposed to a business application through the Open Catalog Interface
(OCI).
Using OCI, you can call an MDM repository and search for products, add the required items to a selection list, transfer these to the shopping cart of the
business application and complete the order.
For more information about how to integrate an MDM product repository via iViews, see OCI Subscriber.
2. Develop Web Catalog
This is an optional step to be applied for Web publishing using APIs.
As a prerequisite, a Web application has been created which uses MDM API to search, read and maintain the repository content. The Web application has
been deployed on a Web server with open connection to the MDM catalog. The API provides access to the repository.
1.1.4 Enabling Print Publishing
Purpose
Using this process, you compose and set-up printed product catalogs using the MDM Publisher.
Note
As an alternative, you can also use the Java API for Publishing for print publishing purposes. For more information, see Java API for Publishing.
Process Flow
This process runs as follows:
1. Create family table to enable initial partitioning (MDM Console)
2. Define further category partitioning (MDM Data Manager)
Catalog printing is based on category-dependent pages. Often, different product groups in a category have different layout. In this case, these categories
can be partitioned based on the content (field or attribute values) to create product families.
3. Assign catalog default settings for publication (MDM Publisher)
In this step, you assign default settings to create a common layout structure for the publication. Layout settings are inherited throughout the family hierarchy.
It is very useful to define default layout settings on the highest level possible. These settings can be overwritten on lower levels.
4. Arrange product layout per family (MDM Publisher)
In this step, you arrange a specific layout for the given product family, for example:
Eliminate redundancies
Apply printed version display name
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 5
Structure tables
It is useful to define the layout on the highest possible level of the family hierarchy.
5. Collect families or non-family based records for publication (MDM Publisher)
For starting publishing activities, a collection of families or non-family based records can be defined as a publication.
In the publication hierarchy, you can make further adaptations which are then only relevant for a given publication. Unlike the family hierarchy, a publication
hierarchy is not fixed to the repository's taxonomy. Instead, it is an organization entirely of your own creation. You are free to add, delete, move, and split
nodes to create a structure that is right for the catalog you want to produce.
In the spread editor you specifically concentrate on page layout and design, for example, you can use master pages and create layout templates for the
publication, and make spread-specific layout adjustments..
6. Publish to DTP (MDM Publisher - DTP Plug-in)
7. Finalize layout (DTP application)
In the DTP application (Adobe InDesign) several finalizing steps can be done, for example, specialized format changes.
All finalization settings can be saved with the publication in MDM and re-used with the next publishing run.
8. Create publication index (MDM Indexer)
An index for the complete publication can be generated.
1.2 Customer Data Integration
Purpose
With SAP NetWeaver, organizations can consolidate and manage customer data from all available sources. Customer data integration ensures that all relevant
departments in the company have constant access to the most up-to-date and complete view of available customer data. This contributes substantially to
streamlining cross-sell and up-sell activities, and facilitates customer processes across business units and locations while enabling consolidated analyses for
strategic business decisions.
Process Flow
From a process perspective, this business scenario operates on the basis of the master-data harmonization scenario.
In the context of customer data integration, special attention is paid to the cleansing and enriching capabilities provided by the MDM Enrichment Architecture.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 5