oct 2007 - using sap mdm to take control of your data - saphila cape town prinsloo adidas

8/8/2019 Oct 2007 - Using SAP MDM to Take Control of Your Data - Saphila Cape Town Prinsloo Adidas

http://slidepdf.com/reader/full/oct-2007-using-sap-mdm-to-take-control-of-your-data-saphila-cape-town-prinsloo 1/16

1

USING SAP MDM TO TAKE CONTROL OF YOUR DATA

Naas Prinsloo

Head of Global Data Management

November 2007



2

Agenda

adidas Group

Business Impact of “bad” Data

Business Solution

Supplier - Benefits achieved

Product – Approach and benefits

Lessons Learned



4

Business Impact of “bad” Data

Financial…..• Sales orders can be placed for articles that have been reserved specifically for

certain customers. Orders must then be cancelled ($ 2.6m per year)• Range Plans suboptimal due to incomplete key data. Sales lost in first

production month due to order cut-off dates missed ($ 3.4m per year)• and many more examples…..

Business losing face…..• Promise to customers not kept• Forecasts incorrect• Allocation of products to markets and sales channels either wrong or not

possible• Resources spend a lot of time to rework data

IT issues…..• Cost and time to integrate new applications• Cost and time to enhance current applications to meet new business realities• Unnecessary point-to-point application interfaces and multiple TIB messages

for one data object



5

What is Data Management for the adidas Group

Meta DataMeta Data (Data definition, business rules, format, length)

Reference DataReference Data

Master DataMaster Data

Transaction DataTransaction DataBIBI

S t r a t e g y

G o v e r n a n c

e

( i n c l . o w n e r s h

i p )

P r i n c i p l e s & P o l i c i e s

S t a n d a r d s

P r o c e s s e s

O r g a n i s a t i o

n

A p p l i c a t i o n & T o o l s

G l o b a l D a t a M o d e l

G l o b a l D a t a M o d e l

Country level

Area level

Region level

Organization

OtherProductCustomerSupplier

OtherProduct typeBrand

InvoiceSales Order Other

The end-goal of

Data Management:

What is needed to

reach the end-goal:

What are the

foundations as

input to reach the

end-goal:

C h a n g e M a n a g e m e n t

Data Quality(definition, content, structure, distribution)

- Making a commercial difference

- Solve business problems- Enable Group solution (all brands)- End-to-end (no silo’s)



6

Business Solution

“How does centralized MDM fit into the overall adidas applicationlandscape?”

SAPMDM

Application Integration

Management

reportingOperational

systems

Master & reference data

Master & reference data Master & reference data

PlanningOrderingPLMEtc.

BW

• Master and reference data maintained in ONE place (MDM)• Standardized, guaranteed data delivery• Maintenance switched off in downstream systems• Workflow notifications when master data changes



7

Business Solution

“Supplier: before”

IBSupplierprofile/

evaluationform(s)

Excelform

E-mail

RMS ILS

ILA

PDM

FLSTechnicalevaluation

form

SOE form

Mfgagrmt.

Beneficiarydetails

Accountdetails

ESC

SAP FI/CO

MADB

SEIS

FLSExcel

Supplier

LO Planner R. Miles

LO Tech Service

Ed Gavin

Erin Sciaraffo

SEA Dept

Legal Dept

Anthony Hearder Diana Chan

Finance Dept

Ivan Ho

Oliver Kwok

• No single system of reference• Different sources of data• No alignment between systems• Different timing between updates• Little/no alignment between people



8

Business Solution

“Supplier: after”

Supplier

FLSIBFFC ILA PDMILSESC SAPFI/CO

RMS

MDM-S

Stakeholders

Data translations fordownstream systemsdone in MDM

Automated, guaranteeddelivery of data

24 other systems containingsupplier data

20 key fields at 4 sigma(99.37%) data quality level. Maintenance switched off in these systems

Simplifiedsupplier

evaluationthat

containssections for

technicalprofile,financial

profile, SOEprofile, MA,beneficiarydetails, etc.

LO Planner LO Tech Svc. SEA Dept. Legal Dept. Finance Dept.

On-line capturing

Automatedworkflow

notifications



9

Supplier - Data quality

Supplier KPI Quality By Period

0%

20%

40%

60%

80%

100%

120%

2 3 4 5 6 7 8 9 10 11 12 1 2 5 7 10 11 1

2005 2006 2007

Time Period

Q u a l i t y L e v e l P e r c e n t

All Statuses

Approved/Active

Status



10

Supplier - Benefits achieved

• For the first time, supplier master data is under control

• One global process to maintain supplier data – adapted by all brands

• Time to establish a new supplier reduced by 45%

• Clear data ownership established – The Snr VP (Global Sourcing) isthe steward for Supplier data

• Simplified application landscape and “one version of the truth”



11

Product - Approach

“Product: today”

• IAM: Not all data fields; only contains adidas brand data• ALL master data captured in PLM, minimum validations• IAM only receives data when product is commercialized – if

data needed earlier, IAM is bypassed• Different timing between updates (daily, weekly) - batch• Non-standard integration to/from IAM

FootwearPLM

ApparelPLM

IAM

LocalArticle

