Requirements | Description | Comment | Source in transparency | Technical name of the source in transparency | Transformation |
|---|---|---|---|---|---|
| Sold to | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | ||||
| Ship to | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | ||||
Material | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | ||||
| Company | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | Integration rate from BW (TO CONSIDER A NEW DIMENSION FOR SOLVAY COMPANY) | |||
| Shipping plant | Plant from which the material is ship to a customer | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | Consider plant dimension | ||
| Manufacturing plant | Last plant in the product production process | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 | For sale transactional data (COPA03) → WP1: Production_plant_in_Material_W_Key PF1: Origin_Plant_Key For forcast COPC07 Manufacturing_Plant_Key ---------------------------------- Not relevant in this Q (planned for q4) → COPC04→ WP1 : C_PLANT PF1: ORIGIN PLANT forecast→ copa07 Depends on what transactional data we want to use in the fact table we use various queries. For example | ||
| Sales order | |||||
| Incoterms | Incoterm will change the price. | It is transactional data (It is a component of the CPC so it is a transactional data). for Novecare CPC is ship to + material + incoterm Notes: CPC itself can be a table but risk (the CPC table has GBU associate) Suggestion to find a master data in BW→ Designing the dimension may be for next PI | Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001 Incoterm in the  | ||
| Measure: Fcst Sales [Est Act] (€) | |||||
| Measure: Fcst Volume [Est Act] (KG) | |||||
| Measure: Fcst Unit Price [Est Act] (€/KG) |
