Data Object Definition

The Customer-Product Combination dataset contains data on all combinations of customer & product which appear in transactional data. For these combinations, it stores attributes which are derived from multiple sources. It serves as a central source of derived master data for enrichment in various other datasets. 

Deployment Status


This data is available in the Data Ocean as of Q1 2024.


Data Model 

CPC data in the Data Lake is composed of below tables/views:

  1. V_DIM_cpc_master  - This table/view includes the one record per the combination of customer(Ship-To/Sold-To), product/material and GBU and the key attributes associated to this combination. This combination is referred as CPC
  2. V_DIM_cpic_master - This table/view includes the one record per the combination of customer(Ship-To/Sold-To), product/material, GBU and incoterm and the key attributes associated to this combination. This combination is referred as CPiC. CPiC is at the high level and a one CPiC can be associated to multiple CPC records

Project Space: gcp-sqo-data-pricing-d
See how this entity relates to the others in the pricing data model here.


Additional Info & Comments

  • The exact definition of customer-product combination can be different between different GBUs:
    • For Specialty Polymers (SP), the customer is specified at the soldto level, and products are specified at the commercial product level (so valid across all different packaging types of the same chemistry).
    • For Composite Materials(CM), the customer is managed at individual slodto level and products are specified including the material packaging format.
    • For Novecare(CS), Aroma Performance (PA), Oil & Gas (OG) & Technology Solutions (TS) the customer is managed at individual shipto level and products are specified including the material packaging format. Along with Customer and material, it will also include incoterm to make the combination unique
  • The customer-product dataset should specify for each CPC at least the following fields:
    • GBU
    • GBU Customer Segment
    • End Use
    • Market Cluster
    • Product Hierarchy (inc. H4)
    • Latest shipping plant & manufacturing plant
    • Latest Incoterm
    • Last Payment Term
    • Final Consignee
    • Latest orderline ID
    • Last Invoice Price
    • Stock Holding Strategy
    • Distribution Channel
  • The  CPiC (Including incoterms) dataset should specify for each CPiC at least the following fields:
    • All the fields from CPC
    • Distribution Channel
    • Latest shipping plant & manufacturing plant
    • Latest orderline ID
    • Last Invoice Price

Data Flow


  • cpc_master table will be built by Extract Type(Snapshot/Delta/Transactional): Transactional data extracted through COPA03 and COCP07 queries (Refer Sales History and Sales Forecast tab for more details )
  • Data Refresh Frequency: Jobs will be scheduled to run everyday at 8AM CET 
  • Data Mapping Document:
  • Schedule and Dependent job details:




Tables & Attributes

View ID: gcp-sqo-data-pricing-d.DataOcean.V_DIM_cpc_master

View ID: gcp-sqo-data-pricing-d.DataOcean.V_DIM_cpic_master