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: Name of project or main leader for the application + reporting coodinator
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
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
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
BOM is loaded from WP1 and PF1 in different data flows.
There are 2 different queries:
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
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 from WP1 with FISCPER = 03/2022 (to extract BOM data from 03/2022)
CV will generate RUNPER 03/2022.
Run DTP from PF1 with FISCPER = 02/2022 (to extract BOM data from 02/2022)
CV will generate RUNPER 03/2022.
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
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 Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016