mdm 3.00 - master guide

8/3/2019 MDM 3.00 - Master Guide

http://slidepdf.com/reader/full/mdm-300-master-guide 1/32

Master GuideMaster GuideMaster GuideMaster Guide

SAPSAPSAPSAP®®®® Master DataMaster DataMaster DataMaster Data

Management 3.00Management 3.00Management 3.00Management 3.00

Document Version 1.03 - August 25, 2004

Material Number 50069271



© Copyright 2003 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.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and

SQL Server ® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®,

MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,

Netfinity®, Tivoli®, Informix and Informix® Dynamic Server TM

are

trademarks of IBM Corp. in USA 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.

LINUX is a registered trademark of Linus Torvalds and others.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®,

WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

J2EE™ 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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP

AG and Commerce One.

MaxDB™ is a trademark of MySQL AB, Sweden

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP

Business Suite, 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.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:service.sap.com/instguidesservice.sap.com/instguidesservice.sap.com/instguidesservice.sap.com/instguides

SAP AGSAP AGSAP AGSAP AGNeurottstraße 1669190 Walldorf GermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.comwww.sap.comwww.sap.comwww.sap.com



Typographic Conventions

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to other

documentationExample text Emphasized words or phrases

in body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,

SELECT and INCLUDE.Example text Screen output. This includes

file and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in the

documentation. <Exampletext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such

as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



1 Getting Started

1.1 Related Information

August 2004 5

1 Getting StartedThis Master Guide was developed to provide a central starting point for the technicalimplementation of SAP Master Data Management (SAP MDM). It contains an overview of allactivities for the installation of SAP Master Data Management.

SAP MDM consists of the following business scenarios:

Content Consolidation

Master Data Harmonization

Central Master Data Management

The Master Guide provides the information about which components and which guides arerequired during the technical implementation process.

• In the Getting Started [page 5] section, you get valuable information about using thisdocument and related information (documentation and SAP Notes) crucial to the

installation.• In the SAP Master Data Management Technical implementation [page 9] section, you will

find:

− An overview of each business scenario including its technical components(mandatory and optional components).

− Examples of how the different components interact, and what protocols andinterfaces are used (technical infrastructure examples). Depending on the actualbusiness processes that have to be implemented and other aspects (such as securityor performance), the real infrastructure might be different.

− Information about the component's software releases.

− Information about the overall installation sequence and subsequent steps.− References to related installation and configuration guides.

− Information about mutual dependencies that affect two or more components withinthe business scenario.

• In the Software Components Overview [page 25] section, you get a short description of every software component that is part of Master Data Management.

• Depending on the specific business scenario and the number of processes to beimplemented, many different installation and configuration guides are required during thebusiness scenario implementation process. In the References [page 31] section, you canfind an overview of all required documentation referenced in this Master Guide.

For the most current information about the technical implementation of SAPMDM and the latest installation and configuration guides, see the SAPService Marketplace under the Internet addressservice.sap.com/instguides.

We strongly recommend that you use the documents that are available onthese pages. These guides are updated on a regular basis.



1 Getting Started

1.1 Related Information

6 August 2004

1.1 Related InformationThe following list contains links to important information for planning the technicalimplementation of SAP MDM.

List of Related Information

Content Location in SAP Service Marketplace

Installation and Upgrade Documentation service.sap.com\instguides

Configuration Documentation service.sap.com\instguides

Information on released platforms service.sap.com\platforms

Information on planning the systeminfrastructure and network security

• service.sap.com\ti for technical

infrastructure information and SAPNetwork Integration Guide

• service.sap.com\securityguide for SAP Security Guide

Information on hardware sizing, calculation of hardware requirements and the quick sizer tool

service.sap.com\sizing

Information and documentation on highavailability issues for a multitude of areas, for example, SAP systems, databases, tools andnetwork.

service.sap.com\ha



1 Getting Started

1.2 Important SAP Notes

August 2004 7

1.2 Important SAP Notes

Read the installation SAP Notes before beginning the installation. Thesecontain the most recent information regarding the installation, as well ascorrections to the installation documentation.Make sure that you have the most recent version of each SAP Note. They arelocated on the SAP Service Marketplace under the Internet address

service.sap.com/notesor in SAPNet - R/3 Frontend.

List of Related SAP Notes

SAP NoteNumber

Title Description

758758 MDM 3.00: Additions to the Master Guide Latest information on SAP MDM3.00.

748777 Master Data Management 3.00 Add-On Information on installing SAP Master Data Management 3.00 Add-Onusing transaction SAINT



2 SAP Master Data Management Technical implementation

2.1 Business Scenario Overview

August 2004 9

2 SAP Master Data ManagementTechnical implementation


SAP MDM supports an incremental approach to cohesive master data management in adistributed and diversified environment. Being a key technology within SAP NetWeaver, SAPMDM is aimed at consolidating and harmonizing master data in heterogeneous systemlandscapes. Generally, it is designed for:

• Achieving high master data consistency beyond system boundaries through:

o Detection of duplicate data (within one system)

o Detection of identical master data (cross-system)• Gaining overall master data knowledge for global reporting by

o Providing the knowledge of master data dependencies (ID mappinginformation of identical records) within the IT landscape

• Improving overall master data quality through

o Rule-based merge of master data attributes of identical records

o Distribution of consolidated data to Master Data Clients (MDCs)

