You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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.



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.

Role CodeRole DescriptionExplanation









Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






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)


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.



A calculation view was created to harmonize BOM data from both sources


Then Manufacturing Cost is loaded in ABCOPC06



Functional and Technical rules on Workbench + Reporting

Rules & Explanations


Novecare (WP1) works with Standard Cost.

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


SpP (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.


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


Run DTP for WP1: DTS_CV_FMCO_MAN_COST_RCS -> ABCOPC06

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


Run DTP for PF1: DTS_CV_FMCO_BOM_FORECAST -> ABCOPC06

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


Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance


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

Reporting

Queries End User Documentation


Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels