Data Migration Preparation

Spirit V3 Customer Master

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 is about 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)

Customer Master Data Entreprise Structure Sales Data

Sales Organization
Distribution Channel
A selling unit in legal terms structured along geographic or other logical sub-divisions

Channel through which saleable materials or services reach customers

Division

Method of grouping products to control product distribution and to monitor profitability of a product or product group

Sales Area

A specific combination of sales organization, distribution channel and division

Finance Data
Company
The company code is the organizational unit that allows you to structure your enterprise from a financial accounting perspective.
3

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 Global Master Data Organization. Use of common tools to maintain Master Data (SAP MDM, BPM workflows)

Customer Master Maintenance Overview

New Master Data Landscape
Transactional data & customer Master Data, customer hierarchy

SAP APO SAP BW Standard interface Standard interface

PEACE System

Legacy

FIRE-MDM-210-007

SAP ECC

FIRE-MDM-210-008 FIRE-MDM-210-011

Company & sales org. data General data

SAP NetWeaver MDM Syndicator MDM global Server

Local SFA tools

BPM portal

Data Cleansing Harmonization-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

Data Cleansing Harmonization-Enrichment Data enrichment in legacy system

In Spirit, some data are mandatory in order to migrate the customer 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 Cleansing Harmonization-Enrichment Transformation rules

Some Mandatory fields do not exist in the legacy system, and must be defined 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 Cleansing Harmonization-Enrichment 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 Cleansing Harmonization-Enrichment Account Groups

Third party customers:
Sold-to (0001) account group - This type of customer can pass order, receive goods, 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 only be 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 group can 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)

10

Data Cleansing Harmonization-Enrichment 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?

11

Data Cleansing Harmonization-Enrichment 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:
EXW Ex Works (named place) FCA Free Carrier (named places) FAS Free Alongside Ship (named loading port) FOB Free on Board(named loading port) CFR or CNF Cost and Freight (named destination port CIF Cost, Insurance and Freight (named destination port) CPT Carriage Paid To (named place of destination) CIP Carriage and Insurance Paid (To) (named place of destination) DAF Delivered At Frontier (named place) DES Delivered Ex Ship (named port) DEQ Delivered Ex Quay (named port) DDU Delivered Duty Unpaid (named destination place) DDP Delivered Duty Paid (named destination place)

12

Data Cleansing Harmonization-Enrichment Inco-term

For a given term, "Yes" indicates that the seller has the responsibility to provide the service included in the price. "No" indicates it is the buyer's responsibility.

13

Data Cleansing Harmonization-Enrichment

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 definitions Every 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) must have a customer classification. Consumption cluster Consumer Activity Sales channel These classifications can be combined with hierarchies and other customer master fields to produce a customized report

14

Data Cleansing Harmonization-Enrichment Customer Hierarchy

Customer hierarchy represents the structure of customers with a complex organization. These customers are identified as groups. They may have different levels of organization, for example a global headquarter, a regional one, a local one A customer hierarchy is a flexible structure consisting of customer records (with the exception of the uppermost record) that refer to another record. The records in the hierarchy, can be normal customers (they can pass orders, receive goods and be billed) or nodes. A node is a specific customer type that represents an organizational level, with which we may not have any transaction (order, shipping, billing, payment). This node 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 real organization 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 to follow the customer structure. But due to the impact of a customer hierarchy change, it has to be anticipated (to reflect the month end situation) and well prepared.
15

Data Cleansing Harmonization-Enrichment

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.

16