This consolidation and quality improvement (harmonization) of master data is achievedthrough a smooth, incremental scenario approach, which embarks Content Consolidation,Master Data Harmonization, and finally Central Master Data Management :

2.1.1 SAP MDM Content ConsolidationAny master data management solution requires the consolidation of master data objects fromdifferent systems. This entails capabilities to:

• Search for master data objects across linked systems

• Identify identical or similar objects

• Cleanse objects as needed

After consolidation, information from different systems should be transferred to a business

information warehouse where it can be accessed for unified, company-wide analytics andreporting.

To minimize disruptions, an MDM solution should enable the consolidation of master datawithout adjusting originating systems. This can be achieved through the use of object typeattributes, valid company-wide, that map identical and similar master data objects throughoutthe entire system landscape. This enables different data formats and structures to beretained in various systems throughout the extend enterprise. Moreover, the assignmentbetween identical data objects should also be updated each time a change is made, obviatingthe need to harmonize different identifiers for the same master data objects over the longterm.

This kind of flexible, non-intrusive approach to master data consolidation lays the foundationfor increasingly useful business analytics that leverage the accuracy of enterprise-wide data.





10 August 2004

Content Consolidation

Cleanse, normalize data

Aggregate, search, and cross

reference data from connectedsystems

Determine identical and

duplicate data

Examples:

Business-wide analyses

(e.g. global spend analysis),

Creation of central catalogs

(e.g. of supplier products)

MDMMDMClient

SAP

Client

non SAP

Clientnon SAP

ClientSAP

Clientnon SAP

MDMMDMClient

SAP

Client

non SAP

Clientnon SAP

ClientSAP

Clientnon SAP

While original master data records remain in the local Master Data Clients (MDCs), SAPMDM uploads identifying master data attributes from the MDCs to:

• Determine identical (duplicate) master data records

• Provide central key mapping information for cross-group reporting (such as GlobalSpend Analysis)

• Build consolidated Master Data Server (MDS) objects

Example use case:Consolidation of supplier records, where name and address data as well as externalidentifiers (Dun & Bradstreet numbers) are used for identification of duplicate and identicalmaster data records. The resulting key mapping information (supplier x in client a is

equivalent to supplier y in client b) can be used for advanced reporting such as global spendanalysis (“How much money do I spend with a supplier all across my organization?”)

2.1.2 SAP MDM Master Data HarmonizationWhile the consolidation of objects is necessary for quality master data management, it is notin itself sufficient for the needs of enterprises operating large distributed IT landscapes on aglobal scale. Consistent maintenance and distribution—which leads to the permanentharmonization of master data—is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systemsreceive the same master data during distribution. Thereafter, these distributed objects can be

enriched with additional attribute values in the Master Data Clients (for example, pricing datawhich is only relevant in the local procurement system).





August 2004 11

MDMMDMClient

SAP

Client

non SAP

Client

SAP

Client

non SAP

MDMMDMClient

SAP

Client

non SAP

Client

SAP

Client

non SAP

Master Data Harmonization

All of Content Consolidation PLUS

Central management and

distribution of global attributes

Post-editing in client systems

Controlled distribution of

local changes

Examples:

Business Partner administration

Central provision of sales articles

Definition and administration of

non-variable parts

In addition to providing central key mapping information, and posting consolidated MDSobjects on the Master Data Server (MDS), the Master Data Harmonization includesdistribution of consolidated data back to the MDCs. Central MDS objects are created either by:

• Merging the attributes of identical master data records that have been determined bySAP MDM.

• Centrally posting unique (that is, non-identical) master data either by postinguploaded non-identical records, or by centrally creating new master data. Newmaster data information is distributed to the client systems for replication.

Master Data Harmonization is focused on globally relevant master data information and stillallows master data maintenance at the client site for locally relevant master data attributes.

2.1.3 SAP MDM Central Master DataManagementWhile maintaining object attribute subsets for local systems might be the smartest course of action for some business processes, companies will want the option of a more centralizedsolution for other business processes. For example, some companies prefer completinginformation in the local procurement system (procurement key, pricing schema), other companies want to maintain all necessary attributes for executing a procurement processcentrally without any further addition of information in their local system. That’s why an MDMsolution should also support the maintenance of a complete object definition—including

object dependencies—in a centralized server for master data. Under such an arrangement,the maintenance of local systems happens rarely if ever. Instead, active status managementprocedures are used to update each of the individual distribution steps so that distribution canbe executed in a controlled, transparent and traceable manner.

The central maintenance of master data has numerous advantages for global companiesseeking ways to enforce, among other things, brand identity and consistent productspecifications. For example, a centralized data pool could supply globally dispersed upper management with consistent control over information relating to important global accounts. Asimilarly centralized data pool could supply up-to-date product data to multiple locations(including branch offices around the world) for the smooth management of production,assembly, sales and distribution.





12 August 2004

Central Master Data

Management

All of Content Consolidation PLUS

All of Master Data

Harmonization PLUS

All master data information

resides centrally

One-stop data maintenance

Examples:

Definition of synergy parts

Central product data pool supplying

product data to multiple locations

for production, assembly, sales and

distribution

MDMMDMClient

SAP

Client

non-SAP

Client

SAP

In contrast to the Master Data Harmonization scenario, Central Master Data Management isaimed at controlling all master data attributes centrally, thus eliminating the need of localmaintenance on master data.

For more information, see the Business Scenario Descriptions available onthe SAP Service Marketplace at the following Internet address:

