1.0 Overview




The GBU Fixed Costs applciation is part of Finance domain and we use mainly the SAP data from CO (Controlling) module to get the dat for the fixed costs and GBU level.

The application GBU Fixed Costs is used to follow Solvay’s fixed costs mainly: 

  • STOT-R330 – Administrative & Commercial expenses
  • R25460 – Non proportional costs of sales
  • R27900 – Mis production.
  • R25510 – Logistics costs.

For this Application the access is provided based on the BW menu "FC - GBU Fixed Costs" and it's done via Service one.

Fill the form
https://solvay-dwp.onbmc.com/dwp/app/#/itemprofile/622 

In SAP system select the "WBP - BW Business Warehouse" 

In WBP - BW Business Warehouse : Select the Business Role select the "FC - GBU Fixed Costs"

Target Users:

GBU and Site Controllers and Plant Management

VERSION

DATE

MODIFIED BY 

DESCRIPTION

0.01

29.09.2023

Inês Vilares

Initial draft










Data Product Type 
  • Dashboard
  • Report
  • Advanced analytics
  • AI 
  • Others <specify which one>
Technologies
  • BW
  • Tableau
  • Qliksense
  • Talend
  • Dataiku
  • Others <specify which one>

Data Sources 

Note: list of all applications and various environment

  • SAP PF1 (Production environment)
  • SAP WP1
  • SAP PI1
  • BW (versions)
  • iCare CRM 
  • CORE CRM
  • Budget flat files
  • Others <specify the name of the source> 

2.0 Business Process


To understand the business process it's important to know the basic concept for the SAP CO module and how it's applicable in Solvay organization. 

The SAP CO module in the SAP ERP (Enterprise Resource Planning) system focus on financial controlling and management accounting functions within an organization. SAP CO is designed to provide tools and capabilities to effectively manage and control costs, perform internal and external accounting, and support decision-making processes related to financial aspects of the business. SAP CO is tightly integrated with other SAP modules, such as SAP FI (Financial Accounting) and SAP MM (Materials Management), providing a cohesive and comprehensive solution for managing financial data, controlling costs, and supporting financial decision-making throughout the organization.


CO Structure in Solvay:

PF1 Structure


CodeDescription
Operating concernFO01 Slv ERP Operating concer
Controlling areaCHEFERP SOLVAY

WP1 Structure


CodeDescription
Operating concernZ001 Solvay Engin.Plasti.Polan
Z006 Rhodia Europe
Z013Rhodia Europe
Z025Rhodia Latin America
Z026Rhodia Asia Pacific
Z028Solvay North America
Controlling area= Operating concern

Scope for GBU Fixed Costs


PF1 & WP1 cost centers are included as long as there are included in the hierarchy ZCBS.


For the cost elements in both systems they are included in the ZRCS-FC hierarchy.


In the systems we can see the hierarchy the user can check in the SAP transaction KSH3 - Display cost center hierarchy to see the hierarchy respective to the cost center organization.

In the systems we can see the hierarchy the user can check in the SAP transaction KAH3 - Display cost element group to see the hierarchy respective to the cost element organization.

Determination of the GBU


The fixed costs report is available by GBU. 

In WP1, the GBU comes from the Profit Center of the cost center while in PF1 it comes from the Business Area of the cost center 

In the PRocess detail section we can see in more detail how is the determination of GBU for WP1 and PF1.

For the GBU fixed costs we use the SAP information from the controlling part to analyze the fixed costs at GBU level. For this it's important to understand the structure behind and how the business see the costs and be able to analyze the information to perform their activities during and end of month.


Model behind for PF1 and WP1:

Curently we have the WBS, cost centers and orders objects with values coming from the purchase orders and accounting entries. Each object is linked to a cost center which we call it "Responsible Cost Center" and this cost center is linked to a GBU. 

We have the primary postings and during the closing process we have the settlements cycles (which will allocate the costs to a final cost center) and the final cost centers has the correspondent cost element for COPA line items to be present in the P&L report for PF1 and WP1 and in here we have also the respective value field. Additionally for PF1 with this information for the responsible cost center and GBU associated in the final cost center this will allow to the users to perform the analysis in PCA (Profit Center Accounting). 


Reporting fixed costs challenges : reconciliation SAP/BFC:

In the controlling side we have primary posting in the CO objects for the fixed costs and during the closing we have the settlement cycles to transfer/allocate the costs to a final CO object and to be in the respective lines in P&L.


3.0 Application Feature Overview


For this application find below all the workbooks available:
ReportsDefinitionPromptsBW Workbook QueryQuery Technical Name
FC - Cost center master data (Core Query)This report  is used to display the master data of all cost centers in WP1 & PF1 including the ZCBS hierarchy, the GBU and the plant code.

Mandatory:

N.A

Optional:

  • CCtr Category;
  • Change date;
  • CO area;
  • Company Code;
  • Cost center;
  • Created by;
  • Creation date;
  • Author. scope of Comp. Code;
  • Source System.
BW_WBK_FC_0003BW_QRY_C_COSTCTR_0001
FC - End month - P&L reconciliation COPA (Core Query)

