You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

General presentation

Objective of the application


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 (Turnover, Volume) 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.

List of contacts

  • Functional Owner of this application: Marc Piret (Sustainable Development & Energy (SDE) 

  • IS Reporting Leader: Diogo Paiva (IS Supply Chain M&S Data)
  • BW Developer: Laressa Moretti (SBS IS) 

Usage information

History

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


Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation
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
   

Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation
 CPFCTR1_2 GBU
  
  

Dataflow overview


Link to dataflow presentation: 


Functional and Technical rules on Workbench + Reporting

Rules & Explanations


Aquisition of data

Sales data is loaded from P&L using APDs.



These APDs load current + previous month into these Direct Update DSOs.

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).

Example:


Derivation of SPM characteristics


This is done in 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 


2) Derive SPM PAC (Application)

For both legacies, based on SPM product obtained in step 1 + End-Use fields (Market, Application, Segment, End-Use)


Some customizing tables were created in WBP with maintenance views (access restricted to very few users).



Example of step 1 for Rhodia legacy:


How it is stored in mapping table 





Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance

 

Key FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Reporting

Queries End User Documentation

 

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

 

  • No labels