Operating segments |
|---|
Operating segments |
are not available in BW queries. |
For ExCom and corporate reporting purpose, we add the Operating Segment based on the GBUs : Materials : Specialty Polymers (SP), Composite Materials (CM) Chemicals : Soda Ash and Derivatives (SD), Peroxides (PE), Silica (SI), Coatis (CT) Solutions : Aroma Performance (PA), Novecare (CS), Special Chem (CH), Technology Solutions (TS) |
Market Mapping |
|---|
Market and Segment displayed in the dashboard is taken from the hierarchy : Market / Segment / Application / End-Use The End-Use is defined by each GBU based on (GBU x Activity x ShipTo x Product) in GBR repository system. Each End-use use is attached to a specific Market Application/Segment/ Application Market hierarchy, managed by Excellence Center.Corporate Strategy. In order to re-write the historical data/Order book Snapshots stored in QlikSense, we re-map the whole history based on the GBR Master Data on a daily basis. This is done by taking the mix; GBU x Activity x ShipTo x Product, and remap the historical data with the current definition of Market/Segment etc. BW End-Use master data source: QV_BW_QRY_MVSDAD01_0003
Specific case for SpP : SpP define the End-uses within ICARE CRM system. A one shot updated update of GBR based on ICARE data has been was performed early may 2020. This one-shot mapping provide provides a market to 93% of PF1 Sales (in revenue) for SpP. WP1 sales are not yet mapped. As of today (late June 20), we're currently working with Excellence Center to include SpP in the GBR Maintenance process for End-Uses. Still in progress by mid-july 2020.
Specific case for Composite Materials : The dimension dimensions AERO Pregram and AERO Market can provide are used to map into the corporate market dimension used by other GBUs (through a manual mapping). Not yet implemented. |
Country and Zones mapping
In order to re-align all country labels, from very distinct sources (PF1 / WP1 systems through BW cubes, flat files, ...), we decided to map the countries labels based on the country codes.
Depending on the GBU, the system ... countries such as Mexico or Pakistan may not belong to the same zone. To prevent that case of a country not fully linked to one unique zone, we also derive the zone based on the country using a mapping that should be aligned with the corporate definition.
Mapping update :
The mapping is currently aligned with the corporate definition of Countries and Zones. If this definition changes and is reflected in BW, the mapping needs to be updated since it will totally override the zones from the sources (BW or flat file)
Discrepancy investigation :
This dashboard is designed to provide a group-wide view on the orderbook. Therefore the figures may differ from what the GBUs are used to see, due to countries that may not belong to the right zone based on GBU definition (Pakistan is Middle East - EMEA for Soda-Ash and Peroxides, for instance).
This won't give the lower levels such as Segment. There are current efforts to apply the same logic in QlikSense (as not possible in Global Sales) as already done in the P&L, by using BW Master data query, to re-map Ship-to x Material x Main Specification x % on Program → to a Segment and Market. This will allows the market and segments to be populated when Composite Materials have fully deployed SAP |
. |