...
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 unit price is stored in DSO ABCOPC10.
For
GBU Novecare
We , 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.
Energy Automation
A change was requested to improve the process for Novecare (and other WP1 GBUs like TS and PA).
As the prices sent by Corporate are not reflecting the same process used by plant controllers, it has been decided to implement a % increase to standard cost instead.
A formula will automatically calculate the % trend of the unit price between each month in the workbook.
Example of the calculation:
https://docs.google.com/spreadsheets/d/1F8YPA5tVAw-hieDyODLhQwQNnKJOt-vxsoe3ezu4gGU/edit#gid=0
So the prices saved by Corporate in the workbook are stored in ABCOPC10.
And a new DSO ABCOPC19 is loaded from ABCOPC10, and the % increase calculation is applied in TRF below
Then ABCOPC19 is integrated in CV_FMCO_MAN_COST_RCS.
No more lag is applied, meaning the Forecast for month M takes directly the price from month M, Forecast for M+1 takes the price from M+1, etc.
GBU SP
There 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 then input the prices.
Currently the only activities loaded in the Unit price workbook for GBU SP are ELEC, GAS, STEAM.
This is filtered in CV_FMCO_ENERGY_SP_FORE_UF into AACOPC06 (used as lookup in TRSF: APCOPC06 -> ADSO ABCOPC11)
As for SpP, there is no detail coming from SAP for "Utilities" (just an aggregated cost)For SpP, there is a this 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.
...
1) Calculation View : CV_FMCO_ENERGY_SP_FORE_UF
This calculation view will generate all the combinations Plant/H4/Prod.Hierarchy/Activity to be loaded in ABCOPC15.
...
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_ENERGY_SP_FORE_UF2
This will be loaded into ABCOPC16, where the increase percentage (K_STDINCR) is calculated (comparing current month x previous month).
Integrating Energy Cost in the Manufacturing CV for Novecare
Then ABCOPC16 is used in following CV
3) Calculation View : In CV_FMCO_ENERGY_MANSP_FORE_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)
UF_CALC
Then this CV is used in the following one:
4) Calculation View : CV_FMCO_MAN_COST_SPP_AVERAGE
Which is used in TRSF: DTS_CV_FMCO_MAN_COST_SPP_AVR WBD_HANAIV -> ABCOP06B
Link to project folder:
...