Customer

See also the page on Customer data governance within the Data Governance directory

Data Object Definition

Customer represents all information related to a business partner of Solvay - a company or an organization - with whom a business relationship exists, involving the exchange of goods and/or services. It contains all the information such as the contact's name, email address, billing information, address, Corporate group and others attributes.

This data is available in the Data Ocean as of Q2 2023.

Data Model 

Customer data in the Data Lake is composed of below views:

1. V_DIM_customer
2. V_DIM_customer_corporate_group

Project Space: prj-data-pricing-dev
See how this entity relates to the others in the pricing data model here.

Additional Info & Comments

• In Salesforce.com, Customers are referred to as Accounts, while SAP mostly uses the word Customer. The two terms can be used as synonyms, but in the Data Ocean we generally prefer the term Customer.
• There are different types of customers. One key distinction is sold-to vs. ship-to customers. The sold-to customer is the entity that is negotiating the price and placing the order (e.g. a corporate headquarters), while the ship-to partner is the one that is physically receiving the goods (e.g. a warehouse or production site). It is possible for customers to be sold-to and ship-to customer at the same time, or for customers to be the sold-to on one order but the ship-to on another.
• Customer group: A Corporate Group allows to create an account hierarchy in Salesforce.com. It groups all the accounts which are part of a same 'legal' entity. The Group is based on the nature of the account, not based on GBU/BU criteria, nor on business rationales. It can be built in the system through a 'Parent account' relationship.
• Customer in Solvay systems is Identified with PRS Code, RCS Code, SAP Code or SF Code.  PRS is the code assigned to an account in PF1 and RCS is the code assigned to an account in WP1. 
• Salesforce code is a code assigned to an account in Icare or Core 
• There is the notion of customer segmentation at group or GBU level (More info here: Customer Segmentation). The corresponding attribute in the material dimension is the customer segmentation at group level. 
• Only the customers related to below source systems will be exposed through view available in Pricing Data Lake
  • PF1_020
  • PI1_020
  • WP1_400
  • NERP001
  • NERP002
  • NERP003
  • NERP004
  • NERP006
  • NERPCYT
  • Sales Force - Core
  • Sales Force - iCare

Data Flow

• Extract Type(Snapshot/Delta): Full data will be extracted from source (SAP-BW & SF-Core) on a daily basis
• Schedule: Jobs will be scheduled to run everyday at 6PM CET 
• Data Mapping Document:

• Data will be processed into DIM_customer through below sources
  • SAP-BW
  • Salesforce-Core
  • Salesforce-iCarr
• If any SOLD-TO/SHIP-TO customers available through sales history query (COPA03) but missing through main SAP-BW customer table, those records will be processed and loaded into DIM_customer through sales history process
• SAP-BW customer record will be enriched with the details available through SF core and iCare records 
• Process will insert missing corporate_group details into DIM_customer_corporate_group table

Data at a Glance

Tables & Attributes

View ID: prj-data-pricing-dev.DataOcean.V_DIM_customer

View ID: prj-data-pricing-dev.DataOcean.V_DIM_customer_corporate_group

View ID: prj-data-pricing-dev.DataOcean.V_DIM_customer_segmentation