service.sap.com/ibc.




2.2 Software Component Matrix

August 2004 13

2.2 Software Component MatrixThis section provides an overview of all available business scenarios and correspondingcomponents and their minimum releases and minimum Support Package (SP) levels.

SAP MDM 3.00 is based on SAP NetWeaver ´04 Support Package Stack 04, which containsthe following Support Package levels:

• Newest kernel patch

• SAP_BASIS 6.40 SP 04

• SAP_ABA 6.40 SP 04

• SAP_BW 3.5 SP 04

• WAS Java J2EE 6.60 SP 07

• EP 6.0 SP 06

• CM 6.0 SP06

• TREX 6.1.4

CC = Content Consolidation

MDH = Master Data Harmonization

CMDM = Central Master Data Management

SAP MDM BusinessScenarios

(X = mandatory / (X) =optional)

Software Component Minimum Release /Minimum SupportPackage (SP) Level

CC MDH CMDM

1: SAP Enterprise Portal

LDAP Server (Portal LDAP, CorporateLDAP)

For information onthe supporteddirectory servers,see the PlatformAvailability Matrix onthe SAP ServiceMarketplace at theInternet address

service.sap.com/pam60

(X) (X) (X)

SAP Enterprise Portal Platform

on

SAP Web AS Java

6.0, SP 06 Patch 02

6.40, SP 07

X X X

Business Package for SAP MDM 3.00 60.1 X X X

SAP Enterprise Portal KnowledgeManagement Platform

•

Content Management (CM)

• Retrieval and Classification (TREX)

6.0, SP 06

6.10.4

X

X

X

X

X

X





14 August 2004

2: Master Data Server

SAP Master Data Management Add-On

(including ABAP-part of SAP ContentIntegrator 3.0)

3.0 (MDM 300),

SP 00

X X X

SAP Web AS ABAP (Unicode system)

Use the latest Kernel Patch when youinstall SAP BW.

If you want to use Load Balancingbetween several application servers,make sure that you have installed theSAP Web Dispatcher.

SAP_BW 3.5 SP 04,SAP_ABA SP 04,SAP_BASIS SP 04

X X X

Basis Plug-In 2004.1, SP 04(PI_BASIS2004_1_640)

X X X

Integrated Product and ProcessEngineering

3.0, SP 00(EA-IPPE 300)Do not use a higher version than EA-IPPE 300.

X X X

SAP Content Integrator (SAP CI)

on

SAP Web AS Java

3.0, SP 00

6.40, SP 07

X X X

Workflow Modeler

on

SAP Web AS Java

4.0

6.40, SP 07

(X) (X) (X)

3: SAP Exchange Infrastructure

XI 3.0 Server, Netweaver 04Support PackageStack 04

X X X

XI Content MDM 3.002)

Netweaver 04Support PackageStack 04

X X X

XI Adapter Engine / JPR Netweaver 04Support PackageStack 04

X X X

XI Plain J2SE Adapter Engine Netweaver 04Support PackageStack 04

X X X





August 2004 15

4: SAP Solution Manager

SAP Solution Manager on SAP CRM

server

Use the latest Support Patches

3.1, SP 07 (ST 310)

including:

ST-ICO 130

(X)3)

(X)3)

(X)3)

SAP Internet Transaction Server

Use the latest Support Patches

6.20, SP 10 X X X

Enterprise Portal Plug-In 6.0, SP00(WP-PI 600_620)

X X X

5: Analytics

SAP Business Information Warehouse(SAP BW)

3.1 ContentSP 15

X (X) (X)

BI Content4)

BI_CONT 3.30SP 12

X (X) (X)

1)= Workflow Modeler 3.1 on J2EE 6.20 can also be used. For further details see SAP Note

626694.

2)= For details about the XI Content, see section 2.5.1 SAP MDM Installation.

3)= Highly recommended to support Customizing ID Mapping and Customizing distribution.

The SAP Solution Manager is not part of the SAP MDM 3.0 shipment. To order theSolution Manager, see SAP Note 628901.

4) = SAP BW 3.1 Content and the BI Content 3.30 add-ons are not part of the SAP MDM 3.0shipment. You can also use use SAP Business Warehouse 3.50 SP Stack 04 (SAP_BWSP 05) with BI Content 3.52 SP 04 or higher.





16 August 2004

Master Data Clients (MDC)

The SAP systems that you want to connect with SAP MDM must fulfill the softwarerequirements listed below.

The fulfillment of the software requirements is a technical prerequisite for connecting thedescribed client systems. It does not imply that the full functional scope regarding theattributes of the individual master data objects is covered.

SAP System Support PackageLevel

Add-Ons Remarks

SAP R/3

SAP R/3 4.6C --- R/3 Plug-InPI 2004_1_46C, SP 02

SAP R/3Releases 4.0B –4.6B can beintegrated on a

project basis

SAP R/3Enterprise 4.70

SAP_ABA 6.20,SP 38

SAP_APPL 4.70,SP 12

Basis Plug-In PI_Basis2004_1_ 620, SP 05

SAP R/3 Plug-In PI2004_1_470, SP 01

SAP XI Add-On 2.0, SP 04(APPINT200_620)

SAP ECC 5.0 SAP_ABA 6.40,SP 04

1)


SAP R/3 Plug-In PI

2004_1_500, SP 02

SAP Customer Relationship Managment

SAP CRM 3.1 BBPCRM SP 05 or higher

