1. Marvels of Material Master Data Solved with SAP Business Objects
Carla Cook
Suncor (C Cubed Information Services Inc)
Bill Towsley
Suncor
Peter Aynsley-Hartwell
Utopia Inc.

2. What We Will Cover Suncor Overview The Data Migration Project
The Tools & Approach
The Reality and The Results
Key points to Take Home
Questions

3. Suncor Energy
Suncor Energy is the largest Canadian Oil and Gas company
300,000 plus bbls/day synthetic crude oil
4 refineries totaling 450,000 bbls/day
1,500 plus retail and wholesale outlets
350 different lubricant and specialty fluid products
Implemented SAP enterprise-wide in 2006
Owner of Petro-Canada (SAP since 1993)

4. Data Migration Project

5. Overall Scope
Integrate former Petro-Canada processes and data into Suncor SAP
Legacy Systems
Source:
PeopleSoft
SAP ECC 6.0
SAP CRM
Target:
SAP MDM
SAP SRM

6. Overall Scope SAP Modules FI/CO, MM, SD, PM,PS, HRM, CRM, SRM
80 Objects requiring ETL (Extract Transform Load)
30 Objects managed with SBO Data Services
Total timeframe of 13 months with 3 staged releases
Systems Integration – Deloitte
Data Migration – Suncor/SAP/Utopia
SAP Support - IBM
Slide 6

7. Project Timelines and SBO Data Services Landscape
The Data Migration Project
Project Timelines and SBO Data Services Landscape
Slide 7

8. 2010 2011 2012 Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct
R3 Integration Testing
M&D Lubes
R3 go-live (8/2)
I&O
Montréal
Edmonton/Burrard (non-distribution)
BUILD
(2/11)
Deploy
QA1
R3 ITC1
(3/18)
R3 ITC2
R3 UAT
(6/3)
I&O go-live (10/3)
QA2
(4/15)
(7/1) S1 S2 S3
Montréal go-live (10/31)
FRICEW Build – FUT Readiness
100%
Development (1/28)
(6/3)
QA3
Priority 3
(12/15) S1 S2 S3
Edmonton go-live (1/30)
(2/11)
Functional Unit Testing
Para.
Perf.
(7/1)
Data Conversion Build / Cleansing
Data Cleansing
2nd Data Trial – All Objects (~12/17)
ITC Prep.
(3/25)
BPP Updates/Creation
Change, Training & Communication
Training Devel. Complete
(1/28)
Release System Freeze
Security Build
Security Testing (increasing scope)
Legacy PC to Suncor BW Migration
To Be Data Model
SPIM Gate-4
Master Queries
WB/Query Ration./Dispo.
LPC User WB/Query Build/Test
R2B PSSP Build (Sustain.)
R2B PSSP Testing (Sustain.)
R2B PSSP Deploy (Sustain.)
HR Build R3/R4
FUT Prep.
HR FUT
HR PR1
HR PR2
HR PR3
2 CCD’s & 70% Development (1/21)
R2B HR GL Prep
100% Config & Development (2/28) 8
Key Milestone / Interim Milestone/
Deliverable Completion Dates
Phase Completion Milestone Dates

9. Landscape - SBO Data flows in the Suncor Landscape
DEV
SAP Q
DR4 Client
305
LPC
Prod Copy
IQ2
Extract data
to be moved
Load converted data
Extract
Configuration
Oracle DB/Server
500GB
SAP Q
SR4
LPC Prod
IPR
Extract data
to be moved
Load converted & de-duplicated data
Extract
Configuration
Oracle DB/Server
500GB
Suncor Prod
PR1 to
de-duplicate QA
SAP Q
SR4
Final Build
LPC Prod
IPR
Extract data
to be moved
Load converted & de-duplicated data
Extract
Configuration
Oracle DB/Server
500GB
Suncor Prod
PR1 to
de-duplicate
PROD
Slide 9

10. Data Migration Challenges
The Data Migration Project
Data Migration Challenges
Slide 10

11. Data Migration Challenges
Extracting from a live production system
Difficult to do cleansing, de-duplication at source
Loading live into production landscape
Need to move millions of records in a short time without disrupting existing system
Complex data mapping
Source and target not nearly the same configuration

12. Data Migration Challenges
Moving target
Short time frame means developing while continuing to refine data mapping spec
Agile ETL required
Needed to be able to ETL, validate, refine, repeat
De-duplication
Data cleansing after extract
Slide 12

13. Technology Approach and Methodology Organization
The Data Migration Project
Tools and Approach
Technology Approach and Methodology Organization
Slide 13

14. Technology SAP Business Objects Data Services SAP NetWeaver MDM
SAP Legacy System Migration Workbench
SAP Standard IDOCs (Intermediary DOCument)
Custom ABAP programs

15. Technology
The SAP Business Objects Data Services