Creation

ERP Other

99

InternationalArticle Master

Ranging

6464

Product Hierarchy

Time Period

Org Views

Materials

Size/Width

Customs

Product NameColor

Digital Assets

Packaging

Pattern

Price

Tooling

Planning

BOM Catalog

Product Hierarchy

Time Period

Org Views

Materials

Size/Width

Customs

Product NameColor

Digital Assets

Packaging

Pattern

Price

Tooling

Planning

BOM Catalog

Scope of IAM vs. what business reallyneeds



12

Product – Approach – Current complexities

ILS -Special

MARLIS AC

RETAIL DWH

SAP AFS

AC/aUS/aJapan/aItaly

SALOMON -

Special

BV-II

RMA GDWH

SAP BW

RBO 3.7 FLS DMT

SIM ILA POD

RMS

LAC

Reebok/10

countries&categories

PDM

USACUSTOMS

DWHPLM/Retail

FTW V&W

aFACTORIES

LAM

Adirace(27)/Sarragan/SportStyle/ aKorea/Tmag Korea/ aRetail/aAustralia

LAC

27 ADIRACE COUNTRIESSarragan/SportStyle/Korea

Tmag/aRetail/ aMoscow

Weekly FTPs

Scheduled FTPs

once/twice a day

FTPs

TIBCO Bus

UK WMS

T I B C O B u s

IAM

Shared

Tables aCanadaaKorea

Thalis

Moerdijk WMS

Mediabin

Taylormade-Special

‘Upstream Apps’

IB

‘Downstream Apps’

Infowerk

Master DataTeam - Ranges

Master DataTeam -

Reservation

UPC Assignemt

aCanada/aUS/T

hirdParties

LAM

Salomon/Tmag/NBA/Third

Parties

Article Request

Tmag/Salomon

/SAP aUS,aAustralia,aJa

pan,AC/Marl isAC

SAP / AFSAustralia

RBO 3.6

MDU Japan

On demand FTPs

IB HGK

RMS

Tibco

Weekly Mail

< 50MB

GUI-Reference data

GDM Team

GUI-Master data

LAmerica,aFrance,aUS

aHongKong

ILS -Special

MARLIS AC

RETAIL DWH

SAP AFS

AC/aUS/aJapan/aItaly

SALOMON -

Special

BV-II

RMA GDWH

SAP BW

RBO 3.7 FLS DMT

SIM ILA POD

RMS

LAC

Reebok/10

countries&categories

PDM

USACUSTOMS

DWHPLM/Retail

FTW V&W

aFACTORIES

LAM

Adirace(27)/Sarragan/SportStyle/ aKorea/Tmag Korea/ aRetail/aAustralia

LAC

27 ADIRACE COUNTRIESSarragan/SportStyle/Korea

Tmag/aRetail/ aMoscow

Weekly FTPs

Scheduled FTPs

once/twice a day

FTPs

TIBCO Bus

UK WMS

T I B C O B u s

IAM

Shared

Tables aCanadaaKorea

Thalis

Moerdijk WMS

Mediabin

Taylormade-Special

‘Upstream Apps’

IB

‘Downstream Apps’

Infowerk

Master DataTeam - Ranges

Master DataTeam -

Reservation

UPC Assignemt

aCanada/aUS/T

hirdParties

LAM

Salomon/Tmag/NBA/Third

Parties

Article Request

Tmag/Salomon

/SAP aUS,aAustralia,aJa

pan,AC/Marl isAC

SAP / AFSAustralia

RBO 3.6

MDU Japan

On demand FTPs

IB HGK

RMS

Tibco

Weekly Mail

< 50MB

GUI-Reference data

GDM Team

GUI-Master data

LAmerica,aFrance,aUS

aHongKong



13

Product - Approach

“Product: mid-term solution”

• Product creation – holds dataneeded for product creation only

• MDM holds all product data forentire Group (all brands)

• All product data published by MDM – standard interface

• All data enrichment occurs in MDM• Online data validations in MDM• Data publishing based on business

event (not batch) from MDM• IAM replaced – cost savings of

$2.6m per annum

SAPMDM

Management

reportingOperational

systems

Master &reference data



PlanningOrderingetc.

BW

Application Integration

ProductCreation

Productcreationdata

Productcreation

data



14

Product – Mid-term benefits

• One “version of the truth” for product data (all brands)

• All master data owners enrich product data in one place – including lifecycle management

• 9 systems for capturing local product data is eliminated

• Standardized integration design – makes adding of new systems easier

• Lag of 6 to 8 weeks between product creation and MDM eliminated – Product planning, etc can happen sooner

• Improved data quality due to online data validations

• Product master data quality KPI’s and reports in one place (MDM)



15

Lessons learned

• Repeat: Very high-level sponsorship needed to succeed

• The concept of centralized data management works

• You do not just implement a new tool – process and organization willchange as well

• Refine your end-to-end processes, do not re-implement complexities

• Make use of consultants if the concepts are new in your organization(SAP, SITACORP)



16

Using SAP MDM to take control of your data - your turn

Questions?

oct 2007 - using sap mdm to take control of your data - saphila cape town prinsloo adidas

Documents