For distribution of Business Partner master data:

SAP_ABA 620, SP23

For distribution of BusinessPartner master data:


Basis Plug-In PI_Basis

2004_1_ 620, SP 03

SAP CRM 4.0 BBPCRM SP 07 or higher

For distribution of Business Partner andProduct master data:

SAP_ABA 620, SP36

For distribution of BusinessPartner and Product master data:



1) Additional notes are required for Master Data Clients on Web Application Server 6.40. For further information, see note 751207.





August 2004 17

Non-SAP systems

You can integrate non-SAP systems on a project basis.

Front End Requirements

Supported Front Ends for Portal Clients that are used for MDM 3.00

Operating System Internet Browser

• Windows 2000 • Internet Explorer 5.5 Service Pack 2

• Internet Explorer 6.0.x Service Pack 1

PortalAdministrator

• Windows XP • Internet Explorer 6.0.x Service Pack 1

• Windows 2000

•

Windows XP

• Internet Explorer 5.5 Service Pack 2Portal User

• Windows 2000

• Windows XP


For the Workflow Modeler, the following versions are supported:

• Internet Explorer 5.5 Service Pack 2


It is generally recommended to have the latest Service Pack installed on your operatingsystem.

SAP MDM 3.00 does not support Netscape®

browsers.

To use some applications that are included in the worksets for the Master Data Administrator or Master Data Manager roles, you must install the SAP GUI for Windows 6.20 (including BW

plug-in). This applies to the following applications:

• Workflow Builder

• Process chain

• Up- and download of business partner data

Java Runtime Environment

For details on the Java Runtime Environment required for SAP Netweaver Java Servers (e.g.used for SAP XI the Workflow Modeler), see SAP Note 716604.




2.3 Related Software CDs / Download Locations

18 August 2004

2.3 Related Software CDs / DownloadLocationsThe following table provides an overview of which CDs are required to install specificsoftware components. In some cases you must download the software or Support Packages /patches from SAP Service Marketplace.

Note that the CD MDM 3.0 Installation includes the following Support Packages:

• SAP_BASIS 6.40 SP 04

• SAP_ABA 6.40 SP 04

• SAP_BW 3.5.0 SP 04

• PI_BASIS 2004_1_640 SP 04

• EA-IPPE 3.00 SP 00

If some components require a higher Support Package level, download the addtional SupportPackages from the SAP Service Marketplace.

Software Component Required Software CDs

LDAP Server CD Novell eDirectory or www.novell.com/edirectory/sap

SAP Enterprise Portal CD Portal/CM , CD RDBMS , CD SAP J2EE Engine Single Node

SAP Service Marketplace: service.sap.com/swdc →

Download → Support Packages and Patches → Entry by

Application Group → SAP NetWeaver → SAP NetWeaver 04 → Enterprise Portal

Content Management CD Portal/CM

SAP Service Marketplace: service.sap.com/swdc → Download → Support Packages and Patches → Entry by

Application Group → SAP NetWeaver → SAP NetWeaver

components (< SAP NW 04 ) → SAP MDM

TREX CD TREX



Application Group → SAP NetWeaver → SAP NetWeaver 04 → TREX

Business Packages www.sdn.sap.com/sdn/contentportfolio.sdn

Web AS 6.40ABAP + Java

SAP Service Marketplace: service.sap.com/swdc → Download → Support Packages and Patches → Entry by


components (< SAP NW 04) → SAP Web AS

SAP Master DataManagement Add-On

CD MDM 3.0 Installation

Basis Plug-In SAP Service Marketplace:service.sap.com/installations

→ SAP R/3 Plug-In → PI_Basis

SAP Service Marketplace: service.sap.com/swdc

→ Plug-Ins → SAP Plug-In → PI_Basis

Integrated Product andProcess Engineering

CD MDM 3.0 Installation





2.3 Related Software CDs / Download Locations

August 2004 19




SAP Content Integrator CD MDM Content Integrator 3.0

SAP Service Marketplace: service.sap.com/patches

→ Download → Support Packages and Patches → Entry by



SAP ExchangeInfrastructure

CD Exchange Infrastructure



Application Group → SAP NetWeaver → SAP NetWeaver 04 → XI

Process IntegrationContent CD MDM 3.0 Installation SAP Service Marketplace service.sap.com/swdc →




SAP XI Add-On(for Masta Data Clients)

CD Exchange Infrastructure 2.0 SP 04



Application Group → SAP NetWeaver → SAP NetWeaver →

SAP NetWeaver 04 → XI

SAP Solution Manager CD SAP R/3 Add-On SAP Solution Manager

Enterprise Portal Plug-In

SAP Service Marketplace:service.sap.com/installations

→ Enterprise Portal Plug-In → WP-PI

service.sap.com/swdc


Application Group → SAP NetWeaver → SAP NetWeaver 04 → Enterprise Portal

SAP InternetTransaction Server

Server Components CD 1

SAP BusinessInformation Warehouse

Kernel CD, Export CD, Presentation CDs, RDBMS CDs

(Language CD)

SAP Service Marketplace: service.sap.com/swdc


Application Group →SAP NetWeaver → SAP NetWeaver → SAP

NetWeaver 04 → BW




2.4 Technical System Landscape

20 August 2004

2.4 Technical System LandscapeThe following graphic shows the systems involved in SAP Master Data Management:

Solution Manager

Master Data Server

SAP Enterprise Portal