The report 

The field Fixed Group 1 as the default values:

  • ZRCS-ABCNP;
  • ZRCS-ABAMO;
  • ZRCS-ASDIS;
  • ZRCS-9999.

Mandatory:

  • Fiscal Year/Period;
  • BFC GBU - Resp Cost Center.

Optional:

  • Auth Scope on Resp Cost Center;
  • BFC Geo/Zone;
  • Company Code;
  • Fixed Group 1.
BW_WBK_FC_0001BW_QRY_MPR_FC003_0003
FC - End month - P&L select - Monthly P&L Impact (Core Query)

BW_WBK_FC_0007
FC - End month - P&L select - P&L Impact (Core Query) 

BW_WBK_FC_0006

4.0 Functional Specification


4.1 General Data/Calculations 


For these reports, it’s important to understand some general concepts which are transversal to all the reports which allows the users to work with the reports in the same way as the SAP system and BFC tool.
GBURefer to the Global Business Unit and it's a concept used in our officil reporting tool. To know how we get the GBU for PF1 and WP1 systems this is detail in the Process Definition section.
Cost Center

A cost center is a specific organizational unit within a company that is responsible for incurring costs. It represents a location, department, or function where expenses are generated. Cost centers are used for tracking and controlling costs, allocating expenses, and monitoring budget compliance.

Responsible Cost Center

A responsible cost center is a subcategory of a cost center that is responsible for specific cost incurrences within the main cost center. It allows for more detailed tracking and allocation of costs within a broader cost center. Responsible cost centers help organizations drill down into expenses for greater accuracy in cost analysis and control.

Responsible Cost center is : 
-    the cost center linked to the Order and WBS of the line item (CO-OM, PS)
-    the cost center of the line item for CO-CCA 

Cost elementIt's a categorization used to track and classify expenses incurred by an organization. It represents a specific type of cost, such as wages, materials, rent, or utilities, and serves as a fundamental building block for cost accounting and reporting. Cost elements are essential for allocating and analyzing costs within the SAP CO module. It's the P&L account used to post the amounts in SAP CO document. 
PlantRefers to a specific physical location or facility within a company's organizational structure. 
Cost Center HierarchyRefers to a structured arrangement or organization of cost centers within a company. It establishes a hierarchical relationship among cost centers, typically based on their functions, responsibilities, or reporting structures. This hierarchy helps in organizing and managing cost centers efficiently for accounting, budgeting, and reporting purposes, allowing for better control and analysis of costs across the organization.

4.2 Process Detail 

4.2.1.  Report/Process Definition 

DomainFinance
ApplicationBW reports under FC - GBU Fixed Costs folder
ProviderMPR_FC003

In this section we will approach:

  • SAP BW High Level View
  • Hierarchy
  • Restrictions
  • Special Case: mixed cost center
  • Plant vs Responsible Plant
  • Workbook Details
  • Related contents
    • FC - Cost centers master data
    • FC - Fixed costs report - P&L impact

The GBU Fixed Costs it's based in an existent model since many years ago exist a controlling model to be more accurate for the GBU needs. We take the model already developed and it was enhanced to follow the fixed costs specially in the cost center at GBU level.

We have the PF1 and WP1 systems and we are using the main CO objects cost centers, WBS and orders and with this information extracted we the data is splitted in two BW tools one side the GBU fixed costs and the other solution is CBS for the functions (This scope is explained in the "Corporate Business Services application"). For both applications we use the same data base and the same cubes but the multiproviders are different also because of the authorization part. The GBU Fixed Cost application are using COPA data's for reconciliation purpose

SAP BW High Level View

To see the data from the source systems see below how the information is organized in the BW perspective: 


Hierarchy

All cost centers for this scope are stored in a unique hierarchy ZCBS.

  • The cost centers for the fixed costs are identified by an unique sub-folder in ZCBS hierarchy : ENTRP (some others filters are done). See more details for the structure for cost centers hierarchy ZCBS.
    • For GBU fixed costs, only cost centers included in the group
      • ENTRP – Enterprise Fixed Costs follow up are displayed
    • As only Fixed Costs Cost Centers are included, the following groups  (Filtered via the 2 – Function group) are excluded:
      • ECP – Variable Costs
      • EACAR – Other Operating Expenses
      • EPSRO – Post Operating Result
      • ECPVSE – Variable Sales Expenses
      • EDISC – Discontinued
      • ESERV – Services
  • The cost elements for the fixed costs are identified by specific  folder (ZRCS-FC) and sub folder. See more details for the the structure of cost elements group ZRCS-FC.



Restrictions

To determine GBU Fixed Costs perimeters, there is restrictions on: 

  • Cost center
  • Cost element
  • Miscellaneous filters 


Restriction on cost center 

For GBU Fixed Cost we only analyse ENTRP (1 Organisation attribute = ENTRP of the Responsible Cost center )

By default we must excluded some “2 Function”  attributes values in the reports. The users can delete these default filters.


Cost center hierarchy ZCBS : restrictions


Restriction on cost element:

In the cost element BW object the cost element hierarchy was denormalized (levels of the hierarchy are translated as attributes of cost element).

By default we must excluded some “Fixed cost group “  attributes values in the reports. The users can delete these default filters.


Cost element hierarchy ZRCS-FC : restrictions:

Miscellaneous filters:

Order Type : we exluded (investment) :

  • ZPM4
  • ZPM6

Project Type we exluded (investment) :

  • II
  • FD

Value type

  • 10- Real
  • 20-plan

Currency type

  • 10 company code currency 

Special Case: mixed cost center

Because some cost centers are not 100% fixed (or variable), we identify them by an attribute mixed cost center = X


For this  cost center we must check if the cost element is variable or not using XCS-ALL hierarchy (to exclude them)

 We need a characteristic to identificate these cost element (with an X as attribute )


How to identificate “Mixed Cost center “?

All cost center ENTRP with level 4 node finishing by Y in ZCBS Hierarchy



How to identificate “variable cost” element?

use XCS-ALL hierarchy

The variable cost elements are all cost element attached to a  node starting with "XCS-V"  ou "XCS-S" (or attached to sub node under XCS-VCAL et XCS- SELL).


Plant vs Responsible Plant

  • Plant is the physical plant
  • Responsible plant is financially responsible of the cost center
  • Responsible plant is an authorization object
  • In SAP (WP1/PF1)  responsible plant is in the field department of the profit center of the cost center



Workbook Details 

See below more details for each workbook available for analysis:

  • FC - Cost center master data (Core Query)
  • FC - End month - P&L reconciliation COPA (Core Query)
  • FC - End month - P&L select - Monthly P&L Impact (Core Query)
  • FC - End month - P&L select - P&L Impact (Core Query)

 This application is built around the following queries: double check with Ludovic the workbooks are not the same from the PPT

Queries built on Cost center accounting:

  • FC-End month - P&L reconciliation COPA (Core Query) is RCS model oriented. This query give you fixed Cost on 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 (before SPS project). This query give you fixed Cost on Cost center and the allocation to reporting cost center (use Partner Coster center characteristic)
  • FC-During month -details (core query) provide fixed cost on original controlling objects (orders, cost centers , WBS elements) before end month allocations. responsible cost center is the way to regroup costs.There is no P&L information 

1 Query built on P&L model (and you must have P&L authorizations)

  • P&L - Fixed Cost analysis : This query is only for COPA models (RCS and after SPS project) 

FC - Cost center master data (Core Query)

The workbook BW_WBK_FC_0003 FC - Cost center master data is used to display the master data of all cost centers in WP1 & PF1 including the ZCBS hierarchy, the GBU and the plant code.

It is used to control the consistency of the cost centers master data and ensure the FC - Create a fixed costs report is working well.

When you open the workbook for the 1st time, the following columns are displayed: 

  • Source System
  • 0 Hierarchy
  • 1 Organisation
  • 2 Function
  • 3 Sub-funct Grouping
  • 4 Sub-function
  • CO area
  • BFC GBU
  • Cost Center
  • Company code
  • CCtr Category
  • Business area
  • Profit Center
  • Obsolete object

By default the report is filtered on the ZCBS group = ENTRP but the filter can be removed to display all cost centers.

It is recommended to filter on active cost centers with "Obsolete object" = 0

For each cost center there is: 

  1. the cost center master data coming from KS03 - Display cost center
  2. the 5 levels of the ZCBS hierarchy 
  3. Other information: 


FC - End month - P&L reconciliation COPA (Core Query)



FC - End month - P&L select - Monthly P&L Impact (Core Query)



FC - End month - P&L select - P&L Impact (Core Query)

Overview of the fixed costs workbook

When you open the workbook for the 1st time, you have the following columns displayed: 

  1. GBU
  2. Function determined with the ZCBS hierarchy
  3. Cost centers
  4. Plant
  5. Cost elements Group ZRCS-FC
  6. Actual - Destination (Conv) = primary & secondary cost elements. (you can click  to see the detail). => conversion is done with the currency entered in the prompt
  7. P&L Destination (Conv). Costs in COPA after cost centers settlement in the corresponding value field. (based on ZCBS hierarchy correspondance)
  8. Actual Destination (Local) = same as (6) in local currency
  9. P&L Destination (Local) = same as (7) in local currency




Related Contents

In this section we can find some links where can help to understand some concepts:

FC - Create a fixed costs report — This page explains how you can create step-by-step an accurate fixed costs report for a plant or a GBU.

FC - Cost centers master data — This page explains how you can display cost centers master data. It is a useful tool for preparing and validating master data to ensure the accuracy of fixed costs reports.

FC - Fixed costs report - P&L impact — The P&L impact fixed costs query is used when a cost center is shared with several GBUs.


5.0 Non-functional Descriptions 


5.1 Usability

5.2 Regulatory Compliance

5.3 Security

5.4 Performance

5.5 Reliability  

5.6 Scalability

5.7 Compatibility

5.8 Availability

5.9 Refresh of the Data

The loads for the GBU Fixed Costs application is the following:

Closing Time:

Outside of Closing: it's one time on a daily basis.