SAP Business Information Warehouse and SAP Master Data Management acting together

SAP TechEd ‘03 Las Vegas
SAP Business Information
Warehouse and SAP
Master Data Management
acting together
Rainer Uhle
Product Manager Product Line BI,
SAP AG
Learning Objectives
As a result of this workshop, you will
be able to:
„ Understand how Master Data handling in SAP BW is
impacted by SAP MDM
„ Define several SAP MDM scenarios and their impact on SAP
BW Master Data load processes
„ Detail the value of SAP BW Consolidated Info Objects as
ideal integration points for SAP MDM.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 2
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
1
SAP TechEd ‘03 Las Vegas
Agenda
Introduction
„ Application optimization example: mySAP SRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 3
Agenda
Introduction
„ Application optimization example: mySAP SRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 4
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
2
SAP TechEd ‘03 Las Vegas
Global Spend Analysis in mySAP SRM
Purchase
Orders
Invoices
SAP XI
XML
XML
Copy
Purchaser
Suppliers
BI
Global Spend
Global Spend Analysis
mySAP SRM
reduces total spend for
continuous profitability
„ Visualize global spend across
organizational boundaries
„ Compare vendor prices
„ Improved sourcing strategy
„ Minimize contract leakage
„ Compressed cycle times
„ Consolidate suppliers
„ Reduced process costs
„ Lower unit prices
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 5
Today’s Option - Point-To-Point Connection
mySAP SRM 3.0:
One or multiple procurement systems, one SAP Business
Information Warehouse (SAP BW Content 3.2 or higher)
One Content Integrator*, that relies on a mySAP SRM server basis
Possible: Dun & Bradstreet Supplier Analytics for SAP BW
All transactional and all master data are uploaded into SAP BW
directly. Connection to SAP R/3 rel. 3.1I and higher, EBP 2.0 and
higher is pre-configured, other procurement systems may be
connected directly to SAP BW via Ascential’s Datastage
Key Mapping data are uploaded
D&B
D&B
from CI into SAP BW
Supplier data and product categories
are consolidated by the Content Integrator
CI
CI
BW
Supplier data may be enriched
with Dun & Bradstreet
EBP
EBP
R/3
R/3
Non
Non
R/3
R/3
EBP
EBP
SUS
SUS
R/3
R/3
* Requires SAP Content Integrator 2.0. Expected availability with mySAP SRM service pack 2
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 6
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
3
SAP TechEd ‘03 Las Vegas
Tomorrow’s Option - Hub-Based Scenario
Future (beyond mySAP SRM 3.0)
One or multiple procurement systems
One SAP Business Information Warehouse
One SAP XI
One SAP Master Data Management (with Content Integrator )
Possible: Dun & Bradstreet Supplier Analytics for SAP BW
Purchase Orders, PO Changes and Invoices (B2B messages) are
routed into SAP BW
CI
CI
Supplier data, product
and product categories are
consolidated by SAP MDM
D&B
D&B
MDM
MDM
Key Mapping data are uploaded from
SAP MDM/CI into SAP BW
Supplier
XI
Supplier data may be
enriched with Dun & Bradstreet
BW
EBP
EBP
R/3
R/3
EBP
EBP
R/3
R/3
Non
Non
R/3
R/3
Non
Non
R/3
R/3
XML
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 7
Agenda
Introduction
„ Application optimization example: mySAP SRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 8
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
4
SAP TechEd ‘03 Las Vegas
Overview – SAP BW/MDM Scenarios and Benefits
An SAP Customer with a productive SAP BW Environment wants to
implement SAP MDM.
¾ Scenario I
Minimal involvement of SAP MDM in SAP BW Master Data extraction
for operational reporting needs
¾ Scenario II
Global consolidation of SAP BW Master Data via SAP MDM for strategic
reporting needs in SAP BW
An SAP Customer without an SAP BW Environment wants to
implement SAP MDM and SAP BW
¾ Scenario III
Maximized and optimized embedding of SAP MDM in the SAP BW Master
Data extraction process
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 9
Scenario I
An SAP BW Customer has several SAP R/3 systems as the only source
for SAP BW.
The SAP R/3 system landscape grew steadily historically. A recent
acquisition caused a significant jump in growth.
Between the SAP R/3 systems (existing and acquired), Material
Management number ranges for the Entity “Material” (MATNR-Domain)
overlap. To accommodate this situation, the corresponding meta object
in SAP BW, the InfoObject 0MATERIAL has been modeled as a
concatenated key consisting of the two digit source system ID and the
local material number.
This technique guarantees a consistent view of the local data for
operational reporting needs.
In this scenario, SAP MDM complements SAP BW by assisting in the
consolidation of the master data of the various R/3 sources.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 10
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
5
SAP TechEd ‘03 Las Vegas
Scenario I: Productive SAP BW Environment on Rel.
3.1 Content
SAP
SAP BW
BW
0MATERIAL
IS: Material
Overlapping
OverlappingNumber
NumberRanges
Rangesfor
forEntity
EntityMaterial
Material
Material
MaterialNumber
Number4711
4711exists
existsin
inthree
three SAP
SAPR/3
R/3
Systems
Systems
Sources
Sources
R/3 Material
MATNR
R/3
R/3
R/3
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 11
Master Data Situation in the SAP R/3 Source Systems
Source
System
Material
Number
...
Short Text
R/3 S1
4711
…
Hammer (150 g)
R/3 S2
4711
…
Hammer G150
R/3 S3
4711
…
Screw Driver S 7a
R/3 S1
4712
…
Hammer 5.25 oz ( ca. 150gr)
R/3 S1
4713
…
Hammer G 450
R/3 S1
4714
…
Hammer G 650
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 12
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
6
SAP TechEd ‘03 Las Vegas
Scenario I: Concatenate Material and Source System
0MATERIAL Text
SAP
SAP BW
BW
0MATERIAL
IS: Material
Sources
Sources
S1
S1
R/3
R/3 Material
S2
S2
R/3
0MATERIAL
...
Hammer (150 g)
S1 4711
…
Hammer G150
S2 4711
…
Screwdriver S 7a
S3 4711
…
Hammer 5.25 oz
( ca. 150gr)
S1 4712
…
Hammer G 450
S1 4713
…
Hammer G 650
S1 4714
…
S3
S3
R/3
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 13
SAP MDM – An Incremental Approach
Content
Consolidation
1
2
Master Data
Harmonization
Content Consolidation
„ Cleanse, normalize data
„ Aggregate, search, and cross reference
data from connected systems
„ Duplicate finding
Examples:
„ Business-wide analyses
(e.g., global spend Analysis),
„ Creation of central catalogs
(e.g., of supplier products)
SAP MDM supports an
incremental approach to a
cohesive master data
management in a
distributed and heterogeneous environment
3
Central Master
Data Management
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 14
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
7
SAP TechEd ‘03 Las Vegas
Master Data Consolidation with SAP MDM 2.0 –
Scenario
1
Content Consolidation
Core Process Steps:
MDM
MDM
Client
SAP
1. Loading identifying attributes of
master data objects as they were
maintained in their local
applications (clients)
Client
non SAP
Load
Client
non SAP
?
2. Matching of uploaded master data
objects to identify duplicates
Matching
Client
SAP
=
3. Providing ID Mapping Information
based on matching results for
subsequent usage (I.e., in
Business Intelligence)
ID Mapping
Client
non SAP
Description of a master data object:
Æ Identifying Attributes
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 15 Æ Other application specific data
SAP MDM Implementation Step 1
CI
Group ID
BW
BW
0815
0MATERIAL Text
MATERIAL
System
Hammer (150 g)
4711
S1
0MATERIAL 0815
4711
S2
0816
4711
S3
IS: Material 0815
4712
S1
Screwdriver S 7a
Hammer 5.25 oz
( ca. 150gr)
Hammer G 450
0817
4713
S1
0818
4714
S1
Hammer G 650
Sources
Sources
CI Group ID Text
Hammer G150
Hammer G150
Screwdrivers
Hammer 450
Hammer 650
R/3 Material
Content
ContentIntegrator
Integrator
S1
S1
R/3
S2
S2
R/3
=
S3
S3
R/3
ID Mapping
?
Load
Description of a master data object:
Æ Identifying Attributes
Æ Other application specific data
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 16
© 2003 SAP Labs, LLC
Matching
MDM
MDM
XI
XI
BW 206, Rainer Uhle
8
SAP TechEd ‘03 Las Vegas
Available CI Extractors on the SAP MDM Server
The right DataSource
for our purpose:
Grouped Key Mapping
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 17
SAP MDM Extractor: Product Key Mapping
Information
Matching
Matching
Process
Process
System-ID
System-ID
S1-S3
S1-S3
Object
Object Type
Type
0MATERIAL
0MATERIAL
Material
Material Number
Number
47*...
47*...
Group-ID
Group-ID
????
????
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 18
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
9
SAP TechEd ‘03 Las Vegas
SAP BW Scenario I: SAP MDM Implementation Step 2
0Material
SAP
SAP BW
BW
0MATERIAL
IS: MDM Product
ATTR+TEXT
IS: Material
Sources
Sources
...
Group ID
S1 4711
0815
S2 4711
0815
S3 4711
0816
S1 4712
0815
SAP
SAP MDM
MDM
R/3 Material
=
ID Mapping
R/3
R/3
?
R/3
Load
Matching
Description of a master data object:
Æ Identifying Attributes
Æ Other application specific data
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 19
XI
XI
Result: Analytic Output (Consolidated View)
Tools
Article
Revenue
Hammer G150
150.000
Hammer (150 g)
30.000
Hammer G150
50.000
Hammer 5.25 oz
( ca. 150gr)
70.000
Hammer 450
100.000
Hammer 650
200.000
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 20
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
10
SAP TechEd ‘03 Las Vegas
SAP BW Scenario I: SAP MDM Implementation in SAP
BW
Implementation
Implementation steps
steps in
in SAP
SAP BW:
BW:
•Implement
•Implement SAP
SAP MDM
MDM as
as aa source
source system
system in
in SAP
SAP BW
BW
•Replicate
•Replicate the
the SAP
SAP MDM
MDM DataSources
DataSources into
into SAP
SAP BW
BW and
and create
create
InfoSources
InfoSources
•Enhance
•Enhance 0MATERIAL
0MATERIAL with
with an
an additional
additional attribute
attribute for
for Group
Group ID
ID
•Create
•Create an
an UpdateRule
UpdateRule for
for 0MATERIAL
0MATERIAL based
based on
on the
the particular
particular
SAP
SAP MDM
MDM InfoSource
InfoSource
•Load
•Load SAP
SAP MDM
MDM Content
Content Integrator
Integrator information
information into
into SAP
SAP BW
BW
master
data
table
for
0MATERIAL
master data table for 0MATERIAL
•Reactivate
•Reactivate Cubes
Cubes with
with transactional
transactional data
data containing
containing 0MATERIAL
0MATERIAL
•Additional
•Additional Aggregates
Aggregates for
for CI
CI Group
Group ID
ID might
might be
be useful
useful
•Existing
•Existing queries
queries provide
provide “local”
“local” views.
views.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 21
SAP BW Scenario I - Summary
•• Harmonization
Harmonization of
of values
values for
for aa single
single entity
entity (here
(here 0MATERIAL)
0MATERIAL)
with
with aa clear
clear defined
defined semantic.
semantic.
•• No
No additional
additional MetaData
MetaData necessary
necessary except
except the
the InfoObject
InfoObject for
for
Group-ID
(0GROUPID
available
with
SAP
BW
3.0B
Group-ID (0GROUPID available with SAP BW 3.0B BCT)
BCT)
•• No
No SAP
SAP MDM
MDM Business
Business Content,
Content, InfoSources
InfoSources and
and UpdateRules
UpdateRules
have
have to
to be
be implemented
implemented manually
manually
•• Transactional
Transactional Data
Data Management
Management is
is not
not affected
affected
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 22
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
11
SAP TechEd ‘03 Las Vegas
Agenda
Introduction
„ Application optimization example: mySAP SRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 23
Overview – SAP BW/MDM Scenarios and Benefits
An SAP Customer with a productive SAP BW Environment wants to
implement SAP MDM.
¾ Scenario I
Minimal involvement of SAP MDM in SAP BW Master Data extraction for
operational reporting needs
¾ Scenario II
Global consolidation of SAP BW Master Data via SAP MDM for
strategic reporting needs in SAP BW
An SAP Customer without an SAP BW Environment wants to
implement SAP MDM and SAP BW
¾ Scenario III
Maximized and optimized embedding of SAP MDM in the SAP BW Master
Data extraction process
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 24
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
12
SAP TechEd ‘03 Las Vegas
Scenario II
An SAP BW Customer has several productive mySAP Components.
The SAP R/3 system landscape grew steadily historically. A recent
acquisition caused a significant jump in growth.
Business Content in SAP BW was activated according to best practices for
each mySAP component. Because these were activated independently, no
globally consolidated view of master data is immediately available.
The project team has opted to use the Consolidated InfoObjects (also
called Cross Application Master Data) included in their upgrade to SAP BW
3.0B to accommodate new requirements for globally consolidated views of
master data from SAP R/3 and mySAP CRM components.
The benefit of this approach is two-fold:
• It guarantees a consistent view of the local data for operational
reporting needs
• It provides a global view for strategic reporting/analysis.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 25
Master Data Situation in the SAP MDM Clients
Source
System
Material
Number
...
Short Text
R/3 S1
4711
…
Hammer (150 g)
R/3 S2
4711
…
Hammer G150
R/3 S3
4711
…
Screw Driver S 7a
R/3 S1
4712
…
Hammer 5.25 oz ( ca. 150gr)
R/3 S1
4713
…
Hammer G 450
R/3 S1
4714
…
Hammer G 650
CRM C1
5711
…
Hammer Trini Lopez 150
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 26
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
13
SAP TechEd ‘03 Las Vegas
Scenario II: Productive SAP BW Environment on Rel.
3.1 Content
SAP
SAP BW
BW
Business
BusinessContent
Contentfor
forvarious
variousbusiness
businessareas
areas
0MATERIAL
0_ORA
0BBP_PROD
0CRM_PROD
IS: Material
IS: ORA
IS: BBP Prod
IS: CRM Prod
R/3 Material
ORA Service
EBP Product
CRM Product
R/3
R/3
R/3
Oracle
R/3
R/3
EBP
R/3
R/3
CRM
R/3
R/3
Sources
Sources
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 27
Cross-Application Reporting: Product Data Flow
Global and
consolidated views
on products
0PRODUCT
Independent on
source system
0MATERIAL
0SERVICE
0BBP_PROD
0CRM_PROD
IS: Material
IS: Service
IS: BBP Prod
IS: CRM Prod
R/3 Material
R/3 Service
EBP Product
CRM Product
R/3
R/3
R/3
R/3
R/3
R/3
EBP
R/3
R/3
CRM
R/3
R/3
Analytics
restricted to the
view of one local
application
system
Local Application
Systems with
individual data
models
DataSources
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 28
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
14
SAP TechEd ‘03 Las Vegas
Consolidated InfoObjects: Status from SAP BW 3.0A
Heterogeneous Master Data in SAP BW for:
„
„
„
„
Products
Product Categories
Business Partner (Vendor / Customer)
...
... from different software components:
„
„
„
„
„
SAP R/3
mySAP SRM (EBP, SUS)
mySAP CRM
mySAP SCM
Non-SAP
... represented in BW with separate InfoObjects:
e.g.: 0MATERIAL
0BBP_PROD
0ORA_PROD
R/3 Material
EBP Product
Oracle Product
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 29
Product: Data Model in SAP BW - Composite Key (I)
The key of all consolidated InfoObjects is composed of:
ÎSource System Information
Represented by Infoobject 0SOURSYSTEM (Char 2)
ÎObject Type
Defined in BW Customizing (Char 4).
Predefined values will be delivered along with Business Content
e.g., 1MAT – Material, 1SER – Service
ÎKey of Local View
Original local key from object in source system
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 30
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
15
SAP TechEd ‘03 Las Vegas
0Product : Consolidated Data Model in SAP BW
The Problem
The Goal
One Instance
For
Global Attributes
And
Key Mapping
Information
System
Obj.Type
Loc. Key Description
Group ID
CRM C1
1MAT
5711
Trini Lopez 150
0815
R/3 S1
1MAT
4711
Hammer (150 g)
0815
R/3 S2
1MAT
4711
Hammer G150
0815
R/3 S1
1MAT
4712
Hammer 5.25 oz
0815
The Solution Model
0PRODUCT Key
Source
System
0MATERIAL Key
in R/3 System
0CRM_PROD Key
in CRM system
Group ID
-
5711
0815
R/3 S1
4711
-
0815
1MAT 4711
R/3 S2
4711
-
0815
1MAT 4712
R/3 S1
4712
-
0815
CRM C1 1MAT 5711
CRM C1
R/3 S1
1MAT 4711
R/3 S2
R/3 S1
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 31
SAP MDM – an incremental approach
Master data harmonization
1
„ All of
Content Consolidation PLUS
Content
Consolidation
„ Central management and
distribution of global attributes
„ Post editing in client systems
„ Controlled distribution of
local changes
2
Master Data
Harmonization
Examples:
„ Business Partner administration
„ Central provision of sales articles
„ Definition and administration of
non-variable parts
SAP MDM supports an
incremental approach to a
cohesive master data
management in a
distributed and heterogeneous environment
3
Central Master
Data Management
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 32
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
16
SAP TechEd ‘03 Las Vegas
Master Data Consolidation with SAP MDM 2.0 –
Scenario
MDM
MDM
Master data harmonization
Client
SAP
9
+
Local
Creation
Client
non SAP
Central
Creation
Local
Completion
1.234.237 €
=?
Matching &
ID Mapping
9
+
6.674.288 €
634.237 €
4.002.531 €
737.108 €
=
9
13.282.401 €
Client
SAP
9
Distribution
Client
non SAP
2
Analytics
Core Process Steps:
1. Central Creation of master data
objects just covering the global
information of the master data object
2. Local Creation within the master data
environment of the application
system (client) and distributing their
global information to MDM
3. Continuous matching processes
identify duplicates and result in
ID Mapping between them
4. Distribution of global master data
information to the various clients
5. Local Completion of master data
within the local environment
6. Use of ID Mapping information for
MDM Analytics like business-wide
analyses etc.
Description of a master data object:
Æ Globally relevant Data
Æ (Client) specific Data
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 33
What does this mean to SAP BW Master Data Loads?
MDS
MDS
CI
CIKey
KeyMapping
MappingInformation
Information
Syst.
Syst.CRM
CRMC1
C1Product
Product5712
5712
Syst.
Syst.R/3
R/3S1
S1Product
Product4711
4711
Syst.
Syst.R/3
R/3S2
S2Product
Product4711
4711
Syst.
Syst.R/3
R/3S1
S1Product
Product4712
4712
Matching
MatchingProcess
Process
Main
MainMatching
MatchingProcess
ProcessProduct
Product
Sec.
Sec.Matching
MatchingProcess
ProcessProduct
Product
MDM-BW
MDM-BW
Extractor
Extractor
for
for
Key
Key
Mapping
Mapping
++
Attributes
Attributes
4 Result Records
for one
Product Record
CRM
CRMC1
C1Key
KeyMapping
Mapping++Attributes
Attributes
R/3
R/3S1
S1Key
KeyMapping
Mapping++Attributes
Attributes
R/3
R/3S2
S2Key
KeyMapping
Mapping++Attributes
Attributes
R/3
R/3S1
S1Key
KeyMapping
Mapping++Attributes
Attributes
MDS
MDSMaster
MasterData
DataRecord
Record
Product
Product0815
0815with
withAttributes
Attributes
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 34
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
17
SAP TechEd ‘03 Las Vegas
SAP MDM Extractors for Business Partner and
Product
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 35
SAP MDM Extractor: Product Key Mapping
Information
System
System
R/3-S1
R/3-S1
Product-ID
Product-ID
4711
4711
Group-ID
Group-ID
0815
0815
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 36
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
18
SAP TechEd ‘03 Las Vegas
Extraction Result on the SAP MDM Server Site
MDC
MDM
MDC
MDM
Global IDs
MDM
System and
Object Information
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 37
Scenario II : Extracting Global SAP MDM Data
SAP
SAP BW
BW
0PRODUCT
SAP
SAP MDM
MDM
IS: Global Product
strategic
strategic
0MATERIAL
0_ORA
0BBP_PROD
0CRM_PROD
IS: Material
IS: ORA
IS: BBP Prod
IS: CRM Prod
operational
operational
Æ Common Identifying Data
Æ Global master data info
Clients
Clients
R/3 Material
ORA Service
EBP Product
CRM Product
R/3
R/3
R/3
Oracle
R/3
R/3
EBP
R/3
R/3
CRM
R/3
R/3
=9
Distribution
XI
XI
9
+
9
9
+
ID Mapping
Description of a master data object:
Æ Common Identifying Data
Æ master data info
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 38
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
19
SAP TechEd ‘03 Las Vegas
Product: Global Attributes – Best Practices
ÎKeep the consolidated InfoObjects very lean!
„ Only attributes used for global reporting are relevant.
ÎDon’t flood them with attributes of local views!
Global attributes delivered by SAP can only be
„ Consolidated InfoObjects
„ InfoObjects with unified or standardized values in all source
systems
„ DUNS number, UNSPSC code, e-Class, ISO codes
ÎCustomer can add own standardized attributes
depending on his master data model.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 39
0PRODUCT - Key Concatenation in Update Rule
Business
Content
Filling
Filling the
the
Product
Product Key
Key
via
via
concatenation
concatenation
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 40
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
20
SAP TechEd ‘03 Las Vegas
0PRODUCT – Filling the Local Key in Update Rule
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 41
0PRODUCT – Filling the Source System
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 42
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
21
SAP TechEd ‘03 Las Vegas
Consolidated InfoObjects: Transactional Data Flow
InfoSource
Master
Data
ODS
object
Info
Cube
MDM
Key Mapping
Information
Consolidated InfoObjects (Example: 0PRODUCT)
ODS
object
InfoSource
Info
Cube
ODS
object
Master
InfoSource
Data
Info
Cube
ODS
Master object
Data
Master
Data
SAP R/3 object model
(namespace 0*)
Example:
0MATERIAL
mySAP CRM/EBP OM
(namesp. 0CRM_*,
0BBP_*)
Example:
0CRM_PROD
R/3
Sources
R/3
Sources
R/3
R/3Sources
Sources
EBP/CRM
Info
Cube
InfoSource
Oracle OM
(namesp. 0ORA_*)
Example:
0ORA_PROD
Oracle
R/3 Sources
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 43
SAP BW Scenario II - Summary
•• A
A more
more complex
complex challenge
challenge
•• Main
Main flow
flow of
of Master
Master Data
Data into
into SAP
SAP BW
BW is
is still
still coming
coming from
from client
client
systems
systems
•• Consolidated
Consolidated InfoObjects
InfoObjects in
in SAP
SAP BW
BW available
available as
as aa kind
kind of
of
Business
Content
for
SAP
MDM
(here
0PRODUCT)
Business Content for SAP MDM (here 0PRODUCT)
•• No
No further
further SAP
SAP MDM
MDM Business
Business Content
Content available,
available,
InfoSources
InfoSources and
and UpdateRules
UpdateRules have
have to
to be
be implemented
implemented manually
manually
•• Additional
Additional flow
flow of
of Master
Master Data
Data information
information on
on the
the Consolidated
Consolidated
InfoObject
level
coming
from
SAP
MDM
has
to
InfoObject level coming from SAP MDM has to be
be implemented
implemented in
in
SAP
BW
SAP BW
•• Complex
Complex Master
Master Data
Data Harmonization
Harmonization in
in SAP
SAP BW
BW does
does also
also affect
affect
the
the management
management of
of transactional
transactional data
data
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 44
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
22
SAP TechEd ‘03 Las Vegas
Agenda
Introduction
„ Application optimization example: mySAP SRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 45
Overview – SAP BW/MDM Scenarios and Benefits
An SAP Customer with a productive SAP BW Environment wants to
implement SAP MDM.
¾ Scenario I
Minimal involvement of SAP MDM in SAP BW Master Data extraction for
operational reporting needs
¾ Scenario II
Global consolidation of SAP BW Master Data via SAP MDM for strategic
reporting needs in SAP BW
An SAP Customer without an SAP BW Environment wants to
implement SAP MDM and SAP BW
¾ Scenario III
Maximized and optimized embedding of SAP MDM in the SAP BW
Master Data extraction process
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 46
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
23
SAP TechEd ‘03 Las Vegas
Scenario III
An SAP customer has several mySAP components in productive use.
There is no data warehouse solution implemented so far.
SAP BW/MDM are implemented in one step in order to benefit from
synergy between both solutions.
The main goal of the project is to reduce the data flow between SAP
MDM Clients and SAP BW to just transactional data.
All master data distribution has to be realized via the SAP MDM.
SAP BW will extract its master data from the SAP MDM Server only.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 47
SAP MDM – An Incremental Approach
1
Central
Master Data
Content
Management
Consolidation
„ All of Content Consolidation PLUS
„ All of Master Data
Harmonization PLUS
„ All master data information
resides centrally
„ One stop data maintenance
Examples:
2
Master Data
„ Definition of synergy parts
Harmonization
„ Central product data pool supplying
product data to multiple locations for
production, assembly, sales and
distribution.
SAP MDM supports an
incremental approach to a
cohesive master data
management in a
distributed and heterogeneous environment
3
Central Master
Data Management
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 48
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
24
SAP TechEd ‘03 Las Vegas
Master Data Consolidation with SAP MDM 2.0 –
Scenario
MDM
MDM
3
Central Master Data
Management
Client
SAP
Core Process Steps:
9
9
w/o Local
Maintenance
Central
Creation
Client
non SAP
1.234.237 €
6.674.288 €
634.237 €
Distribution
4.002.531 €
737.108 €
=
9
13.282.401 €
=9
ID Mapping
9
Client
SAP
1. Central Creation of master data
objects covering the complete
information as used later in the local
application systems (clients)
2. Distribution of centrally maintained
master data information as individual
objects as they are defined in the
local application systems
3. Use of master data within local
application processes w/o local
maintenance
4. Use of ID Mapping information for
MDM Analytics like business-wide
analyses etc.
Analytics
Description of a master data object:
Æ Common Identifying Data
Æ Complete master data info
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 49
Initializing SAP BW Master Data from Central SAP
MDM
SAP
SAP BW
BW
InfoSource: Global
0PRODUCT
Product
SAP
SAP MDM
MDM
mandatory
mandatory
0MATERIAL
0_ORA
0BBP_PROD
0CRM_PROD
IS: Material
IS: ORA
IS: BBP Prod
IS: CRM Prod
R/3 Material
ORA Service
EBP Product
CRM Product
R/3
R/3
R/3
Oracle
R/3
R/3
EBP
R/3
R/3
CRM
R/3
R/3
Æ Common Identifying Data
Æ Global master data info
Clients
Clients
=9
9
+
9
9
+
Distribution
ID Mapping
XI
XI
Description of a master data object:
Æ Common Identifying Data
Æ master data info
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 50
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
25
SAP TechEd ‘03 Las Vegas
SAP BW Scenario III - Summary
•• Simplified
Simplified Mater
Mater Data
Data Handling
Handling in
in SAP
SAP BW
BW
•• Entire
Entire Master
Master Data
Data flow
flow is
is shifted
shifted from
from SAP
SAP MDM
MDM Clients
Clients
to
to the
the SAP
SAP MDM
MDM Server
Server
•• Identifying
Identifying global
global and
and local
local Master
Master Data
Data Attributes
Attributes are
are provided
provided
by
the
SAP
MDM
Server
to
cover
the
needs
on
strategic
by the SAP MDM Server to cover the needs on strategic and
and
operational
operational reporting
reporting level
level in
in SAP
SAP BW.
BW.
•• Transactional
Transactional data
data flow
flow into
into BW
BW is
is not
not affected
affected but
but relies
relies on
on
availability
availability of
of consistent
consistent master
master data
data
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 51
Agenda
Introduction
„ Application optimization example: mySRM Global
Spend Analysis
SAP BW – Scenarios for Master Data load
„ Scenario 1
„ Scenario 2
„ Scenario 3
Summary
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 52
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
26
SAP TechEd ‘03 Las Vegas
Summary: Master Data Flow Scenarios for SAP BW I
SAP
SAP BW
BW
SAP
SAP MDM
MDM
Business
BusinessContent
Content
Areas
Areas
0MATERIAL
11
Operational
OperationalReporting
Reporting
(localized,
(localized,unified)
unified)
MATNR
ERP
ERPSolutions
Solutions
MATNR
MATNR
MATNR
XI
XI
mySAP
mySAP
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 53
Summary: Master Data Flow Scenarios for SAP BW II
SAP
SAP BW
BW
SAP
SAP MDM
MDM
Strategic
Strategic
(global,
(global,consolidated)
consolidated) 0PRODUCT
All
AllGlobal
GlobalAttr.
Attr.
Operational
OperationalReporting
Reporting
(localized,
(localized,identified)
identified)
...
0EBP_PROD
0CRM_PROD
0MATERIAL
22
Global
Globaland
andlocal
localAttributes
Attributes
...
...
...
MATNR
XI
XI
Global
GlobalAttr.
Attr.
mySAP
mySAP
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 54
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
27
SAP TechEd ‘03 Las Vegas
Summary: Master Data Flow Scenarios for SAP BW III
SAP
SAP BW
BW
SAP
SAP MDM
MDM
Strategic
Strategic
0PRODUCT
...
0EBP_PROD
0CRM_PROD
0MATERIAL
Operational
Operational
33
...
...
...
MATNR
XI
XI
mySAP
mySAP
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 55
SAP MDM 2.0: Relevant Objects for SAP BW
04.-06.09.2002
28.02.2003
SAPPHIRE `02 Lisbon
SAP MDM first
announcement
Development
Closed
Start Product Ramp-Up
Q3.2003
Business Partner
Product Master
Technical Asset
Scope of
Delivery for
SAP MDM
2003
Product Structure
Documents
Change Management
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 56
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
28
SAP TechEd ‘03 Las Vegas
Further Information
Î
Public Web:
www.sap.com/solutions/netweaver/masterdata
SAP Customer Services Network: service.sap.com/mdm/
Î
Consulting Contact
Roy Wood, VP SAP NetWeaver Consulting Practice ([email protected])
Î
Related SAP Education Training Opportunities
www.sap.com/education/
BW310, SAP BW Modeling
Î
Related Workshops/Lectures at SAP TechEd 2003
SRM102, Master Data Consolidation and Catalog Management..., Beginner
MDM201, SAP MDM as a Key Technology of SAP NetWeaver, Intermediate
BW205, Concept of Consolidated InfoObjects in SAP BW, Intermediate
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 57
Questions?
Q&A
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 58
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
29
SAP TechEd ‘03 Las Vegas
Feedback
Please complete your session evaluation and
drop it in the box on your way out.
Thank You !
The SAP TechEd ’03 Basel Team
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 59
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 ServerTM are trademarks of IBM Corporation 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.
„
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.
„
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.
„
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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.
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 60
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
30
SAP TechEd ‘03 Las Vegas
SAP TechEd `03 EMEA
Online
WATCH THE
REPLAYS,
DOWNLOAD THE
SLIDES, AND READ
THE TRANSCRIPTS.
www.sap.com/community
 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 61
© 2003 SAP Labs, LLC
BW 206, Rainer Uhle
31