SAP Exchange Infrastructure

Master Data Clients

J2EE Engine 6.40

EP 6.0

BusinessPackages

Exchange

Infrastructure

MDM

RDBMS

RDBMSRDBMS

EBP

R/3

CRM

Analytics

(optional)

BW

RDBMS

J2EE Engine 6.40

ABAP

CI

MDM

EA-IPPE

SAP BW 3.5

RDBMS

Content

SAP Netweaver´04

SAP Web AS

ITS

SolutionManager

For the sake of simplicity and clearness the graphic contains icons for whole SAP systems,not for single hosts. Remember that every SAP system may consist of several hosts withdifferent tasks.

To provide high availability and load balancing to the Master Data Manager, follow thedocumentation High Availability for mySAP.com Solutions. This documentation is available

on the the SAP Service Marketplace under the Internet address service.sap.com/ha .

Redundant network infrastructure should be used to ensure availability of the service. Thisincludes all active and passive network devices. Some load balancing mechanisms, such asWindows Load Balancing Server (WLBS), have no single point of failure (SPOF) by design.Other mechanisms avoid SPOF by redundancy.




2.4 Technical System Landscape

August 2004 21

The next graphic shows an exemplary technical infrastructure of SAP MDM. It depicts howyou can distribute the SAP MDM components on different hosts. For performance reasonsyou should implement SAP MDM on at least three hosts.

To improve performance in your production landscape, you must install SAPMDM and SAP CI on one host (add-in installation). By this, you minimize thenumber of remote calls.

Keep in mind that there may be dependencies for the different SAP MDMcomponents regarding databases and operating systems. Therefore, plancarefully on which platforms you are going to install the components. For detailed information on platform dependencies, see on SAP Service

Marketplace under the Internet address service.sap.com/platforms.

Master Data Clients

EBP

R/3

CRM


J2EE Engine 6.40

EP 6.0

BusinessPackages

MDM

RDBMS


Exchange

Infrastructure

RDBMS

Analytics

(optional)

BW

RDBMS

Content

Solution Manager

Master Data Server

RDBMS

J2EE Engine 6.40

ABAP

CI

MDM

EA-IPPE

SAP BW 3.5

RDBMS

SAP Netweaver´04

SAP Web AS

ITS

SolutionManager




2.5 SAP MDM Technical implementation Sequence

22 August 2004

2.5 SAP MDM Technical implementationSequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenarios of SAP MDM.

2.5.1 SAP MDM Installation

Do not install the Master Data Server on an already existing SAP BW system.

If the following components already exist in your system landscape you canuse them for SAP Data Management provided they fulfill the softwarerequirements:

• SAP Solution Manager

• SAP Exchange Infrastructure

You can install the below mentioned systems in parallel. However, within the systems youmust follow the given installation sequence.

For information about the required minimum component releases and Support Packagelevels, see the Software Component Matrix [on page 13].

For information on the required documentation, see section Documentation [on page 31].

No Action

[Corresponding Documentation]

Remarks andSubsequent Steps

[CorrespondingDocumentation]

Master Data Server

1 Install a Netweaver´04 Unicode system ABAP Server and JavaServer (Add-In) and apply the required Support Packages.

SAP Service Marketplace: service.sap.com/nw04doc

Installation

Use the latest KernelPatch when you installSAP Web AS.

2 Install the required support packs for the components:

o SAP_BASIS

o SAP_ABA

o SAP_BW

Upgrade the Basis plug-in to at least PI_BASIS 2004_1_640 SP04.

3 Install the following components on SAP Web AS ABAP 6.40and apply the required Support Packages:

• Integrated Process and Product Engineering (see SAP Note700780)

4 Install the SAP MDM 3.00 Add-On

Guide: SAP Note 748777 See also SAP Note 758758.





August 2004 23


5 Install the SAP Exchange Infrastructure including the IntegrationServices.

Guide: Master Guide – SAP Exchange Infrastructure 3.0

For details see theNetweaver 04 SupportPack Stack 04 Guide

6 Copy the process integration content (XI Content) from CD tothe file system of the Integration Repository host and import itinto the Integration Repository. You must import the content for the following components:

• MDM 3.00

• Application Basis 640 (SAP_ABA 6.40)

• PI_BASIS 2004_1_640

You must also import the necessary XI content for your Master Data Clients. The different MDCs require XI Content for thefollowing software components:

• SAP R/3 4.6C:

• SAP_APPL 4.6C

• PI 2004_1_46C

• SAP R/3 Enterprise 4.70:

• SAP_APPL 4.70

• PI 2004_1_470

• PI_Basis 2004_1_ 620

• SAP ECC 5.0

• SAP_APPL 5.0

• PI 2004_1_500

• PI_Basis 2004_1_ 640

• SAP CRM 4.0:

• SAP_BBPCRM 4.0

• SAP_ABA 6.20

• PI_BASIS 2004_1_ 620

• SAP CRM 3.1:

• SAP_ABA 6.20

• PI_BASIS 2004_1_ 620

The Support Package level of the Master Data Client XI contentmust be the same as the Support Package level of the Master Data Client itself.

Guide:

Online documentation in SAP XI or in SAP Help Portal at the

Internet address help.sap.com.

7 Download and install the most current SLD Content from theService Marketplace

http://service.sap.com/swdc: Download -> Support

Packages and Patches -> Entry by Application Group ->Additional Components -> SAP MASTER DATA FOR SLD





