General presentation

Objective of the application

Manufacturing Unit Cost query (QV_BW_QRY_CPCOPC04_0001) is one of the components to calculate the FL ICM.

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

The BOM brings the breakdown of the Variable Cost (Raw Materials, Packaging, Tolling and Utilities).

For projected months, if forecast prices are not found for a raw material, the query extrapolates the costs from Actuals.

Latest update from Raw Material Forecast does the extrapolation of the unconfirmed prices, from the first previous confirmed price.

Therefore Manufacturing extrapolation with Actuals is only done now for prices not forecasted in the first months of the projection.

Tool Leader + IT leader of the application: 

Usage information

History

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

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

You can find the dimensions of each query here:

WP1 data flow is a replication of the solution used by Novecare before.

PF1 data flow is totally new and relies on a custom table (ZCO_PRICE_RM) populated in PF1.

Calculation view CV_FMCO_BOM was created to harmonize BOM data from both sources.

Then Manufacturing Cost is loaded in ABCOPC06

Two Transformations were added into Manufacturing object ABCOPC06 to load "Buy & Sell" products (products with no BOM)

• From ABCOPC01 - to get forecast prices for projected months
• From ODS_PCP9 - to get standard cost for the current month

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

Data loadings

Info providers and objects loaded

Process chain PC_COPC_10 scheduled monthly on CD7

Loading frequency

Monthly on Day + 7

Average performance

Record Keeping

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