The Journey To World-Class: Introduction To SAP Master Data

The Journey to World-Class
Introduction to SAP Master Data

Presented to:
EzLifeSciencesTM
An SAP All-In-One Business Solution
Date
Agenda
 Master Data Overview & Scope

 Master Data Levels and Elements
 Data Migration
 Lessons Learned
 Next Steps
Page 2
Client Name - Introduction to SAP Master Data
© 2020 The Hackett Group. All rights reserved. Reproduction of this document or any portion thereof without prior written consent is prohibited.
Master Data Overview & Scope
Introduction
 Master data is the central information source for your company. All SAP components access this data. By integrating
master data in central database objects, you can avoid data redundancy. SAP components use data from the
individual master data records for most transactions.
 Critical Master data elements in SAP:

– Material Master
– Customer Master
– Vendor Master
– G/L Account
– BOM/Routing
Page 3
SAP Data Hierarchy
 Configuration Data
– Company Code, Plant, Sales Organization etc.
Configuration Data
 Master Data
– Material Master, Customer Master, Vendor Master, G/L Account etc. Master Data
yit
ual
ta Q
 Transaction Data
Da
– Purchase Order, Production Order, Sales Order etc. Transaction Data
Page 4
Structure of Master Data
 Master data within SAP is structured using Views

– Examples:
 Repligen View
 Company Code View
 Plant View
 Address view
 Others
 Depending on business requirements, different views are required so the system functionality can work
 Responsibility for data in the views can be divided up to different individuals.
 Master data exists once and only once (e.g. material unique by form, fit, function)
Page 5
Integration of Master Data
Purchasing/ Sales/
Accounting Accounting
Vendor Master Customer Master
Material
Master
Bill of Material Info Record
Purchasing/ Purchasing/
Subcontracting Accounting
Page 6
Master Data to be Converted
Financial
Accounting Controlling Sales
Chart of Accounts Cost Centers Customer Masters

Banks Cost Center Groups Pricing conditions
Cost Elements
Cost Element Groups
Profit Centers
Activity types
Statistical Key Figures
Materials &
Production Other
Purchasing
Production Versions Quality Views (QM)
Material Masters
Bills of Material Personnel Data (HR)
Vendor Masters
Purchase Info Records Work Centers
Source Lists Routings
Characteristics
Classes
Page 7
Transactional Data to be Converted
Financial
Accounting Controlling Sales
GL Account Balances Activity Labor Allocations Open Sales Orders

Payables outstanding Overhead Application
Receivables outstanding Departmental Balances
Chart Of Accounts (COA) Profit Center P&L
Materials &
Production Other
Purchasing
Inventory (RM, Semi, Finished Open Production Orders Open Batch Status
Goods)
Batches and Serialization data
Open Purchase Orders
Page 8
Master Data Levels and Elements
Materials
 Purpose
– The Material Master contains information on all the materials that a company procures or produces, stores, and sells. It is the
company's central source for retrieving material-specific data. This information is stored in individual Material Master records.
 Integration
– The Material Master is used by all components in the SAP Logistics System. The integration of all material data in a single
database object eliminates redundant data storage. In the SAP Logistics System, the data contained in the Material Master is
required, for example, for the following functions:
 In Purchasing, for ordering
 In Inventory Management, for goods movement postings and physical inventory
 In Invoice Verification, for posting invoices
 In Sales and Distribution, for sales order processing
 In Production Planning & Control, for material requirements planning, scheduling, & work scheduling
 We will set the Material Master to suit your specific requirements.
Page 9
Material Master Data Levels & Elements
• Material description, number & type

Repligen Base unit of measure
RepligenLevel
LevelData
•
Data • Material group
• Product group
• Material hierarchy
Company
CompanyLevel
LevelData
Data • Financial balances
• Storage & basic shipping data
• MRP and scheduling information
Plant
PlantLevel
LevelData
Data • Quality and batch management
• Profit center
• Purchasing group
Purchasing
PurchasingLevel
LevelData
Data • Procurement data
• Product costing
Valuation
ValuationLevel
LevelData
Data • Accounting rules
• Storage requirements
Storage
StorageLocation
LocationLevel
LevelData
Data
• Physical quantities
• Storage unit of measure
• Selling & delivery information

