Access Management 

DataFlow

In Solvay group there are 2 controlling models

• WP1 model: fixed costs are managed in CO and are allocated to the P&L in COPA.

• PF1 model:

  • Until end of 2017, fixed costs were managed in CO and were allocated to CO on "reporting" cost centers.

  • From 2018, the P&L in PF1 is fully managed in COPA

WP1 model & PF1 (from 2018) model: fixed costs are managed in CO and allocated to the P&L in COPA

The goal of the application is to give (by default) to users Destination Cost centers by group of cost elements and to give from COPA the P&L destination (value field & BFC account , destination GBU )

The allocation to COPA are identified with the cost element group 'ZRCS-CO COPA

It enables the user to analyze fixed costs on cost centers and reconciled data with the P&L

PF1 model (until 2017): fixed costs were managed in CO and were allocated to CO on "reporting" cost centers

The goal of the application is to give (by default) to PF1 users, Destination Cost centers by group of cost elements and to give from P&L destination. In the former model PF1 the P&L was set-up using reporting Cost centers (=have the type "reporting")

The allocation to Reporting cost centers is identified with the cost element group 'ZRCS-CO COPA

The attribute "BFC GBU" of the partner cost center for cost elements group 'ZRCS-CO COPA gives the users the BFC GBU destination.

Overview

MPR_FC003

• Remove old data: Only keep the 5 last years in the cubes in order to make the cube lighter and gain space in BWA.

• Fixed Cost project: A project is in progress to have fixed costs reporting by plant and GBU. This project will be finished end of july.

This project is a mix between CBS and COPA in order to provide fixed cost reporting by plant and GBU. The objective is also to replace actual fixed cost application for Rhodia legacy FC2.

For this project, we have created specific info areas

We have created MPR_FC003 for this purpose. This multi provider has same cubes as CBS application, two cubes from COPA application and one PAX cube.

Technical Rules on Workbench

CUB_FC003 - Fixed costs Analysis PIM → not loaded

CUB_FC002 - Fixed costs Analysis Acetow → loaded but with 0 records.

CUB_FB001 - Fixed costs Budgets → not loaded since 2019.

CRCOPA29, CRCOPA01 & CRCOPA22 documenation in P&L Documentation.

CBS application and GBU Fixed Costs application

• BW RTR - CBS (WBP) (=Corporate Business Services) is an application used to follow-up costs of Solvay's function

• GBU Fixed Costs application is used to follow-up GBU Solvay's fixed costs 

There was an old application for fixed costs: FC2 application. This application is replaced by GBU Fixed Costs.

These 2 applications are using CO data's (cost center (CO-CCA), WBS (PS) and Orders (CO-OM)) and sharing (in most cases) the same infoproviders

All cost centers (CBS or fixed Cost) are included in a common cost centers hierarchy ZCBS.

Differences between the 2 applications:

• Cost centers displayed in the GBU - fixed costs report are included in the sugroup ENTRP of the ZCBS hierarchy (Others filters are done - see below),

• Fixed Costs cost elements are identified with specific groups of the ZRCS-FC hierarchy,

• Authorization objects are different,

• GBU Fixed Cost application is using COPA data's

The 2 applications are using the same source of data's but the scope is different (cost centers selection / queries).

CBS technical documentation: Technical Documentation - Corporate Business Services - Function costs report CUB_FC002 / CUB_FC003 / CUB_FC004 / CUB_FC005 / CUB_FC006 / CUB_FC007)

Master Data: Cost Center (C_COSTCTR) and Responsible Cost Center (C_RESP_CC)

• The cost center is the cost center of the line item

• The responsible cost center is the cost center linked to the Order and WBS of the line item

The responsible Cost center is the main object in GBU Fixed Cost queries.

Master Data : Responsible plant (C_RPLANT)

The plant of the cost center is determined in the Profit Center department. It has the same proprieties as a standard plant code.

The Responsible plant is a navigational attribute of the cost center and the responsible cost center.

Master Data : Purchase Domain and Purchase Segment

The fixed Costs data flow has been improved (2020/02) in order to add NAV providing Purchase Domain and Purchase Segment from different points of view : Material and Vendor.

The following NAV have been added in the flow till the multiprovider MPR_FC003

• C_MATNR2__C_DOMAIN (populated in C_MATNR2 through a lookup on C_MAT_GRP)