24 August 2004

See SAP Note 669669 for details on how to get the latest SLDContent.

SAP Solution Manager

8 Install the SAP Solution Manager.

Guide: Installation Guide – SAP Solution Manager 3.1

Install the Enterprise PortalPlug-In (see SAP Note655941).

9 Optional: Install the SAP Internet Transaction Server on the SAPSolution Manager

Guide: SAP@Web Installation Guide


10 Install the SAP Enterprise Portal on SAP Web AS Java, LDAPcorporate server(s) (optional), Content Management and TREX

Guide:

SAP Service Marketplace: service.sap.com/nw04doc Installation

11 Import the required Business Packages:

Business Package for SAP MDM 3.01)

Guide:

How to use a Business Package

Download the BusinessPackages fromwww.sdn.sap.com/sdn/

contentportfolio.sdn

SAP Content Integrator

12 Install SAP Content Integrator 3.0 to the Netweaver 04 Java-Server (Add-In Installation)

Guide: Installation Guide - SAP Content Integrator 3.0 .1)

For information about the installation of Business Package for SAP MDM 3.0, see in theConfiguration Guide.

2.5.2 SAP MDM UpgradeFor information about the upgrading of SAP MDM 2.00 to SAP MDM 3.00, see thecorresponding Upgrade Master Guide.

2.5.3 SAP MDM ConfigurationFor information about the configuration of SAP MDM, see the corresponding configurationguides:

• Configuration Guide – SAP MDM Content Consolidation (SAP MDM 3.00)

• Configuration Guide – SAP MDM Master Data Harmonization and Central Master DataManagement (SAP MDM 3.00)



3 Software Components

3.1 Software Components Overview

August 2004 25

3 Software ComponentsThis section provides additional information about the most important MDM softwarecomponents.


SAP Web Application Server

Use

SAP Web Application Server (SAP Web AS) is the application platform of SAP NetWeaver and with this of the mySAP Business Suite. It provides the technological foundation for all

other SAP components.

For SAP Web AS, different basic system variants exist. It can be installed as ABAP+Javasystem, as Java system or as ABAP system. The difference between these system variantsis that you can either operate both the ABAP Engine and the J2EE Engine, only the J2EEEngine or only the ABAP Engine in your SAP Web AS.

Until SAP R/3 4.6D, SAP Web Application Server was named SAP Basis.

Since SAP Web AS contains the ABAP Engine, the Java Engine or both, it provides aruntime for ABAP and/or Java applications.

SAP Web AS includes a platform for quickly developing and deploying dynamic andcollaborative Web applications or other thin-client applications (WAP, PDA, and so on) andincludes all proven SAP programming models and technologies. With SAP Web AS, SAP

natively supports open Internet standards, including such protocols as HTTP, HTTPS, andSMTP, as well as Internet document standards like HTML and XML.

Open integration capabilities provide access to existing SAP and non-SAP applications. Allintegration facilities supported by SAP are available with SAP Web AS. The Java Connector or the .NET Connector give ABAP applications access to Java or .NET components and viceversa. In addition, the Internet Communication Framework (ICF) of SAP Web AS enablesABAP-written programs to process and distribute HTTP requests directly. As a consequence,SAP Web AS can serve both as an HTTP server and client. It serves as an HTTP server for bringing applications to the user through a Web browser either directly or using a standardWeb server. It serves as an HTTP client to access other Web applications for collectinginformation and data. To complete Web connectivity, SAP Web AS provides full support for sending and receiving e-mails using SMTP.

Building Blocks

SAP Web AS 6.40 consists of the following main building blocks:

Central instance

Central service instance

The central services instance forms the basis of communication and synchronization for the Java cluster.





26 August 2004

Database instance

SAP Web AS Java has a separate database schema. As a result, a database instance isalso a mandatory installation component for the installation of an SAP Web AS Javasystem.

For the installation of an SAP Web AS ABAP+Java system, both the ABAP and the Javaschema get installed in the same database.

Exception:If your SAP system is running on Informix, a separate MaxDB or IBM DB2UDB for UNIX and Windows is required for the Java database schema.

Dialog instances, if required

Dialog instances are SAP instances that include only:

• Dispatcher, IGS, and CCMS agents

• SAP Web AS ABAP+Java system and SAP Web AS Java system: Java server processes

• SAP Web AS ABAP+Java system and SAP Web AS ABAP system: gateway andcertain ABAP work processes (dialog, batch, spool, or update)

Dialog instances are installed on application servers.

The dialog instances of SAP Web AS Java systems are called J2EE dialog instances.

SAP GUI

See separate component description above.


Based on a native Web infrastructure that leverages open standards, SAP ExchangeInfrastructure (SAP XI) makes it possible to manage the broad diversity of highlyheterogeneous components from a multitude of vendors and running in various technologyenvironments. The integration capabilities capture shared business semantics and act as amediator between the services and their technical realizations. It includes technical functions,such as queuing, mapping, and routing. It also establishes an infrastructure for businessprocess management and high-performance execution within and across organizationalboundaries.

Process integration based on SAP XI removes the problems of direct connections byextracting shared collaboration knowledge. These shared business semantics ease theintegration of both external and internal components. Instead of directly coding point-to-pointinterfaces for each new component, the exchange infrastructure allows instant plug-in of newcomponents once for each component. This provides the future flexibility needed in today’sfast-changing business world, and it reduces integration costs compared to the directconnection approach.


