General presentation

Objective of the application

Manufacturing VC query (QV_BW_QRY_CPCOPC04_0001) is one of the components to calculate the FL (Forward-Looking) ICM.

The Variable Cost (VC) of a product, used to calculate the ICM (Integrated Contribution Margin). is the sum of Raw Materials + Packaging + Tolling + Utilities costs.

We bring these detailed costs from SAP from the BOM (Bill of Material).

The BOM brings, for a given Finished Product/Plant/Month, the detailed list of components with the corresponding quantities and costs.

In the query, we calculate the FL Variable Cost for projected months, using the forecasted prices for Raw Material and Energy (input by the users in IP workbooks) and multiply them by the quantities from the BOM. If no forecast is found, then we extrapolate last Actual price to the future months.


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.

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M83Forward Looking ICM - ManufacturingRole Menu
ZBI_RCS_CO_A09Forward Looking ICM - ManufacturingAuthorization objects



Authorization variables

List of authorization variables mandatory for the application.

Authorization variablesObject
V_CPFCTR1_2_0006CPFCTR1_2
V_C_PLANT_0012C_PLANT
V_C_AUTHMA_0001C_PLANT__C_AUTHMA

Dataflow overview


There is one Composite Provider CPCOPC04.

ADSOs ABCOPC06 (WP1) and ABCOP06B (PF1) store the data, which combines BOM (Actuals) + Forecast data.

BOM data flow

First step to calculate Manufacturing Cost is to load the BOM.

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

WP1 data flow is a technical replication of the old BOM query for Novecare (QV_BW_QRY_CPCSPR02_0001). We select all the finished products sold in the past 24 months (DTS_PU_RM01) and do the BOM explosion, level by level (via lookup in ODS_PCP1) in a BW routine.

PF1 data flow is totally new for Pricing Project and depends on a table generated in PF1 (ZCO_PRICE_RM). It's more straight-forward because the logic of the BOM explosion resides in PF1 and there is not much transformation of data on BW side (on the other hand, we don't have all the level of detail as in WP1).

The BOM data from both ERPs is then harmonized in CV_FMCO_BOM to be consumed by the Manufacturing Cost CVs.


There are 2 different BOM queries (not used directly in Pricing dashboard, but can be used to check the BOM data with all the available granularity)

You can find the dimensions of each query here:


Granularity of the BOM

From WP1 (Novecare), each record in the BOM is an individual component, which is either a Raw Material (C_BOMCPT) or an Activity Type (0ACTTYPE).

From PF1 (SpP), we don't have the same granularity. Only the critical raw materials are detailed (with quantity, price and cost). Then we have some "buckets" that aggregate the costs as follows:

Buy & Sell products

These are products that the GBU buy and re-sell, and they have no BOM in SAP.

They are identified in Critical Raw Material Master Data C_FLRMAT, where “Critical flag” (C_FLRMATF) =  “B” (No BOM)

We create a "virtual" BOM in BW assigning the same material code as both Finished Product and Raw Material, and the quantity is 100% of the lot size (1000 KG).

The forecast price for these materials is collected in the workbook and saved in ABCOPC01 normally as the other critical raw materials.

The actual price in this case comes from P&L. query QVSBS_QRY_MVCOPA06_0001. (technically we take data directly from ODS_PCP9 field C_MVR_CP).


Forecast data

It's saved in following ADSOs:

The prices are input by the users in the corresponding BW-IP workbooks.






You can find FL-ICM overall architecture here:



Functional and Technical rules on Workbench + Reporting

Rules & Explanations


Novecare (in WP1) works with Standard Cost.

Beginning of month M, we have the cost for month M.


Specialty Polymers (in PF1) works with Actual Cost.

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 (for example, April Forecast is calculated with the price from March).


In Manufacturing Cost calculation view, BOM (Actuals) is combined with Forecast data.

2 different calculation views were created as 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 from DTP (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 (calendar day 7)


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


Key FigureEstimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

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 Name

Info-object

Selection Type

Required

Description/Explanation

0I_CALMO0CALMONTHIntervalNoCalendar Year/Month
V_C_PLANT_0012C_PLANTAuthorization with InputNoPlant
V_CPFCTR1_2_0006CPFCTR1_2Authorization with InputNoGlobal business Unit
V_C_MATNR2_0001C_MATNR2Select OptionNoRaw Material
V_C_AUTHMA_0001C_AUTHMAAuthorizationNoAuthorization Scope
V_0CALMONTH_0062C_RUNPERIntervalNoRun Period

Variable Sequence

Filters

Key figures

Characteristics

Broadcast

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