Sales
SalesOrg.
Org.Level
LevelData
Data • Sales product grouping, hierarchy, & attributes
Page 10
Material Master Record Views
A
Integration
Material Master record for an industry contains the following subject areas:
– Accounting
Since different departments in a company work with the same material, but each department uses different information on the material, the
– Basic
data inData
a Material Master record is subdivided by user department.
– Classification
– Costing
– Forecasting
– Materials Planning
– Production Resources and Tools
– Purchasing
– Quality Management
– Sales and Distribution
– Plant/Storage Location Stock
– Storage
– Warehouse Management
– Work Scheduling
Page 11
Introducing ‘Business Partners’ in S/4 HANA
 There are redundant object models in the traditional ERP system, typically the vendor master and customer master is
used.
 The (mandatory) target approach in S/4HANA is the Business Partner approach.
 A Business Partner is now capable of centrally managing master data for business partners, customers, and
vendors. With current development, BP is the single point of entry to create, edit, and display master data for
business partners, customers, and vendors
Page 12
Introducing ‘Business Partners’ in S/4 HANA
 Customer/Vendor Object Model Limitations

– Only one single address
– No relation between a vendor and a customer for the same real world entity (no role concept)
– No time-dependency
 Business Partner – SAP Strategic Object Model

– General data are shared across different roles
– One business partner could perform multiple roles, e.g., customer and vendor (supplier)
– One business partner could have multiple addresses
– Time-dependency object attributes and relationships
– Provide harmonized architecture
– Customer/Vendor Integration (CVI) component ensure the synchronization between the Business Partner object and the customer/vendor
objects
Page 13
Business Partner - Customers
 Purpose
– In the SAP System, all business transactions are posted to and managed in accounts. You must create a master record for
each account that you require. The master record contains data that controls how business transactions are recorded and
processed by the system. It also includes all the information about a customer that you need to be able to conduct business
with him.
 Integration
– Specifications you make in Customer master records are used:
 As default values when you create sales transactions. For example, the terms of payment, delivery priority, partner functions, incoterms
you specify in the master record are defaulted in the sales transactions.
 For working with master records. You can prevent certain users from accessing an account by setting up authorization groups.
Page 14
Business Partner - Customer Master Data Levels & Elements
• Address
• Tax
Repligen
RepligenLevel
LevelData
Data • Classification
• Operating figures
• Unloading points
• Account management
Company 001 • Payment transaction data
Company 002 • Dunning
• Correspondence
Company
CompanyLevel
LevelData
Data
Balances
Balances
Sales Org 001 • Ordering data

Sales Org 002 • Pricing data
• Shipping
Sales
SalesOrg
OrgLevel
LevelData
Data • Billing
• Delivery & payment terms
Credit control area 001 • Partner functions (ship to, bill to etc)
Credit control area 002
Credit • Credit limits
CreditControl
ControlArea
Area • Credit checking rules
Level Data
Level Data • Payment history
Page 15
Business Partner - Vendors
 Purpose
– Business transactions are posted to accounts and managed using those accounts. You must create a master record for each
account that you require. The master record controls how business transactions are recorded and processed by the system.
 Integration
– Specifications you make in master records are used:
 As default values when you post items to the account. For example, the terms of payment you specify in the master record are defaulted
for document entry.
 For processing business transactions For instance, bank details and the payment methods (check or bank transfer, for example) are
required for automatic payments.
 For working with master records. You can prevent certain users from accessing an account by setting up authorization groups.
 In addition, line item display and open item management are defined automatically for each vendor account.
Page 16
Business Partner - Vendor Master Data Levels & Elements
• Address
• Tax
Repligen
RepligenLevel
LevelData
Data • Bank details
Company 001 • Account management

Company 002
• Payment transactions
• Dunning data
Company
CompanyLevel
LevelData
Data • Correspondence details
Balances
Balances
Purch Org 001

