Data Conversion Approach

Data Conversion Overview Our approach

Data Collection Standardize & Map & Data Load & • Focus on data readiness for the first few steps in
Analyze Profile Construct Sustain
& Setup Cleanse Transform Validation the data conversion process, as shown in the
Data Conversion Overview graphic.
• Assess data readiness along key dimensions of
data sourcing, completeness & accuracy,
The Data Collection & Setup In the data mapping, transformation, and standardization, duplication, and governance.
phase is aimed at loading phase, precise data mapping &
transformation programs are designed • Address supporting/enabling people, process,
understanding the current
and built. Additionally, data migration technology capabilities needed to improve data
state data objects in scope,
identifying relevant data strategy covering conversion build, readiness.
sources, and formulating testing cycles, cutover planning, data
sourcing requirements for data The Analyze, Profile, Cleanse and Construct validation etc. is finalized and executed.
migration. This helps prepare steps encompass all tasks related to analyzing
for data profiling, cleansing, data in scope for conversion, performing data
and migration next steps. profiling & cleansing, and constructing data to
support new requirements

Data Sourcing Ability to identify, locate, and source data for conversion to S/4HANA

Data Completeness Availability of structured data for key data types and attributes (i.e. no data gaps, missing attributes)

Data Standardization Existence of data standards and conformity of data against the standards (e.g. Nomenclature, taxonomy)
Data Profiling
Needs Data Duplication Existence of master data duplicates. Ability to accurately identify, match, and merge duplicate master data

Data Governance Level of governance oversight and processes around master data lifecycle, i.e. Creation, Read, Update, Deletion, Archiving of data

Technology Availability of necessary tools, technology, and skills to implement data profiling and cleansing
Enabling
People/Resources Identifying organizational support, data roles & responsibilities, key resource bottlenecks for data readiness
Capabilities
Process & Alignment Understanding data readiness activities and alignment with S/4 implementation program phases
 Data Profiling and Cleansing Process
Applying strict discipline in the execution of a robust data ONGOING ACTIVITY
quality process, the organization will benefit from executing • Identify Data Quality thresholds, metrics, and measure groups and
calibrate during periodic DQ cycles
a battle-tested approach to identify, diagnose, and deliver • Deploy iterative Data Quality sprints to design, deliver, expand, and
master data profiling and cleansing capabilities that drive optimize DQ monitoring capabilities
positive results. • Identify DQ remediation opportunities
• Prioritize DQ initiatives and define/refine data remediation
portfolio/roadmap
• Obtain approval of proposed remediation initiatives and commit
5. Sustain resources
• Execute remediation and validate results

• Identify in scope data objects and

• Review, analyze, and validate Data 1. Identify & required source systems
Quality outputs with business and IT. Stage source • Identify relevant tables/attribute
• Finalize & document the cleansing 4. Cleanse &
approach
data • Build jobs to extract and stage data
Analyse • Identify DQ rules & scenarios
• Based on the profiling results, cleanse
the data in source systems.

• Review DQ scenarios with Data Owners and

• Set up the profiling rules in the DP tool 2. Prioritize & prioritize.
• Run/Refine rules to get failed data set 3. Profile Build • Define sample set of Data profiling business rules
• Execute, generate and review profiled such as de duplication criteria, identify
data active/inactive data, mandatory fields etc., with
subject matter resources
• Design prototype DQ metrics engine with
exception reports and scorecard
• Set up the basic infrastructure and configure the
DP tool

2
Types of Data Cleansing (‘what’)
•Object (i.e. record) level cleansing:
– Objective: cleansing the object so it does or does not get extracted
– Example: ensure applicable old/non-relevant objects are flagged for deletion

•Attribute (i.e. field) level cleansing:

– Configurable fields:
• Objective: cleansing the attribute so it can get converted (1 to 1) or transformed (x to y)
• Example: ensure no payment terms are used that can’t or won’t be mapped to the target payment terms
– Text fields:
• Objective: cleansing the attribute to correct/increase the quality of the data
• Example: address validation, ensure phone numbers are following a consistent format
– Enrichment:
• Objective: populating missing data required in the target system
• Example: location on site customer

•Deduplication:
– Only applicable for customers (vendors: single in-scope source system, FIP, no duplicates)

3
Cleansing Approach (‘where’)
•Method 1 – Cleansing in source systems (recommended where feasible, must for object level cleansing):
– Discrete changes based on manual review upfront and/or mock 0, no ‘rule’ can be applied:
• Example: typo-corrections in text fields, replacement and/or removal of old/no longer applicable values
– Mass changes based on manual review upfront and/or mock 0, ‘rule’ can be applied:
• Example: rationalization of payment terms, e.g. replace net_30 and net.30 with net-30
• Example: activate deletion flag for all vendors/customers with name1=‘do not use’

•Method 2 – Cleansing during transformation:

– Address validation:
• Example: validate street, street number, postal code, city, state/province, country combination
• Addresses cleansed during transformation will need to be (1) reviewed and approved by Sobeys and (2) updated manually in the source
systems to ensure that addresses in target and source match
– Formatting corrections:
• Example: ensure consistent phone number format is being used
– Deduplication:
• Customer deduplication; Sobeys to confirm fields/rules to be used to identify duplicates (e.g. name1, key address fields)

•For each field in scope for conversion, we will align on:

– Does the field require cleansing?
• If yes, what cleansing?
• If yes, where will the cleansing take place, who will be the owner and when will it be completed