v3-data-migration-preparation.pptx
Post on 04-Jun-2018
223 Views
Preview:
TRANSCRIPT
-
8/13/2019 V3-Data-Migration-preparation.pptx
1/16
Data
Migration Preparation
Spirit V3
Customer Master
1
-
8/13/2019 V3-Data-Migration-preparation.pptx
2/16
2
Customer Master Data
Different objects related to customers
General or Global Data
These data are unique for one customer even it exists for several Bacardi entities (like the
Intercompany customers). This is about Name, address, Fiscal and tax Ids, GLN #, Bank
details... For Intercompany customers that are shared between different entities, these
data must be maintained by Global Master Data to avoid mistakes.
Local Data
Sales Data: mainly used to facilitates Order, Shipping, Billing process and reporting. This isabout data that generates pricing, tax, logistic conditions, Payment terms, Inco Term
Company code data: Data mainly used for financial posting (GL account) and Dunning.
Customer Hierarchy
Used for pricing and reporting.
Depicts the organizational structure of a Group Customer.
Customer Material Info records
These records are used to overwrite the Sales Data with new data specific for the
combination product-customer. (exception)
-
8/13/2019 V3-Data-Migration-preparation.pptx
3/16
3
A selling unit in legal terms structured along geographic or other logical sub-divisions
Channel through which saleable materials or services reach customers
Method of grouping products to control product distribution and to monitor profitability of
a product or product group
Sales
Organization
Distribution
Channel
Division
A specific combination of sales organization, distribution channel and divisionSales Area
Customer Master Data
Entreprise Structure
Sales Data
Finance Data
CompanyThe company codeis the organizational unit that allows you to structure your enterprise
from a financial accounting perspective.
-
8/13/2019 V3-Data-Migration-preparation.pptx
4/16
4
Customer Master Data
Data Harmonization
Avoid at the maximum any local exception in term of data maintenance. Use SAP standard at the maximum
V1 and V2 Customer Master fields must be used in V3 with the same purpose. (no local
adaptation)
Any change in the data configuration must be discussed with the Global MDO and Spirit
to evaluate the potential impacts on other organizations and on the common process.
Process Harmonization A Global Master Data Team in charge of enforcing Master Data guidelines, procedures,
policies and Data Standard within all Bacardi Entities.
Maintenance of customer master is local and is performed by different roles. Market
Master Data specialists are responsible to enforce the rules defined by the GlobalMaster Data Organization.
Use of common tools to maintain Master Data (SAP MDM, BPM workflows)
-
8/13/2019 V3-Data-Migration-preparation.pptx
5/16
5
New Master Data Landscape
Customer Master Maintenance Overview
SAP NetWeaver
MDM Syndicator
MDM global Server
Legacy
System
SAP ECC
SAP BW
SAP APO
PEACE
Local SFA
tools
General data
Company &
sales org.
data
Transactional data
& customer Master
Data, customer
hierarchy
FIRE-MDM-210-007
FIRE-MDM-210-008
FIRE-MDM-210-011
Standard interfaceStandard interface
BPM portal
-
8/13/2019 V3-Data-Migration-preparation.pptx
6/16
Data CleansingHarmonization-Enrichment
Identify active customers
We should migrate only active customers Define in your market what is active
Build a rule to determine after how long a customer without any activity is obsolete
(no order, no shipment, no billing)
Identify in the legacy system the obsolete records (use a specific field, a specific
value, so that we can eliminate them from the extract)
In BI, historical data will be stored. It is not necessary to migrate
obsolete records for this purpose.
Identify Duplicate customers
No duplicate customers should be maintained
6
-
8/13/2019 V3-Data-Migration-preparation.pptx
7/16
Data enrichment in legacy system
In Spirit, some data are mandatory in order to migrate thecustomer master successfully
Identify related fields in the legacy system
Ensure that the following data are populated in the legacy
system for each of the customer and are accurate :
Name (max 35 characters)
Postal code (ensure that the format is correct. Ex: 5 digits in France)
City
Country
Payment term
Data CleansingHarmonization-Enrichment
7
-
8/13/2019 V3-Data-Migration-preparation.pptx
8/16
Transformation rules
Some Mandatory fields do not exist in the legacy system, and must bedefined record by record (manual transformation) or can be
determined based on existing field(s) from the legacy sytem(automatic
transformation).
Account group
Distribution channel
Inco Term
Tax classification
Data CleansingHarmonization-Enrichment
8
-
8/13/2019 V3-Data-Migration-preparation.pptx
9/16
Account Groups
A standard SAP manner to group customers according to their type Can be used for reporting purpose
Define which screens and fields are mandatory / optional (when
maintaining the customer record, at the order entry)
Define which partner functions are valid
Define Number range
Data CleansingHarmonization-Enrichment
9
-
8/13/2019 V3-Data-Migration-preparation.pptx
10/16
Account Groups
Third party customers: Sold-to (0001) account group - This type of customer can pass order, receivegoods, receive invoice and pay invoice. (they can be indirect customers (bar,
hotels), Big distribution centers for a chain, outlets.
Ship-to (0002) account group - They can onlybe a good receiving points. They
are not able to pass an order, neither to receive and pay an invoice.
Payer (0003) account group - These customers can, receive the invoice and
pay it. Other functions are performed by other customers (Example:
headquarter of a chain that pay all the invoices)
Bill-to (0004) account groupcan only receive invoices
An account group cannot be changed after a customer is create
We can decide that by default, all Third party custromers are created as Sold to
(Germany / Austria Choice)
Data CleansingHarmonization-Enrichment
10
-
8/13/2019 V3-Data-Migration-preparation.pptx
11/16
Account Groups
Other customers Hierarchy Nodes : They are customers with which we do not have any
transaction. They are maintained to build the customer hierarchy used for
pricing and reporting. How to identify these hierarchy nodes and how to
determine the hierarchy assignments in the legacy system.
Ex: Carrefour France/ Carrefour owned, Affiliates/Provencia,
Logidis/Hyper, Super
Ex: ESD Italy / Esselunga, Selex
IFA Espanola/ Leclerc Spain, Unagras/
Employees:How to isolate the employees in the legacy system?
Data CleansingHarmonization-Enrichment
11
-
8/13/2019 V3-Data-Migration-preparation.pptx
12/16
Inco Term Inco terms are a series of international sales terms and widely used in international
commercial transactions.
We have made this field mandatory in ECC in order to be sure that it is maintained in
case of International transactions
For Domestic customers, each entity must select an inco term, even if it is a dummy one
Values: EXWEx Works (named place)
FCAFree Carrier (named places)
FASFree Alongside Ship (named loading port)
FOBFree on Board(named loading port)
CFR or CNFCost and Freight (named destination port
CIFCost, Insurance and Freight (named destination port)
CPTCarriage Paid To (named place of destination)
CIPCarriage and Insurance Paid (To) (named place of destination)
DAFDelivered At Frontier (named place)
DESDelivered Ex Ship (named port)
DEQDelivered Ex Quay (named port)
DDUDelivered Duty Unpaid (named destination place)
DDPDelivered Duty Paid (named destination place)
Data CleansingHarmonization-Enrichment
12
-
8/13/2019 V3-Data-Migration-preparation.pptx
13/16
Inco-term
For a given term, "Yes"indicates that the sellerhas the responsibility to
provide the service included in the price. "No"indicates it is the buyer's
responsibility.
Data CleansingHarmonization-Enrichment
13
-
8/13/2019 V3-Data-Migration-preparation.pptx
14/16
Distribution channel Channel through which salable materials or services reach customers.
Defined for Spirit: Travel retail, Export, Domestic, Intercompany.
Each customers must be created under one Distribution channel
Customer Classifications Fields used (3 fields mandatory)to describe the customer activity. The definitions must be consumer driven and
orientated
As an industry we need to think demand chains not supply chains
Objectives:
To have a unique approach and definitionsEvery user will understand the concepts in a common way
To facilitate reporting exercises
The system will have a common structure to be maintained and reported on
To make a consistent structure to compare
The numbers across markets will have the same meaning
To satisfy all classification requirements
Covering all the complexities of the business from origin to consumer
All Customers (sold to) musthave a customer classification.
Consumption cluster
Consumer Activity
Sales channel
These classifications can be combined with hierarchies and other customer master fields to produce a customizedreport
Data CleansingHarmonization-Enrichment
14
-
8/13/2019 V3-Data-Migration-preparation.pptx
15/16
Customer Hierarchy
Customer hierarchy represents the structure of customers with a complex organization. Thesecustomers are identified as groups. They may have different levels of organization, for examplea global headquarter, a regional one, a local one
A customer hierarchy is a flexible structure consisting of customer records (with the exceptionof the uppermost record) that refer to another record.
The records in the hierarchy, can be normal customers (they can pass orders, receive goodsand be billed) or nodes. A node is a specific customer type that represents an organizationallevel, with which we may not have any transaction (order, shipping, billing, payment). Thisnode is used for reporting purpose or aggregation of a group of customers.
We want to use customer hierarchy to determine :
the way we perceive our customersorganization, respecting customers realorganization how we want to measure the business we make with them
The link of the customers to Customer hierarchy must be dynamic and flexible in order tofollow the customer structure. But due to the impact of a customer hierarchy change, it has tobe anticipated (to reflect the month end situation) and well prepared.
Data CleansingHarmonization-Enrichment
15
-
8/13/2019 V3-Data-Migration-preparation.pptx
16/16
Customer Hierarchy
Define the hierarchy nodes (see page 7) according to the real structure of the
customer and according to the pricing need (for example, define a discount
that will apply to the customers under a node) and according to the reporting
need (for example, determine the volume sold to a specific banner within a
group)
Build the hierarchy, assign the nodes one to the others.
Data CleansingHarmonization-Enrichment
16
top related