Purch Org 002
• Conditions
Purch.
Purch.Org.
Org.Level
LevelData
Data • Control data
Info.
Info.Records
Records
• Material specific data
• Pricing conditions
Page 17
General Ledger
• Account Number
Chart
ChartofofAccounts
Accounts • Account Group
• Description
• Currency
Company 0001 • Tax Category
Company 0002 • Field Status
• Sort sequence
COMPANY LEVEL DATA • Automated/manual posting
• Line item display
Balances
Balances
Page 18
Cost Centers
Cost
CostCenters
Centers • Name & Description
• Person Responsible
• Cost Center Category
• Std Hierarchy Area
Basic
BasicData
DataTab
Tab • Company Code(s)
• Functional Area
• Currency
• Profit Center Assignment
• Lock/Unlock for:
• Actual/Plan Primary Postings
Control
ControlTab
Tab • Actual/Plan Secondary Postings
• Actual/Plan Revenues
• Commitments
Address
AddressInformation
Information • Optional
Page 19
Bank Accounts
• Bank Country
House
HouseBank
BankMaster
MasterData
Data • Bank Key
• House Bank
• Account ID
Bank
• Bank Account
BankAccount
AccountMaster
MasterData
Data • Text
• GL Number
• Currency
• Swift Code
Cash Receipts
Cash Disbursements
Other Cash Entries
Ending
EndingBalance
Balance
Page 20
Agenda

 Data Migration
 Lessons Learned
 Next Steps
Page 21
Data Migration
Why is Master Data important?
 Business data will drive your SAP S/4HANA business processes

 Successful implementations depend on business data which is:
– Accurate
– Relevant
– Timely
 Poor business data can result in:
– Inaccurate financial reporting
– Uncollected receivables
– Overpayments
– Poor product specifications
– Excess inventory
– Project delays and cost overruns
 Garbage In, Garbage Out (GIG0) avoidance!
Page 22
Data Migration
Potential Risks
Risk P I
Data Quality is poor (Erroneous, Duplicates, Inconsistent use of fields) which
leads to large manual migration effort  
Different structure of data in SAP and legacy systems; e.g. various levels of
master data in SAP (Repligen, company code, plant etc.) lead to difficulty or  
misunderstanding on how to create the data extracts
Multiple source systems requires merging of data, which causes huge
adaptation effort in the Data Migration programs or manual intervention  
Underestimating the effort of Data Migration activities  
Migration of historical data required, which causes huge adaptation effort in the
Data Migration programs  
Lack of data migration skills at the customer resulting in inability to extract data  
Same resources used for project & data migration, meaning insufficient time to
complete either role  
P = Probability I = Impact  High  Medium  Low
Page 23
Data Migration
The Entire Data Migration Process
1 Extract Data 2 Map data 3 Clean data 4 Load data 5 Reconcile data
 Data requirements and cleansing plan are critical for this process. Production Data may require a faster upload
process than that for Sample Data. Therefore we suggest using SAP tools such as LSMW within this data migration
model:
– Extract- Where do you need to get the data from in your current systems?
– Transform- How does your legacy data need to be transformed to map to SAP?
– Load- Load of the data using tools such as LSMW, load routines or manual data loads.
– Individual activities are defined in the pre-project activities phase. Key milestones are:
 Data Definition
 Data Mapping
 Data Extraction
 Data Cleansing
 Test Loads
 Live Loads
 These activities take place at scheduled times throughout the Implementation Cycle with a weekly review of progress
against the plan.
Page 24
Data Migration
Standard Conversion Procedure
 The conversion procedure is composed of four main steps:

1. Extract data
 The data that is to act as the basis for the conversion of each entity will either be created manually or by extracting data from existing
systems files/databases. The results of this step will either be an extract file or a file/database containing the data in its initial form.
 The extract of historical data from existing systems and its conversion to new systems can be a sizeable effort. Converting historical data
should be avoided, unless there is strong business or legal requirements to do so.
2. Purify / Clean data

 The purification step will validate the integrity of the source data and correct it where necessary. This will include:
