SPM stands for "Sustainability Portfolio Management".
It's a Solvay proprietary approach to assess business sustainability risks and opportunities that runs on PF7.
The objective of SPM reporting in BW is to provide a "Sustainability view" (Market Alignment, Operations Vulnerability) for the sales of the group.
Sales are extracted from P&L in WBP and then enhanced with an SPM dimension, through a sequence of steps (lookup in mapping tables).
SPM Master Data (SPM Product, SPM Application) is loaded from PF7.
Functional Owner: Marc Piret (Sustainable Development & Energy (SDE)
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
The project had 2 phases:
1 - First development covering most of the GBUs (pilot: Aroma and Special Chem)
link to the project folder: https://drive.google.com/drive/folders/0BxkySrtHryoBejV1VG5CbmNwM3c
2 - Extension for GBU Specialty Polymers and Composite Materials
link to the project folder: https://drive.google.com/drive/folders/18bJbaF-EfKSDfYl5X1uWe25xiwa99ClU
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZBI_RCS_SPM_A01 | Sustainable Portfolio Management - End User Role | Role for the application |
| ZR_RCS_CA_M58 | SPM - Sustainable Portfolio Management | Role menu for the application |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| CPFCTR1_2 | GBU |
Link to dataflow presentation:
Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way
Sales data is loaded from P&L using APDs.
The APDs load current + previous month into Direct Update DSOs, then it goes to the next level DSOs, which keep all historical sales.
The Sub-Activity field (0G_CWWE01) is very important to define the GBU and Group of Activities.
From Rhodia query, it gets directly field 0G_CWWE01 (normally IECRAxxx)
From Solvay query, (due to PQ1 decomission and SpS projects), it gets from different fields depending on the month being loaded. It takes C_TECHBA (old object from PQ1) if month < 01/2018 (kept for reloading purposes) and from C_TECPCT2 if month >= 01/2018. In any case, it takes the attribute C_REST_BA (Restated BA) and move to 0G_CWWE01 (single object in the query for both legacies).
Example:
List of APDs:
(The last 2 APDs are not scheduled on a regular basis. They were created for reloading purpose, allowing to inform the period to be loaded in the query variant).
Some mapping tables were created in WBP with maintenance views (restricted to very few users).
The access is done via transaction ZSPM in WBP.
There are basically 2 steps:
1) Derive SPM product
For Rhodia Legacy - based on GBU / Group of Activities / Sub-Activity / Product Line 2 / Product Line 0 / Commercial Product
For Solvay Legacy - based on GBU / Group of Activities / Sub-Activity / PIF hierarchy / Product hierarchy / Material Group
Example:
How it's stored in mapping table
How the derivation is done from a sales record
2) Derive SPM PAC (Application)
For both legacies, based on SPM product obtained in step 1 + End-Use fields (Market, Application, Segment, End-Use)
Example:
How it's stored in mapping table
How the derivation is done from a sales record
| Table | View | Description | Comment |
|---|---|---|---|
| ZSPM_TAB1 | ZSPM_V1 | SPM Product (Rhodia) | |
| ZSPM_TAB2 | ZSPM_V2 | SPM Product (Solvay) | |
| ZSPM_TAB3 | ZSPM_V3 | SPM Applications | |
| ZSPM_TAB4 | ZSPM_V4 | SPM End-Use to Market (SPP) | Specific to GBU Specialty Polymers |
| ZSPM_TAB5 | ZSPM_V5 | SPM Applications (SPP) | Specific to GBU Specialty Polymers |
| ZSPM_TAB6 | ZSPM_V6 | SPM Non-integrated GBUs | Only for GBUs where sales doesn't come from P&L |
Important: the lookup in the mapping tables is done from the most specific case (complete key) to the most generic case, so for example, when reading ZSPM_TAB1 to get SPM product, it does the following:
In terms of the data flow, this is where these lookups are implemented
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
PC SPM_MAIN is scheduled daily at 05:00 (FR time).
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | 50 minutes |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Keep only current year + 3 previous years.
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016