General presentation
Objective of the application
Energy Forecast prices are collected in a BW-IP workbook and then integrated in Manufacturing VC query to calculate the Energy cost for projected months.
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 Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M79 | Forward Looking ICM - Energy - Menu | Role Menu |
| ZBI_RCS_CO_A07 | Forward Looking ICM - Energy | Authorization objects |
Authorization variables
List of authorization variables mandatory for the application.
| Authorization variables | Object |
|---|---|
| V_C_AUTHMA_0001 | C_PLANT__C_AUTHMA |
| V_C_PLANT_0012 | C_PLANT |
| V_CPFCTR1_2_0006 | CPFCTR1_2 |
Dataflow overview
Link to dataflow overview diagram:
https://app.diagrams.net/#G1RLCMm5yN06FOmvBvRN5HOSCk1xwCFtvl
There are 2 workbooks concerning Energy Forecast:
The first one ("FL - Energy Forecast") is common for Novecare and SpP and is used to save Energy price typed by the users. This is done by plant/activitiy (ELEC, GAS, STEAM, etc)
Energy price is stored in DSO ABCOPC10.
For Novecare, we get the latest Actual price (current month M) from the BOM, for each plant/activity, to use as proposed price in the workbook for future (M+12) months. Then the user can change the prices and save.
For SpP, there is no proposed price because we don't have this level of detail (by activity type) in the BOM in PF1. So we load from the BOM only the plants, then the activities are "artificially" created in BW from the values in master data C_ENERGY, and then the user can input the prices.
For SpP, there is a specific process covered by the second workbook ("FL - Energy Forecast - SPP Usage Factor) where the users save the usage factor by plant/H4/product hierarchy.
Actually this is where the Energy Forecast process starts for SpP.
1) Calculation View : CV_FMCO_SP_FORE_UF
This calculation view will generate all the combinations Plant/H4/Prod.Hierarchy/Activity to be loaded in ABCOPC15.
Filters:
1- All Material with product Hierarchy : ("0PROD_HIER" != '')
2- GBU "CPFCTR1_2" = 'SP'
3- "C_ENERGY" = 'ELEC' or "C_ENERGY" = 'GAS' or "C_ENERGY" = 'STEAM' or "C_ENERGY" = 'OTHER'
After data is loaded in ABCOPC15, then it's used in CV below to calculate the Energy Cost (quantity from ABCOPC15 * price from ABCOPC10)
2) Calculation View : CV_FMCO_SP_FORE_UF2
This will be loaded into ABCOPC16, where the increase percentage is calculated (comparing current month x previous month).
Integrating Energy Cost in the Manufacturing CV for Novecare
In CV_FMCO_MAN_COST_RCS, for each plant/activity from the BOM, we get the forecast price from ABCOPC10 for the subsequent months.
If no forecast is found, Actual data is extrapolated for the future months (same logic as Raw Material Forecast)
Link to project folder:
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
Dependencies with other applications
Data loadings
Info providers and objects loaded
1- DSO DPSDSO92 : for having H4 Code (PC_FIWC_02)
2- DSO ABCOPC15 : for the Usage Factor (PC_COPC_09)
3- DSO AACOPC06: source data for Unit Price workbook (PC_COPC_09)
4- Make sure that the master data C_ENERGY is fulfilled correctly (ELEC/KWH, GAS/KWH and STEAM/TO)
5- Be sure that the DSO ABCOPRIC is loaded (PC_COPC_BOM_PF1)
6- DSO ABCOPC16 : for the integration in Manufacturing (PC_COPC_MAN_COST)
7- DSO ABCOP06b : to load Manufacturing cost for SpP (PC_COPC_MAN_COST)
So we have 4 process chain :
PC_FIWC_02
PC_COPC_09
PC_COPC_BOM_PF1
PC_COPC_MAN_COST
Loading frequency
Average performance
| 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 |