– Data consolidation across Legacy instances
– Validation of the format of each field. For example, that a numeric field only contains numeric characters.
– Validation of foreign keys.
Page 25
Data Migration
Standard Conversion Procedure (continued)
3. Map data
 The enrichment step will take the source data and add any attributes that are required in SAP but could not be extracted from the source
system. It will also cover the creation of other data related entities.
 It is conceived that the enrichment and purification steps will occur concurrently and that a number of iterations will be required to produce
a complete, error free set of data for loading into SAP.
4. Load data
 The upload step will take the complete set of data as produced by the purification and enrichment process and load it into SAP.
We will make a determination between manual and automatic entry. The decision depends on certain factors such as availability of
data in magnetic format, complexity and volume.
For Repligen, some master data and open balances will be entered manually due to their low volume.
Page 26
Data Migration
Standard Conversion Procedure (continued)
 Purifying/Cleaning Data – Repligen must:
1. Purge data
 Before transferring data from any of these, Data owners must get rid of all old and obsolete data. This will save space and processing
time.
– Example: get rid of all inactive customers or vendors and delete all materials that are not being used. This is an analysis that each
data owner needs to carry out.
2. Clean data
 Cleansing refers to cleaning up the data that is in the database. Cleansing the database is done to ensure the accuracy of the existing
data. If some mistakes were made and the data is not correct, it should be corrected before the transfer.
– Example: materials might have been classified only for reporting subtotal purposes and the wrong classification did not show up in
the result. In the tightly integrated SAP system the wrong material type (the major determination for a material), could result in wrong
account postings, valuation calculation and screen display.
– Data cleansing is necessary to ensure data consistency and data accuracy.
Page 27
Data Migration
Data Cleansing Considerations
 Write-off bad debts or give to collection agency or …

 Start calling in all days and days A/R
 Settle outstanding customer’s claims
 Identify, archive inactive Customers, Vendors, Materials and BOMs
 Eliminate duplicate records by postal codes, telephone, product description, etc…
 Identify and correct missing data elements
 Correct data for consistency and clarity
 Adopt Nomenclature conventions for each Data Set (e.g. internal/external No. Range, Descriptions)
 Perform physical inventory; eliminate idle or obsolete inventory and corresponding material master records
 Extract transaction history to data warehouse
Accurate Business Data requires Business ownership, it is not IT’s responsibility

Page 28
Data Migration
When is Data Required?
Playbacks
1 2 3
Config &
ABAP
Converted data not required Converted data not required Converted data not required but
• PB data will be created! • PB data will be created preferred
• Can leverage converted • PB data can be created
data if clean • Will leverage converted data
Data Should be delivering on Should be delivering on targets Integration

targets • Materials: ~ 70 – 80 % Test
• Materials: Top 200 • Vendors: ~ 70 – 80 %
• Vendors: Top 200 • Customers: ~ 70 – 80 % Converted data required for master
Should set key targets • Customers: Top 200 data
master data for: Need to be addressing transactional
• Materials Approach and process data by this point if not already doing Should be delivering on targets
• Vendors should be well defined so. • Materials: ~ 80 – 90 %
• Customers and working at this point • Vendors: ~ 80 – 90 %
• Customers: ~ 80 – 90 %
Security Roles & Responsibilities

Security required
BASIS
Page 29
Data Migration
Process for Data Migration - Sample
File formats are:
• Provided by Answerthink
• Based on SAP Input Structure
Mapping is executed at 2 Levels

