| JIRA | Title | Description. What problem are we trying to solve? | Requested by | Business Value | Complexity | Tentative Timing |
|---|---|---|---|---|---|---|
| tbc | Unified Timeline | A table joining historical sales with price forecast. Columns: Calendar month, last invoice price, forecast price, .... Level of granularity: aggregation of measures at CPC level,... Possibility to join with other tables: to be joined with all the dimension tables Acceptance criteria: updated as soon as a CPC appears in the forecast query,... | 2024.Q1 or Q2 | |||
| PC-204 | Account Mgr Allocation | Create a centralized master source indicating which CPC is managed by which account manager. This feeds into multiple reports, including Transparency, Orderbook, and Sales Incentive Plan (Bonus) reporting. Today different sources (SAP / Salesforce) are contradicting each other. There is a business rule describing which source takes priority for which purpose. See for example: https://solvayagile.atlassian.net/browse/PT-1391 | Melissa Bahr | Medium | Medium | 2023.Q4.3 or 2024.Q1.1 |
| P&L Categories | Translate the detailed financial P&L into a simplified and harmonized Pricing P&L. | Ayoub Kadioui | High | Low | 2023.Q4.3 ? | |
| Unique Customers | Provide a dataset on Customer Master that contains 1 record per customer across all source systems, rather than a record for every source system separately. | Ayoub Kadioui | Medium | Medium | 2024.Q1.1 ? | |
| Quality Complaints | Complaints are managed in Salesforce CRM. The Customer 360 dashboard (non-Pricing) reports on this data, and there has been some business discussion to analyze if there is any significant impact of quality complaints on price levels. | Mariana Chavez | Medium | Medium | 2024.Q2 or later | |
| CPC table design → CPC Region | Currently there is a field in the fact table in the data lake called GBU region. It is a field made by the transparency team based on the customer Zone available in the COPA03 query. Transformation rules here 2) Transactional data - Historical sales Since it is unique per GBU and CPC, it was discussed and suggested to move this attribute to the CPC table. | Azadeh (discussed with Ayoub and Franck) | To decide on the design Q4 | |||
| CPC table design→ GBU and CPC combination as a primary key | Azadeh (Discussed with Ayoub) | To decide on the design Q4 | ||||
| CPC table design → aggregation | Measures calculations is required at both combination of: 1) Customer+material+incoterms 2) Customer+ material | Azadeh | ||||
| Ship-To KA attribute for the sales forecast fact table | we lack the information in the forecast query, we should retrieve it from historical sales. (coming from order line transaction from copa03. The ship to ka assigned to the Last order line of a CPC from COPA03) To proceed, we should go through the same flow as "last price logic" but instead of retrieving a price, we just extract the dimension value. Multiple fields will be certainly retrieved that way (except if already part of a master data). | Azadeh (Franck) | ||||
| Historical data view to users | View to users from fact table of P&L query | Azadeh | ||||
| Forecast data view | ||||||
| Unique Customer ID view | For transparency dashboard to have just one row per Customer ID regardless on whether we retrieve several from the different SAP instances. This (in principle) will make the Transparency Dashboard not to have to filter the data when consuming it. | Ayoub | TBD | Low | TBD | |
| ||||||
| Outlier Detection | Detect price outliers (e.g. large statistical deviation from product family average price) and add a "price outlier" flag to be able to filter out the noise. | Mark | tbd | tbd | tbd | |
| Customer Annual Volume | Calculate total customer annual volume or annual revenue as a derived metric in the data lake to support price analysis | Mark | tbd | tbd | tbd | |
| Order creation date v posting date analysis | Analyze the difference on recognizing costs on order creation date (commercial P&L) vs financial posting date (pricing P&L). For Q4.1, we went with what Transparency is doing = financial posting date, to make the P&L easier to reconcile with Finance - but downside is that makes it harder to check profitability on individual orders. | Mark | tbd | tbd | tbd | |
| Import / Export Trade Statistics | Trade data available from public sources (e.g. Eurostat) through API. This data shows import & export values and prices, which can be used for competitive analysis. | Mark | tbd | tbd | tbd |
Overview
Content Tools
Tasks
1 Comment
Azadeh Nasiri
Van De Wielle, Mark
According to the discussion we had yesterday, I created this page to only collect ideas from pricing stakeholders to understand what would be useful for them to have in the data lake. So far, we only considered the bare minimum to cover CS price optimization requirements.
It is highly important at this stage to only think of the requirements (what) than the design/solution (how). Doesn't need to be detailed now. Let me know what do you think?