a) Received from Carlos for Novecare price optimization tool
| Customer | Sold-To revenue (EUR) excl. CPC | Yes | BW P&L or Order Query | High | N/A |
| Customer | Customer Segment | Yes | BW P&L or Order Query OR Salesforce Customer Data | High | GBU Customer Segment |
| Customer | Customer centralization? | No | TBC | Low | |
| Customer | Sold-To Group revenue (EUR) excl. Sold-To | Yes | BW P&L or Order Query | Medium | |
| Customer | Enterprise segment | Yes | Not in initial scope | Enterprise segment |
b) Received by Leo (May 11)
Historical
| Month | Incoterms | Source System | Material Code | Ship-To Code | Group of Activity | Country (Ship-To) | Country (Sold-To) | GBU Region | End Use | GBU Product Family | Enterprise Segment | Market | GBU Customer Segment | Group Customer Segment | Product Name | Product Code | Product Brand Name | Sales (€) | Unit Price (€/KG) | Volumes (KG) | Last Invoice Price (€/KG) |
Forecast
| GBU | Month | Incoterms | Source System | Material Name | Material Code | Ship-To Name | Ship-To Code | Sold-To Name | Sold-To Code | Sold-To Group | Shipping Plant | Manufacturing Plant | Group of Activity | Country (Ship-To) | Country (Sold-To) | GBU Region | End Use | GBU Product Family | Enterprise Segment | Market | GBU Customer Segment | Group Customer Segment | Product Name | Product Code | Product Brand Name | Fcst Sales [Est Act] (€) | Fcst Volume [Est Act] (KG) | Fcst Unit Price [Est Act] (€/KG) | Last Invoice Price (€/KG) |
| BW P&L ICM/Sales Order QV: QVSBS_BW_QRY_CPCOPA03_0001 | BW P&L Integrated Unit cost QVSBS_QRY_MVCOPA06_0001 | BW (Global Sales) Order Book QVSD_BW_QRY_MVSDSO41_SD004 | BW (Global Sales) - Review Budget & BFR QV_BW_QRY_MVSDSO61_0001 | Manufacturing Variable Costs QV_BW_QRY_CPCOPC04_0001 | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 |
Transactional data from BW and dimension from Salsforce (ID of customer/Account and SAP code from salesforce to join )
First customer is created in SAP and after a certain time window that record is forced to sales force that's why there might be rarely a gap between the two
Customer group from salesforce or BW
Always customer data is searched from BW and when needed will be enriched from salesforce
C) Used in transparency dashboard
| Source | Technical name of the field | BW query | Update Frequency | Attributes | Transformation/Rules | Reference data (Change in data feed→ delta ) | Made/New in transparency dashboard | COMMENT | User story | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Corp region ship to | Region of the ship to | BW | [0COUNTRY__C_GZONE] if empty -> [C_SHIPTID__C_GZONE] (ShipTo Region !!!) | QV_BW_QRY_MVSDSO61_0001 QV_BW_QRY_CPCOPC07_0001 | |||||||
| Corp region sold to | Geo region of the Sold To (invoiced party) | ||||||||||
| Country ship to | Country of the customer delivered | BW | [4CPCOPA03-SHIP_COUNTRY] Country of destination [10COUNTRY] Ship-to party > Country (Name) C_SHTCTRY | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_MVSDSO61_0001 QV_BW_QRY_CPCOPC07_0001 | For those with more than one query mapping, it is better to address the with BW cube directly (the main reason for this is that data might not be available in all queries for example for a customer) | ||||||
| Country sold to | Country of the Sold To (invoiced party) | "[0COUNTRY] Country if empty => [C_SHIPTID] Ship-to party\Attributes\[0COUNTRY] Country key" | QV_BW_QRY_MVSDSO61_0001 | ||||||||
| Customer segmentation | Functionality in Salesforce.com allowing you to link an account to your GBU. By doing so, you can easily find active accounts for your GBU through specific views and report on them | Bus_Rank__Corp_ Map on P&L info | QV_BW_QRY_MVSDSO61_0001 QV_BW_QRY_CPCOPC07_0001 | ||||||||
| Final consignee= ship to kA | Allow to capture internal sales for SpP | QVSBS_BW_QRY_CPCOPA03_0001 | SAME CUSTOMERS THEY HAVE different name in various sources from SAP to BW | ||||||||
| Final consignee group | Group of final consignees | ||||||||||
| Final Customer | Specific for SpP: Any entity using a Solvay Specialty Polymers product RULE : IF Final_Consignee_Group is Empty or not assigned, Then Sold-to group, Else Final_Consignee_Group | QVSBS_BW_QRY_CPCOPA03_0001 | |||||||||
| GBU Customer Segment | GBU customer segmentation is managed by GBU CE Teams in SFDC. So a customer receiving different service levels could be classified as KA for one GBU and Standard for other. Exceptions: GSKA- they remain GSKA for all GBUs. | Salesforce | GBU_Account_Type__c from SLV_INVOLVED_GBU_C searches within the fields "RCS ID", "PRS ID" and "Other ERP ID" within each account and respective source system in order to show the sales figures in Analytics Map on P&L info | QV_BW_QRY_CPCOPC07_0001 | |||||||
| GBU region | Customize dimension to reflect the pricing organisation of the GBUs SpP : ECCO region Novecare/TS : Region of Ship to with MX moved to LATAM Aroma = Region H1 | Made in transparency dashboard | Map on P&L info | QV_BW_QRY_CPCOPC07_0001 | There are correction from BW → based on application requirements there are some rules | china is under spp but for novecare will be under asia | |||||
| GBU Zone H1 | Type of region in BW (used as GBU region for Aroma) | Made in transparency dashboard | QV_BW_QRY_MVSDSO61_0001 | There are correction from BW | It can be under activity | ||||||
| GBU Zone H2 | Type of subregion in BW (used for Logistics forecast calculation) | Made in transparency dashboard | QV_BW_QRY_MVSDSO61_0001 | There are correction from BW | |||||||
| Group Customer segment/GBR GBU Segment | It uses the highest customer segment of a GBU and classifies it as Corporate C Segmentation. This dimension is relevent for corporate views only to avoid double counting of accounts. | BW or salesforce (To check) GBR is a master data (where) | there are GBU segmentation and solvay segmentation . For solvay one can be considered as dimension but not the GBU one | ||||||||
| Sales rep | Account manager in charge of a customer For SpP, Sales rep of Sold to is used (if empty Sales rep of Ship to) For others GBU, Sales rep of Ship to is used | BW → to consider getting it directly from SF | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_MVSDSO61_0001 | Problem: Comming from SF and used in BW . Should be considered to come from SF Customer can have various Sales rep | |||||||
| Ship to name | SAP customer to whom Solvay is shipping the products | BW | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_MVSDSO61_0001 QV_BW_QRY_CPCOPC07_0001 | Customer: ship to, sold to, ship to KA | |||||||
| Ship to code | SAP code for customer to whom Solvay is shipping the products | SAP | Customer: ship to, sold to, ship to KA | ||||||||
| Ship to KA (final consignee for SPP) | Dimension used to capture indirect sales | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_MVSDSO61_0001 | Customer: ship to, sold to, ship to KA check transformation from master table to BW | ||||||||
| Ship to state | Country of the Ship to | BW | not important | ||||||||
| Ship to town | City of the Ship to | BW | not important | ||||||||
| SHIP_TO_GROUP=customer group | Decide to get from SF or BW | Customer hirarchy | |||||||||
| Shipping Plant | Plant from which the material is ship to a customer | QV_BW_QRY_CPCOPC07_0001 | |||||||||
| Sold to | SAP customer to whom Solvay is selling | QVSD_BW_QRY_MVSDSO41_SD004 QV_BW_QRY_MVSDSO61_0001 QV_BW_QRY_CPCOPC07_0001 | |||||||||
| Sold to code | SAP code used to describe the sold to entity | ||||||||||
| Sold to group= 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. | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_MVSDSO61_0001 | |||||||||
| Sold_to_group_code | Grouping of Sold tos |