...

Energy Forecast prices are collected in a BW-IP workbook and then used integrated in Manufacturing VC query to calculate the Energy cost for projected months.

...

Dataflow overview

Link to dataflow overview

...

diagram:

https://app.diagrams.net/#G1RLCMm5yN06FOmvBvRN5HOSCk1xwCFtvl

There are 2 workbooks concerning Energy Forecast:

Image Added

The first one (Workbook "FL - Energy Forecast")is common for Novecare and SpP and is used to save Energy forecast prices entered price typed by the users

Image Removed

The workbook is assigned to query BW_QRY_ALCOPC14_0001, which is built on Aggregation Level ALCOPC14.

. This is done by plant/activitiy (ELEC, GAS, STEAM, etc)

Energy unit price is Energy prices are stored in DSO ABCOPC10.

Image Removed

The data flow starts from the BOM.

Image Added

GBU Novecare

We get the latest Actual price (current month M) from the BOM, For Novecare, we get the last Actual price for each plant/activity (commodity), 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

Image Added

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 (by activity type). So we load from the BOM only the plants, then the activities (commodities) are "artificially" created in BW from this list (the values in master data C_ENERGY)

Image Removed

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

Image Removed

Link to documents

https://app.diagrams.net/#G1RLCMm5yN06FOmvBvRN5HOSCk1xwCFtvl

, and then the user can 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)

Image Added

As for SpP, there is no detail coming from SAP for "Utilities" (just an aggregated cost), there is 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.

Actually this is where the Energy Forecast process starts for SpP.

Image Added

1) Calculation View : CV_FMCO_ENERGY_SP_FORE_UF

Image Added

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', 'GAS', 'STEAM', '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

Image Added

This will be loaded into ABCOPC16, where the increase percentage (K_STDINCR) is calculated (comparing current month x previous month).

Then ABCOPC16 is used in following CV

3) Calculation View : CV_FMCO_ENERGY_SP_FORE_UF_CALC

Image Added

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:

Functional and Technical rules on Workbench + Reporting

...

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

...