16. Approach and Methodology
Utilised SAP Best Practices for Data Quality
SAP’s Enterprise Information Management (EIM) Best Practices provides a repeatable process to deliver consistent, sustainable results.
Implementation of business rules provides automation of key processes for the data migration process.
Integrate quality checks into all data touch points for on-going data governance.
Data Quality for all data: Customer, Supplier, Product, and beyond.
Manages the process throughout the entire ETL event.

17. Approach and Methodology
Legacy Data Environment
Data Staging and Test Environment
Loading
LSMW
Files
IDocs
Pre-Built load routines for SAP Objects
Target Environment
Dashboards and Business Reporting
Performance Analysis
Staging Area
SAP
Configuration
Extraction
SAP
Flat Files/
Excel
Data Services Platform
Cleanse
Name Parsing
Address Parsing & Correction
Material/Product Parsing
Matching
Validate & Load
Transform
Business Validation Rules
Automatic SAP Config Validation
Data into SAP structure
Extract & Profile
Databases
Applications
Reconciliation
XML
Transparency, Communication and Governance,

18. Approach and Methodology

19. Organization - Data Mgmt Operational Structure

20. Organization ETL Team SBO MDM Business Function DM Focal (lead)
30 Objects
6 on-shore
4 off-shore
3 on-shore
3 off-shore
30 on-shore
5 on-shore (split between 30 objects)
Slide 20

21. The Reality and The Results
The Data Migration Project
The Reality and The Results
Why ETL? How we utilized the tools Benefits What would we do differently?
Slide 21

22. Sample Data Objects – why ETL
Volume
(Source)
Complexity
Data Quality
Transformation
Rules
(Target)
Pricing Conditions
1,000,000
High
Complex
Vendor
95,000
Medium
Low
15,000
Product – Light Oils
339
339 x
1500 plants
508,500

23. How we utilized the tools
A look under the hood at the Material Master ETL
Slide 23

24. Materials: Data Flow & Implementation Steps
SBO Tasks
MDM Tasks 3
Import Materials into MDM via XML PI
PC DATA
(SAP - IPR)
Sequential updates 5 2
MATNR comes back
MDM 1
Dedupe / Match / Validate
LEIH – LEIH
HIBE – Z005, Z007, Z013, Z016
RHIB/FHIB – Z006
? - Z008
Z015 – Service masters
? - Z017?
SAP
IR4
XML
Data
SBO
LEIH
Z005
Z006
Z007
Z008
Z013
Z015
Z016
Z017
Implement scenarios below. 4
XML files on MATMAS05 format
> 1000 records each file 6
X-ref
XREF
Scenario #1 (update)
LPC Material exists in Suncor.
We will need to extend the Suncor Material with the PC plant
NOTES: * Neither SBO or MDM are pulling in Suncor Materials
* MDM will have no data to begin
Scenario #2 (Create)
LPC Material does not exist in Suncor
Material to be created and duplicate MATNRs to be added to record
Slide 24

25. Slide 25

26. Slide 26

27. Slide 27

29. The Benefits - Compare Release 1 with Release 3
Release 1 (July 2010)
ETL using ABAP and SAP MDM
Extract from source, transform in-flight load to MDM
Mapping changes required ETL re-process(14 hrs for Materials)
Release 3 (July 2011)
Utilizing SAP Business Objects Data Services and the SAP Data Migration Framework
Mapping changes require only a re-run of specific SBO jobs (minutes not hours)

30. The Benefits - Utilized SAP Technology
Connect directly to SAP for extraction by OBJECT
Utilizes the data model table structures and relationships
IDOCS for Loading
Using standard IDOC identified inappropriate screen customizations transported into the target system

31. The Benefits - Utilized SAP Technology
Pre-Validation of Check Values before loading
No requirement for trial loads to test the data
Automatically adjusts for configuration changes
Data in a common staging area
Easy to update and repeat if rules/requirements changed
Cross object validation easy
eg PO ->Vendor -> Material -> PIR
Slide 31

32. What would we do differently?
Follow best practices more stringently
Use the end-to-end process rather than break out to “existing” custom ABAP and LSMW
Not allow acceptance testing to be disconnected from data loads
Test scenarios need to use loaded data and be flexible
Understand the target configuration
e.g. Custom user-exits on forms not supported by BAPIs

33. Key Points to Take Home
What worked for Suncor
Slide 33

34. What worked for Suncor Establishing a strong data management team
Using standard processes and tools wherever possible
Using a robust ETL tool that met our key requirements of:
Flexibility
Agility
Repeatability

35. Peter Aynsley-Hartwell (C Cubed Information Services)
Bill Towsley
Suncor Energy
Peter Aynsley-Hartwell
Utopia Inc
Carla Cook
Suncor Energy
(C Cubed Information Services)
Q&A

36. March 27 – 30, 2011 Hyatt Regency Huntington Beach Resort and Spa
Huntington Beach, California

37. SAP Data Migration Framework
Subhead (Arial 40 Bold)
Text (Arial 40 Regular)
Demoted Text (Arial 34 Regular)

38. Slide 38

39. The Reality and The Results
Slide 39

40. The Reality and The Results
Slide 40

41. The Reality and The Results
Slide 41