peter aynsley-hartwell utopia inc

Produced by:Platinum SponsorPremier Sponsor

Peter Aynsley-HartwellUtopia Inc.

Marvels of Material Master DataSolved

with SAP Business ObjectsCarla Cook

Suncor(C Cubed Information Services Inc)

Bill TowsleySuncor

Suncor Overview

The Data Migration Project

The Tools & Approach

The Reality and The Results

Key points to Take Home

Questions

What We Will Cover

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)

Data Migration Project

Slide 5

Overall Scope

• Integrate former Petro-Canada processes and data into Suncor SAP

• Legacy Systems

Source:oPeopleSoftoSAP ECC 6.0oSAP CRM

Target:oSAP MDMoSAP ECC 6.0oSAP CRMoSAP SRM

Slide 6

• SAP Moduleso FI/CO, MM, SD, PM,PS, HRM, CRM, SRM

• 80 Objects requiring ETL (Extract Transform Load)o 30 Objects managed with SBO Data Services

• Total timeframe of 13 months with 3 staged releaseso Systems Integration – Deloitteo Data Migration – Suncor/SAP/Utopiao SAP Support - IBM

Overall Scope

Slide 7

The Data Migration Project

Project Timelinesand

SBO Data Services Landscape

8

2010 2011 2012

Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

R3 go-live (8/2)Deploy

SPIM Gate-4

I&O go-live (10/3)

Montréal go-live (10/31)

Edmonton go-live (1/30)

(2/11)

(4/15) (6/3)

(1/28)

100% Development (1/28)

R3 ITC1 R3 ITC2 R3 UAT

Para.

Perf.

Security Testing (increasing scope)

2 CCD’s & 70% Development (1/21)100% Config & Development (2/28)

QA2

QA3

Release System Freeze

R2B PSSP Testing (Sustain.)

R2B PSSP Deploy (Sustain.)

To Be Data Model

LPC User WB/Query Build/Test

Training Devel. Complete

BUILD

2nd Data Trial – All Objects (~12/17)

Functional Unit Testing

ITC Prep.

QA1

Change, Training & Communication

BPP Updates/Creation

Security Build

R2B HR GL Prep

Data Conversion Build / Cleansing

R2B PSSP Build (Sustain.)

Legacy PC to Suncor BW Migration

WB/Query Ration./Dispo.

Master Queries

FRICEW Build – FUT Readiness

Priority 3(12/15)

HR FUTFUT Prep.

HR Build R3/R4HR PR1 HR PR3HR PR2

(7/1)

(3/18)

Key Milestone / Interim Milestone/Deliverable Completion Dates

Phase Completion Milestone Dates

S1 S2 S3

(2/11)

(6/3)

(7/1)

S1 S2 S3

R3 Integration Testing

Data Cleansing

(3/25)

Slide 9

DEV

SAP QDR4 Client

305

LPC Prod Copy

IQ2

Extract data to be moved

Load converted data

ExtractConfiguration Oracle DB/Server

500GB

SAP QSR4

LPC ProdIPR

Extract data to be moved

Load converted & de-duplicated data

Extract

Configuration Oracle DB/Server500GB

Suncor ProdPR1

Extract data to

de-duplicate

QA

SAP QSR4

Final Build

LPC ProdIPR

Extract data to be moved

Load converted & de-duplicated data

Extract

Configuration Oracle DB/Server500GB

Suncor ProdPR1

Extract data to

de-duplicate

PROD

Landscape - SBO Data flows in the Suncor Landscape

Slide 10

The Data Migration Project

Data Migration Challenges

Slide 11

Data Migration Challenges

• Extracting from a live production systemo Difficult to do cleansing, de-duplication at source

• Loading live into production landscapeo Need to move millions of records in a short time without

disrupting existing system

• Complex data mappingo Source and target not nearly the same configuration

Slide 12

Data Migration Challenges

• Moving targeto Short time frame means developing while continuing to refine

data mapping spec

• Agile ETL requiredo Needed to be able to ETL, validate, refine, repeat

• De-duplication

• Data cleansing after extract

Slide 13

The Data Migration Project

Tools and Approach

TechnologyApproach and Methodology

Organization

Slide 14

Technology

• SAP Business Objects Data Services

• SAP NetWeaver MDM

• SAP Legacy System Migration Workbench

• SAP Standard IDOCs (Intermediary DOCument)

• Custom ABAP programs

Slide 15

Technology

The SAP BusinessObjects Data Services

Approach and Methodology

Slide 16

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.

Slide 17