• C_MATNR2__C_MAT_GRP

• C_MATNR2__C_SEGT (populated in C_MATNR2 through a lookup on C_MAT_GRP)

• C_VENDOR2__C_DOMAIN (populated in C_VENDOR2 through a lookup on C_VENDID)

• C_VENDOR2__C_SEGT (populated in C_VENDOR2 through a lookup on C_VENDID)

To be implemented : Business needs as well Domain and Segment coming from Purchase Order.

Master Data : BSA Group of the Responsible Cost Center

The fixed Costs data flow has been improved (2020/02) in order to add NAV providing BSA Group of the responsible Cost Center.

The following NAV have been added in the flow till the multiprovider MPR_FC003

• C_RESP_CC__C_BSAGRP

The BSA Group attribute has been added in C_COSTCTR based on the 0COSTCENTER Hierarchie named Z013ZCBS_BSA.

The hierarchie Z013ZCBS_BSA is loaded in master data C_FUNCT_4:

And then in transformation "IOBJ C_COSTCTR -> IOBJ C_COSTCTR" a lookup is done to fill C_BSAGRP:

Restrictions

Filters on Cost centers

The  ZCBS hierarchy was denormalized (levels of the hierarchy are translate as attributes of cost center and responsible cost center)

• In the  GBU Fixed Costs application, we can only display cost centers included in the group ENTRP and or ZNS-FUNCT (1 Organisation attribute = ENTRP of the Responsible Cost center )

• By default the following groups "2 Function" are excluded of the report but it can be displayed by the user.

  • ECP - Variable Costs are excluded

  • EACAR - Other Operating Expenses are excluded

  • EPSRO - Post Operating Result are excluded 

  • ECPVSE - Variable Sales Expenses are excluded

  • EDISC - Discontinued are excluded

  • ESERV - Services are excluded

Filters on Cost elements

• “ZSOLV”  hierarchies are available below fixed costs queries, and can be added into reports.

CBS queries

BW_QRY_MPR_FC001_0001 - CBS - Functions - end of month

BW_QRY_MPR_FC001_0002 - CBS - Functions by Companies - end of month

BW_QRY_MPR_FC001_0003 - CBS - Functions - during month

BW_QRY_MPR_FC001_0004 - CBS - Functions by Companies - during month

BW_QRY_MPR_FC001_0005 - CBS - Synthesis of the Functions

GBU fixed costs

BW_QRY_MPR_FC003_0003 - FC-End month - P&L reconciliation COPA

BW_QRY_MPR_FC003_0008 - P&L Impact

BW_QRY_MPR_FC003_0009 - FC-End month - Monthly P&L Impact

One Solvay

BW_QRY_MPR_FC003_9000 - ONE SOLVAY-End month - Cost center analysis

In all above fixed cost reports the below ZSOLV fields are added in free characteristics

0COSTELMNT__C_CELTHZ1 -> ZSOLV Group 1

0COSTELMNT__C_CELTHZ2 -> ZSOLV Group 2

0COSTELMNT__C_CELTHZ3 -> ZSOLV Group 3

0COSTELMNT__C_CELTHZ4 -> ZSOLV Group 4

Removed the hierarchy ZRCS-FC from the following queries (Fixed Cost Group1 – Fixed Cost Group 4) and added ZSOLV Group 1 - ZSOLV Group 4 in the reports.

BW_QRY_MPR_FC001_0001 - CBS - Functions - end of month

BW_QRY_MPR_FC001_0002 - CBS - Functions by Companies - end of month

BW_QRY_MPR_FC001_0003 - CBS - Functions - during month

BW_QRY_MPR_FC001_0004 - CBS - Functions by Companies - during month

BW_QRY_MPR_FC003_0003 - FC-End month - P&L reconciliation COPA

BW_QRY_MPR_FC003_9000 - ONE SOLVAY-End month - Cost center analysis

BW_QRY_MPR_FC003_0008 - P&L Impact

BW_QRY_MPR_FC003_0009 - FC-End month - Monthly P&L Impact

The hierarchy ZRCS-FC are no more visible in the reports.

By default some "ZSOLV  Group 4" are excluded from the report. The user can delete the default filter.

Removed the hierarchy ZRCS-FC in the prompts (Fixed Cost Group 1) of the below queries and replaced with hierarchy ZSOLV Group 4 with default exclusion of the below values