SAP Enterprise Portal provides a role-based, secure and web-based interface to any kind of information, application and services. To run the portal, you need a standard browser on the

desktop; no additional software components are required.





August 2004 27

As part of SAP Enterprise Portal, the Portal Infrastructure provides a secure access to anykind of structured data coming from any kind of business applications, such as SAP, non-SAP, data warehouses, or databases.

As a key technology of the Portal Infrastructure, iViews allow an access for reading purposes

or for carrying out an operation, such as submitting a form for supplies. A set of portalservices is provided to enable iViews to interact with each other such as portal navigation (for example, Dynamic Navigation or the patented Drag&Relate technology), portal eventing, or WorkProtect mode.

Portal roles structure and deliver targeted content to each end user. Thanks to the role-baseduser interface, a company can structure its business processes and deliver business contentaccording to the needs of certain user groups. Besides the role concept, Portal Infrastructureprovides additional personalization features such as iView, page or layout personalization.

To create and develop portal content, SAP provides a set of tools targeted to different user groups ranging from business experts to developers.

Before creating or developing iViews, customers should first check the SAP iViewStudio,

where thousands of iViews, bundled as business packages, are available for download.Business packages contain pre-assembled, role-based content for completing businesstasks.

Knowledge Management

The Knowledge Management platform provides access to an organization's unstructuredinformation (documents). The information may reside in various repositories that can beconnected to the portal by means of components called repository managers. Somerepository managers are delivered by SAP; other repository managers can be developedbased on open APIs. The functions of the KM platform can be exposed to the documents inall connected repositories, given that the respective repository manager allows it. The major

functional areas of KM are:

Content Management, which supports the entire lifecycle of documents, including theauthoring, storage, management, and display of documents. It also manages theconnection between document repositories and the portal and provides collaborativefunctions such as feedback, rating, subscription, etc.

Search and Classification (TREX), which processes search queries on free-text or attributes, and provides automatic classification in taxonomies and text mining. Searchand Classification (TREX) is also used in other building blocks of SAP NetWeaver suchas SAP Business Information Warehouse.

Search and Classification (TREX)The information retrieval system Search and Classification (TREX)provides various softwareapplications with a wide spectrum of intelligent search, retrieval, and classification functions.You can use Search and Classification (TREX) to search extensive electronic collections of text documents flexibly, and to structure document collections in a way that gives a clear overview of what is available. The Search and Classification (TREX) text-mining functionsallow interesting and relevant information to be extracted from text documents for the user.

In principle, Search and Classification (TREX) can process, search, and classify any fileformat that can be rendered as text.





28 August 2004

Business Packages

Business packages are predefined portal applications targeted to a set of related roles.Because business packages already include most of the content those roles need, they

greatly speed up the implementation process. Business packages consist of worksets thatform a unit from the content perspective. Customers can change and extend businesspackages by creating new iViews and worksets, changing SAP's iViews and worksets, addingaccess to additional reports or documents, and adding Drag&Relate relationships. They canalso modify the business packages by enhancing them with the building blocks offered aspart of SAP's content offering, including role templates or SAP BW Business Content.

SAP User Management Engine

The User Management Engine (UME) provides a centralized user management for all Javaapplications and can be configured to work with user management data from multiple data

sources. It is seamlessly integrated in the J2EE Engine of SAP Web AS Java as its defaultuser store and can be administrated using the administration tools of SAP Web AS Java.

UME adds business value by enabling you to leverage your existing system infrastructure byaccessing user-related data on an existing corporate directory, an SAP Web AS ABAPsystem, a database or any combination of these. In addition it reduces administrativeoverhead by allowing you to perform centralized user administration.

SAP Master Data Management Add-OnSAP Master Data Management Add-on is a central unit within SAP MDM to manage themaster data objects and required services, such as maintenance, authorization, statusmanagement, Workflow, and cross-object search. Additionally it incorporates central featuresfor controlled load and distribution of master data within a heterogeneous IT landscape.

SAP Content Integrator CI supports the following: matching, ID mapping, and recategorization of products. Matchingidentifies pairs of “equal” objects within a set of business objects. The term “equal” can meananything from identical objects in different systems to equivalent objects in the same system,such business partners with similar names. “Matching strategies”, can be used to tailor thedefinition of “equal”.

The matching results - pairs of “equal” business objects - are stored in the ID mappingservices for future use.

Therefore, CI provides an external API to query the ID mapping service. Furthermore, andindependent pf the matching, the ID mapping service can maintain all kinds of categoryhierarchies; for example, mapping from an R/3 material group to a standard categoryhierarchies such as UNSPSC.

CI provides you with the means to maintain this “vectored” ID mapping.

It can be used by CI to re-group products based on their category information, which allowsyou to classify products appropriately, for global spending analysis within BI, for example.





August 2004 29

SAP Solution Manager

The SAP Solution Manager is SAP's new service and support platform that helps you toimplement and operate your SAP solution efficiently. Together with the SAP Service

Marketplace, the SAP Solution Manager represents SAP's strategic service infrastructure thatguides our customers through all stages of their SAP solution life cycle.

Today, the SAP Solution Manager consists of:

• Central documentation of system landscapes and core business processes

• Implementation tools, key functional implementation aspects such as blueprinting,configuration and testing(formerly known as AcceleratedSAP or ValueSAP)Access to SAP Support services and Best Practices

• Periodic service level reporting and real-time monitoring of system components andbusiness processes

