General presentation

Objective of the application

Manufacturing VC query (QV_BW_QRY_CPCOPC04_0001) is one of the components to calculate the FL ICM (Forward-looking Integrated Contribution Margin).

It combines BOM data for Actuals + Forecast.

The BOM (Bill of Material) brings the detailed costs for each component (down to raw material/activity) for each Finished Product/Plant.

The Variable Cost of a product is made up of Raw Materials + Packaging + Tolling + Utilities costs.

For projected months, we use forecasted prices for Raw Material and Energy (collected in the respective BI-IP workbooks) and multiply by the quantities from the BOM. If forecast prices are not found, we extrapolate from Actual last prices to calculate the FL Variable Cost.

Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator

Usage information

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

History

Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information

Roles & Access

Roles and access

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

Authorization variables

List of authorization variables mandatory for the application.

Dataflow overview

BOM is loaded from WP1 and PF1 in different data flows.

There are 2 different BOM queries:

• QV_BW_QRY_CPCOBOM1_0001 - for WP1 GBUs (for example Novecare)
• QV_BW_QRY_CPCOBOM2_0001 - for PF1 GBUs (for example Specialty Polymers)

You can find the dimensions of each query here:

You can find FL-ICM overall architecture here:

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Novecare (in WP1) works with Standard Cost.

So beginning of month M, we have the cost for month M.

Specialty Polymers (in PF1) works with Actual Cost.

So beginning of month M, we have the cost for month M-1 (last closed month).

In order to have a common view, for a unique Running Period, this is the way we generate data in Manufacturing Cost query.

Note that for Novecare (WP1), there is a month lag in the Forecast price for the projected months.

We can only filter a single period to read BOM data, so in each CV, Run Period is calculated differently:

CV_FMCO_MAN_COST_RCS (WP1)

RUNPER is equal to FISCPER used to extract BOM

CV_FMCO_MAN_COST (PF1)

RUNPER = FISCPER from DTP +1

For example: to generate RUNPER 03/2022

DTP from WP1 with  FISCPER = 03/2022 (to extract BOM data from 03/2022)

CV will generate RUNPER 03/2022.

DTP from PF1 with FISCPER = 02/2022 (to extract BOM data from 02/2022)

CV will generate RUNPER 03/2022.

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Process chain PC_COPC_10 scheduled monthly on CD7

Loading frequency

Monthly on Day + 7

Average performance

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

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Main queries

Manufacturing Unit Cost query : QV_BW_QRY_CPCOPC04_0001

Main functionalities

It combines BOM (Bill of Material) data for Actuals + Raw Material Forecast.

Global properties

Variables

Definitions

Variable Sequence

Filters

Key figures

Characteristics

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.