• Technical – understanding fields to extract
• Functional – understanding business requirements, rules, field definition &
meaning
(Ecometry, GoldMine, Data Mart, etc.)
Repligen Legacy Systems
.XLS
SAP S/4HANA
• LSMW
AIO Name MAT_NUM PLANT PROD_VERSN PROFI LE VALID_FR STATUS USAGE BASE_QTY BASE_UOM OLD_MAT_REF
Technical Product ion Base Unit of Old Material
Legacy
Field Name -> Material Plant version Profile Valid from St atus Usage Quant it y Measure ref erence
RC271-
SAP Field RC27M- PROFI DNE RC271- PLKOD- PLKOD- PLKOD- PLKOD-
Map Review
Name -> MATNR PLKOD-WERKS RC27M-VERID TZ STTAG STATU VERWE BMSCH MEI NH RC27M-MATNR
• Input Program
Data Type -> CHAR(18) CHAR(4) CHAR(4) CHAR(7) DATS(8) CHAR(3) CHAR(3) QUAN(13) UNI T(3) CHAR(18)
Field Type
Data Preparation
M - Mandat ory
Sequential
D - Def ault AI O Name MAT_NUM PLANT PROD_VERSN PROFI LE VALID_FR STATUS USAGE BASE_QTY BASE_UOM OLD_MAT_REF
O - Optional M M M M M M M M M O
Default Value -> B P01 Product ion Base Unit of Old Mat erial
Manual
Field Name ->BP01
PH-6601 Mat erial Plant1 version
PI01 Profile 4 Valid from1 St at us 2500
20061205 Usage EAQuantity Measure reference
Functional •
PH-6601 BP01 2 PI01 RC271- 4
20061205 1 1 EA
SAP Field BP01
PH-6501 RC27M- 1 PI01 PROFI DNE
20061207 4 RC271- 1 PLKOD- 1000 PLKOD- EAPLKOD- PLK OD-
Name -> MATNR PLKOD-WERKS RC27M-VERI D TZ STTAG STATU VERWE BMSCH MEINH RC27M-MATNR
Program / Extract File

Dat a Type -> CHAR(18) CHAR(4) CHAR(4) CHAR(7) DATS(8) CHAR(3) CHAR(3) QUAN(13) UNIT(3) CHAR(18)
Field Type
Mapping
M - Mandatory
• Other
D - Default
AI O Name MAT_NUM PLANT PROD_VERS N PROFI LE VALI D_FR STATUS USAGE BASE_QTY BASE_UOM OLD_MAT_REF
O - Opt ional M M M M M M M M M O
Def ault Value -> BP01
Production Base Unit of Old Mat erial
PH-6601 BP01 1 PI01 20061205 4 1 2500 EA
Field Name -> Mat erial Plant version Prof ile Valid from St atus Usage Quant it y Measure reference
PH-6601 BP01 2 PI01 20061205 4 1 1 EA
RC271-
PH-6501 BP01 1 PI01 20061207 4 1 1000 EA
SAP Field RC27M- PROFI DNE RC271- PLKOD- PLKOD- PLKOD- PLKOD-
Name -> MATNR PLKOD-WERKS RC27M-VERI D TZ STTAG STATU VERWE BMSCH MEI NH RC27M-MATNR
Dat a Type -> CHAR(18) CHAR(4) CHAR(4) CHAR(7) DATS (8) CHAR(3) CHAR(3) QUAN(13) UNI T(3) CHAR(18)
Field Type
M - Mandat ory
D - Default
O - Opt ional M M M M M M M M M O
Def ault Value -> BP01
PH-6601 BP01 1 PI01 20061205 4 1 2500 EA
PH-6601 BP01 2 PI01 20061205 4 1 1 EA
PH-6501 BP01 1 PI01 20061207 4 1 1000 EA
• Remove duplicates • Prioritize Data Cleansing