• Advanced message handling for fast problem analysis and resolution including the SAPNote Assistant and a direct connection to the SAP Support Back Office.

Within SAP Master Data Management, the SAP Solution Manager is used for Customizingsynchronization within a heterogeneous IT landscape.

SAP Business Information Warehouse

The reporting, analysis, and interpretation of business data is of central importance to acompany in guaranteeing its competitive edge, optimizing processes, and enabling it to reactquickly and in line with the market. As a core component of SAP NetWeaver, the SAPBusiness Information Warehouse (SAP BW) provides data warehousing functionality, abusiness intelligence platform, and a suite of business intelligence tools (BW Business

Explorer) that enable businesses to attain these goals. Relevant business information can beintegrated, transformed, and consolidated in SAP BW with the toolset provided. SAP BWfacilitates the reporting, analysis, and interpretation of this information, as well as itsdistribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis. With the comprehensive predefinedinformation models delivered for different roles in a business (BI Content), SAP BW increasesthe usability of analysis functions and facilitates a quick and cost-effective implementation.

Data warehousing in SAP BW represents the integration, transformation, consolidation,cleanup and storage of data. It also incorporates the extraction of data for analysis andinterpretation. The data warehousing process includes data modeling, data extraction, andadministration of the data warehouse management processes.

The business intelligence platform serves as the technological infrastructure to support

information access and comprehensive analytics. It provides various analytical technologiesand functions. These include the OLAP processor, Business Planning and Simulation, andspecial analysis processes such as Data Mining, and the Reporting Agent.

The SAP BW business intelligence suite, the Business Explorer, provides flexible reportingand analysis tools for strategic analyses, operational reporting, and decision-making supportwithin a business. These tools include query, reporting, and analysis functions. Users canevaluate old and current data in varying degrees of detail and from different perspectives –on the Web and also in Microsoft Excel. The Business Explorer allows a broad spectrum of users access to information in the SAP BW using SAP Enterprise Portal, the Intranet (Webapplication design) or mobile technologies (mobile telephones with WAP or I-modecapabilities, and personal digital assistants).




3.2 Non-SAP Components

30 August 2004

SAP Internet Transaction Server

The SAP Internet Transaction Server (SAP ITS) combines existing Internet technology withSAP technology and provides reliable access to SAP functions from the Internet or intranets.

SAP ITS is a SAP technology component. It is a gateway between one or more Web serversand one or more SAP application servers. Typically, the Web server is an HTTP server, butother protocols such as FTP or Gopher may also be supported.

SAP ITS mainly generates HTML pages and enables end users to interact with different SAPsystems using a Web browser. SAP ITS also acts as the server component for the SAP GUIfor HTML and various application scenarios, such as SAP Employee Self-Services or SAPCRM.

The following graphic shows how SAP ITS extends the three-tier client/server architecture of the SAP system for Internet use:

SAPSAP

applicationapplication

server server

SAPSAP

databasedatabase

server server SAP ITSSAP ITSWebWeb

server server WebWeb

browser browser

Request

Response

The SAP ITS manages all requests and responses between a Web browser client and anSAP system server.

3.1.1 Industry-specific ComponentsSAP MDM uses no industry-specific components.

3.2 Non-SAP ComponentsThe LDAP server is the only non SAP component used within SAP Master DataManagement.



4 References

4.1 SAP Notes

August 2004 31

4 References

4.1 SAP NotesThe following table lists all SAP Notes mentioned in this documentation.

SAP Note Number Title

758758 MDM 3.00: Additions to the Master Guide

748777 Master Data Management 3.00 Add-On

633762 Sporadic RFC crashes in a multithread application

544979 Importing Java Support Packages with SDM

700780 Installation of EA-IPPE 300

655941 WP-PI 6.00: SAP Enterprise Portal Plug-In

628901 You want to order the SAP Solution Manager 3.1

711769 Single sign on between SAP Java Software Products



4 References

4.2 Documentation

4.2 DocumentationList of technical implementation and configuration documentation for SAP MDM and itsbusiness scenarios.

For detailed SAP Netweaver 04 documentation, see the Service Marketplace,alias \nw04doc.

Title Where to find

SAP Enterprise Portal Installation Guide

(Documentation set that containsinstallation guides for Portal, Content

Management and TREX)

SAP Service Marketplace atservice.sap.com/nw04doc

Installation

Installation Guide – SAP User Management Engine 3.0

SAP Service Marketplace at the Internet addressservice.sap.com/instguides

SAP Components SAP MDM SAP MDM 3.00

How to use a Business Package SAP Service Marketplace at the Internet addressservice.sap.com/epinstall

How-To Guides Current How-To Guides

Component Installation Guide – SAP Business Information Warehouse 3.5.x

SAP Service Marketplace at the Internet addressservice.sap.com/nw04doc

Installation

SAP@Web Installation Guide Server Components CD

Installation Guide – SAP Content Integrator 3.0



Master Guide – SAP ExchangeInfrastructure 3.0

SAP Service Marketplace at the Internet addressservice.sap.com/nw04doc

Installation

Upgrade/Migration Guide – SAP Solution Manager 3.1

SAP Service Marketplace at the Internet addressservice.sap.com/solutionmanager

Installation Guides

Configuration Guide – SAP MDM Content Consolidation



Configuration Guide – SAP MDM Master Data Harmonization and Central Master Data Management



mdm 3.00 - master guide

Documents