Approach and MethodologyLegacy Data Environment

Data Staging and Test Environment

XML

Applications

Databases

Flat Files/Excel

Extract & Profile

Staging Area

SAP

Target Environment

Data Services Platform

Cleanse

Name Parsing

Address Parsing & CorrectionMaterial/Product ParsingMatching

SAP Configuration

Extraction

Reconciliation

Performance Analysis

Dashboards and Business Reporting

Transparency, Communication

and Governance,

Loading

LSMWFiles

IDocs

Pre-Built load routines for SAP Objects

Validate & Load

Transform

Business Validation

RulesAutomatic SAP Config Validation

TransformData into SAP

structure

Slide 18

Approach and Methodology

Slide 19

Organization - Data Mgmt Operational Structure

Slide 20

Organization

ETL Team

SBO MDMBusiness

Function

DM

Focal (lead)

30 Objects6 on-shore

4 off-shore

3 on-shore

3 off-shore30 on-shore

5 on-shore (split between 30 objects)

Slide 21

The Data Migration Project

The Reality and The Results

Why ETL?How we utilized the tools

BenefitsWhat would we do differently?

Slide 22

Sample Data Objects – why ETL

Object Volume

(Source)

Complexity Data Quality

Transformation

Rules

Volume

(Target)

Pricing Conditions

1,000,000 High High Complex 1,000,000

Vendor 95,000 Medium Low Complex 15,000

Product – Light Oils

339 High High Complex 339 x

1500 plants

508,500

Slide 23

How we utilized the tools

• A look under the hood at the Material Master ETL

Slide 24

Materials: Data Flow & Implementation Steps

PC DATA(SAP - IPR)

SBOLEIHZ005Z006Z007Z008Z013Z015Z016Z017

XML

Dedupe / Match / Validate

NOTES:* Neither SBO or MDM are pulling in Suncor Materials

* MDM will have no data to begin

1

XML files on MATMAS05

format> 1000 records

each file

2

SBO Tasks

Scenario #1 (update)•LPC Material exists in Suncor.

•We will need to extend the Suncor Material with the PC plant

Scenario #2 (Create)• LPC Material does not exist in Suncor

• Material to be created and duplicate MATNRs to be added to record

MDM

SAPIR4

MATNR comes back

PI

Import Materials into MDM via XML

Implement scenarios below.

XREF

3

4

MDM Tasks

5 Sequential updates

6X-ref

LEIH – LEIHHIBE – Z005, Z007, Z013, Z016RHIB/FHIB – Z006? - Z008Z015 – Service masters? - Z017?

Data

Slide 25

Slide 26

Slide 27

Slide 28

Slide 29

The Benefits - Compare Release 1 with Release 3

• Release 1 (July 2010)o ETL using ABAP and SAP MDM

oExtract from source, transform in-flight load to MDMoMapping changes required ETL re-process(14 hrs for Materials)

• Release 3 (July 2011)o Utilizing SAP Business Objects Data Services and the SAP

Data Migration FrameworkoMapping changes require only a re-run of specific SBO jobs

(minutes not hours)

Slide 30

The Benefits - Utilized SAP Technology

• Connect directly to SAP for extraction by OBJECTo Utilizes the data model table structures and relationships

• IDOCS for Loadingo Using standard IDOC identified inappropriate screen

customizations transported into the target system

Slide 31

The Benefits - Utilized SAP Technology

• Pre-Validation of Check Values before loadingo No requirement for trial loads to test the datao Automatically adjusts for configuration changes

• Data in a common staging areao Easy to update and repeat if rules/requirements changedo Cross object validation easy

oeg PO ->Vendor -> Material -> PIR

Slide 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 loadso Test scenarios need to use loaded data and be flexible

• Understand the target configuration o e.g. Custom user-exits on forms not supported by BAPIs

Slide 33

Key Points to Take Home

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

What worked for Suncor

Produced by:Platinum SponsorPremier Sponsor

Bill TowsleySuncor Energy

btowsley@suncor.com

Peter Aynsley-HartwellUtopia Inc

peter@utopiainc.com

Carla CookSuncor Energy

(C Cubed Information Services)carla.cook@ccubedis.com

Produced by:Platinum SponsorPremier Sponsor

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

Huntington Beach, California

Slide 37

SAP Data Migration Framework

Subhead (Arial 40 Bold)

• Text (Arial 40 Regular)o Demoted Text (Arial 34 Regular)

Slide 38

Slide 39

The Reality and The Results

Slide 40

The Reality and The Results

Slide 41

The Reality and The Results