• ZSO-IND31
• ZSO-IND51
• ZSO-29999A

BW_QRY_MPR_FC003_0003 - FC-End month - P&L reconciliation COPA

BW_QRY_MPR_FC003_0008 - P&L Impact

BW_QRY_MPR_FC003_0009 - FC-End month - Monthly P&L Impact

This Hierarchy is centrally maintained 

Special cases : Cost center mixing fixed and variable costs

In PF1, some cost centers are mixing fixed and variables costs. These costs centers are included in a group  used to identify this type of cost center. 

For these cost centers, variable cost elements are excluded using the XCS-ALL hierarchy .

How to identificate "Mixed Cost center "

Mixed cost centers are included in a group ending with "Y" in the ZCBS Hierarchy

How to identificate "variable costs" cost elements

A cost element is condidered as variable when it is included in the group "XCS-SELL" or "XCS-VCAL" in the  XCS-ALL hierarchy

Others filters in queries

Order Type - are exluded :

• ZPM4

• ZPM6

Project Type - are exluded :

• II

• FD

Value type

1. 10 - Actual

2. 20 - Plan

Currency type

• 10 company code currency

COPA integration

The reconciliation between Fixed Costs and COPA is using the cube CRCOPA01 - Profitability Analysis: COPA - IECRA Determination. Source of cube DBCOPA02 is already documented in P&L documentation.

MAIN MAPPINGS (see technical documention to have the complete mapping)

BFC GBU (and activities) used in P&L reports have to be mapped with the BFC GBU of the cost center. A cost center of a GBU can be allocated to a different GBU in the P&L

In this example, the cost center is assigned to the GBU Novecare (based on the profit center of the cost center in WP1) but it is assessed to the GBU 'TECHNOLOGY SOLUTIONS  in COPA and on the BFC account R26152 and R27200

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Reporting

Role menu queries

For below QV queries Conso View 2 & Conso View 3 for Scope ECO & SCO was not added earlier, the same was added and now report can be executed for conso view 2 & 3 along with conso view1, following changes have been applied.

Report QV_BW_QRY_MPR_FC003_0001 changes

Key figure used in the report as below

1. Total Cost (debit)
2. Over/Under absorded (CC settle. to VVD45)

Key figure formula with conso view 1 & 0

The conso view 2 & 3 is added in the existing formula

Report QV_BW_QRY_MPR_FC003_0002 changes

Basically the calculated key figure BW_CKF_MPR_FC003_0033 is used to calculated conso view for below 5 key figures.

Calculated key figure for conso view 1 & 0

Conso view 2 & 3 is added in the calculated key figure along with conso view 1 & 0

There are 3 queries in the application

Queries built on Cost center accounting

• FC-End month - P&L reconciliation COPA (Core Query). It is the core query which is detailing fixed costs by Cost center and the allocation to COPA (and also the COPA GBU/COPA BFC account ...)

• FC-End month - P&L reconciliation PF1 (Core Query) is PF1 model oriented (until 2017). It should not be used after 2018. 

Query built on P&L model (with P&L authorizations)

• P&L - Fixed Cost analysis: it gives the list of cost centers assessed to each BFC heading

GBU Fixed Cost workbooks

A workbook is created based on each query. Role menu workbook:

• BW_WBK_FC_0001 → BW_QRY_MPR_FC003_0003

• BW_WBK_FC_0003 → BW_QRY_C_COSTCTR_001

• BW_WBK_FC_0006 → BW_QRY_MPR_FC003_0008
• BW_WBK_FC_0007 → BW_QRY_MPR_FC003_0009

Selection screen Workbook (BW_WBK_FC_0001)- FC-End month - P&L reconciliation COPA (Core Query)

BW_QRY_MPR_FC003_0003 documentation

BW_QRY_MPR_FC003_0008 documentation

BW_QRY_MPR_FC003_0009 documentation

Data Loading

Info Providers and objects loaded 

CUB_FC003 - Fixed costs Analysis PIM → not loaded

CUB_FC002 - Fixed costs Analysis Acetow → loaded but with 0 records.

CUB_FB001 - Fixed costs Budgets → not loaded since 2019.

Data Quality Control

Data come from SAP system. To compare data between BW and sources systems, check propagation layers.

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticity, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>