• Remove obsoletes • PB2
• Identify gaps • Top 200 Materials
• Perform a quality check on the • Top 200 Customers
general data accuracy • Top 200 Vendors
• Naming conventions • PB3
• Abbreviations Note: Data cleansing to be completed
• Missing fields by
• Monitor data extraction progress close of PB 3
Step 1: Extraction / Formatting / Technical Mapping Step 2: Functional Mapping / Cleansing Step 3: Load & Verify
Extraction / Formatting - Repligen Functional Mapping – Repligen / ANSR Load – Repligen / ANSR
Technical Mapping – Repligen / ANSR Cleansing - Repligen Verify - Repligen
Page 30
Data Migration
Master Data Conversion Template Example – BOM’s
MAT_NUM_TOP PLANT ITEM_NUM COMP_MAT COMP_QTY COMP_UOM COMP_ITM_CAT COMP_SORT_STR COMP_SCRP_PCT COMP_OFFSET COMP_NOTE COMP_RSLT_ITM_CAT COMP_CLS_TYPE COMP_CLS_NAME
AIO Name
Component
BOM Material Plant Item Number Component qty Component UOM Item Category Sort string Scrap percent Offset Note Resulting Item Category Class type Class Name
Material
Field Name ->
RC29P-
RC29K-MATNR RC29K-WERKS RC29P-IDNRK RC29P-MENGE RC29P-MEINS RC29P-POSTP RC29P-SORTF RC29P-AUSCH RC29P-NLFZT RC29P-POTX1 RC29P-POTPR RC29P-KLART RC29P-CLASS
SAP Field Name -> POSNR
Data Type -> CHAR(18) CHAR(4) CHAR(4) CHAR(18) QUAN(13) UNIT(3) CHAR(1) CHAR(10) DEC(5) DEC(3) CHAR(40) CHAR(1) CHAR(3) CHAR(18)
Field Type
M - Mandatory M M M M M M M O O O O O O O
D - Default
O - Optional
Default Value -> BP01
MD-6601 BP01 10 MD-6600 1 EA L
MD-6600 BP01 10 MD-4300 1 EA L
MD-6600 BP01 20 MD-4500 1 EA L
MD-6600 BP01 30 MD-4801 1 EA L
MD-6600 BP01 40 MD-4920 1 EA L
MD-6600 BP01 50 MD-4930 1 EA L
PH-6601 BP01 10 PH-2800 50 KG L
PH-6601 BP01 20 PH-4300 1 EA L
PH-6601 BP01 30 PH-4920 1 EA L
PH-6601 BP01 40 PH-4930 1 EA L
PH-6601 BP01 50 PH-4801 1 EA L
PH-6601 BP01 60 PH-1820 100 KG L
PH-6601 BP01 70 PH-4400 1 EA L
PH-6501 BP01 10 PH-2800 1 KG L
PH-6501 BP01 20 PH-4300 1 EA L
PH-6501 BP01 30 PH-4920 1 EA L
PH-6501 BP01 40 PH-4930 1 EA L
PH-6501 BP01 50 PH-4400 1 EA L

Page 31
Data Migration
Roles and Responsibilities
 In general the Roles & Responsibilities of Data Migration are divided between Repligen and Answerthink, however,
the majority resides with Repligen
– Repligen
 Data cleansing, extraction, data mapping, testing of data loads, live data loads, produce data migration plan and agree any additional consultant resources
required for training and support (by functional area)
– Answerthink
 Provide agreed training and support
– Assist with functional data mapping
– Technical use of data templates and LSMW’s
 At the conclusion of BP, a weekly activity schedule needs to be produced with a week by week breakdown of the
customer and the consultant tasks
– This should be led by and managed jointly by the Repligen Data Czar and Answerthink Technical Lead
Page 32
Data Migration
Roles and Responsibilities (Key Roles)
 Answerthink recommends that Repligen review its current Data Policy and Procedures and modify as needed to
support pre-deployment, stabilization, and post deployment and strives for accurate and reliable information.
 Key roles in the Data Migration process are:
– Data Czar
 Central Oversight and Analysis
 Data metrics
 Overall Data Validation and Maintenance
– SAP Team Leads
 Accountable for system configuration and data integrity
 Ensure data objects support the business processes
 Legacy data cleansing and validation
– Repligen Team Leads
 Functional business oversight
 Issue resolution management
– Repligen Subject Matter Experts
 Responsible for data content
Page 33
Agenda

 Data Migration
 Lessons Learned
 Next Steps
Page 34
Lessons Learned
Summary Lessons Learned
 Data Quality is essential. Look for opportunities to eliminate:

– Erroneous
– Duplicates
– Inconsistent
– Obsolete
 If data resides in multiple source systems, merging of data required
 Different data structure between SAP and legacy systems may require data transformation and enhancement
 Skills
– Requires both IT and business leads.
 Time/Resources
– Many underestimate the current situation and what it requires to extract, cleanse and convert.
 Clearly articulate strategy for historical data
Page 35
Lessons Learned
General
 Data Quality is essential - Look for opportunities to eliminate:

– Erroneous Data
– Duplicates
– Inconsistent Data
– Obsolete Data
 If data resides in multiple source systems, merging of data is required and necessary
 Different data structures between SAP and the legacy systems may require data transformation and enhancement in
order to map the data sets
 Skills
– Requires both IT and business Team members
 Time/Resources
– Many underestimate the current situation and what it requires to extract, cleanse and convert.
 Develop strategy for historical data
Page 36
Lessons Learned
Where to Begin
 Inventory your current data sets:  Develop Data Cleansing Rules

– Identify what exists and what does not  Identify the Adopted convention
– Identify data sources – Internal or External number range
 Legacy ERP systems – Nomenclature
 3rd party systems (CRM, PLM, etc.)
 Spreadsheets / databases
 Notebooks
 Human knowledge
 other
 Initiate Data Cleansing … The sooner, the better,
 Identify data Volume Estimates
Lets get started, now
 Identify Type of Conversion (Manual/Automated)
 Assign Business Owner Responsibility
Page 37
Agenda

 Data Migration
 Lessons Learned
 Next Steps
Page 38
Next Steps
Last Considerations
 Data Maintenance (When to do)

– During cleanup
– During Transformation
 After Extract from legacy and before Go-live
– After Go-live
 New processes and new controls now in place, to avoid future problems
 Who “Owns” data, especially cross functional data (Need to discuss)

– Multiple organizational elements (e,g. Materials, Vendors, Customers)
– Multiple legacy systems/sources
 Data “Czar” needed?
– Drives and Tracks effort: extracts, mapping to SAP, number of records, cleansing, loads, sequence
 Data, Data, Data…This will be covered again and again and again…
Page 39
Contact Information
Answerthink Associate Name
1001 Brickell Bay Drive Michael Greene
Miami, Florida Principal
Phone: 732 727-6944 mgreene@answerthink.com
570.466.5155
www.answerthink.com
Page 40

The Journey To World-Class: Introduction To SAP Master Data

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Journey To World-Class: Introduction To SAP Master Data

Uploaded by

Copyright:

Available Formats

The Journey to World-Class

Introduction to SAP Master Data

 Master Data Overview & Scope

 Critical Master data elements in SAP:

 Master data within SAP is structured using Views

Vendor Master Customer Master

Bill of Material Info Record

Chart of Accounts Cost Centers Customer Masters

GL Account Balances Activity Labor Allocations Open Sales Orders

• Material description, number & type

• Selling & delivery information

 Customer/Vendor Object Model Limitations

 Business Partner – SAP Strategic Object Model

Sales Org 001 • Ordering data

Company 001 • Account management

Purch Org 001

 Master Data Overview & Scope

 Business data will drive your SAP S/4HANA business processes

P = Probability I = Impact  High  Medium  Low

 The conversion procedure is composed of four main steps:

2. Purify / Clean data

 Purifying/Cleaning Data – Repligen must:

 Write-off bad debts or give to collection agency or …

Accurate Business Data requires Business ownership, it is not IT’s responsibility

Data Should be delivering on Should be delivering on targets Integration

Security Roles & Responsibilities

Mapping is executed at 2 Levels

Technical Product ion Base Unit of Old Material

Program / Extract File

• Remove duplicates • Prioritize Data Cleansing

 Master Data Overview & Scope

 Data Quality is essential. Look for opportunities to eliminate:

 Data Quality is essential - Look for opportunities to eliminate:

 Inventory your current data sets:  Develop Data Cleansing Rules

 Master Data Overview & Scope

 Data Maintenance (When to do)

 Who “Owns” data, especially cross functional data (Need to discuss)

You might also like