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

Authorization objects

List of autorisation objects mandatory for the application.

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

Derivation of SPM characteristics

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

List of mapping tables

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:

1. Search with complete key = GBU + Group of act + Sub-act + Line 2 + Line 0 + Com.prod
2. If not found, search with GBU + Group of act + Sub-act + Line 2 + Line 0 + Com.prod = space
3. If not found, search with GBU + Group of act + Sub-act + Line 2 + Line 0 = space + Com.prod = space
4. and so on ... until the search is done only by GBU

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

PC SPM_MAIN is scheduled daily at 05:00 (FR time).

Average performance

Record Keeping

Keep only current year + 3 previous years.

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution