Authorization for Loading
Access grant:
- To BW - Production (WBP)
- To the transaction ZBW_SD_PC (role ZR_RCS_CA_M491 named “SD - Upload Forecast Budget – BFR”)
Loading Basic Requirements
The loading is done using an Excel file.
The BW transaction to be used is ZBW_SD_PC
Using this transaction, it is possible to enter new forecasts or update existing one and load data for both system : WP1 (Rhodia legacy) and PF1 (Solvay legacy).
Refer to the WIKI page :
https://wiki.solvay.com/display/TECHREP/Forecast#Forecast-HowtodownloadForecastfromBWsystem
Loading Frequency
Loading frequency using the BW transaction is up to the user.
Once data is loaded it is integrated in the Global Sales solution and in the CRM-analytics dashboard during the night job.
If you load several versions during the day only the last one will be loaded in BW during the night.
File Format for Loading
Description | Data Format | Mandatory / Optionnal | Remark |
Version | BUDGET, BFR03, BFR06, BFR09 | Mandatory – key for update | BUDGET=BFR12 |
ERP Source | PF1_020 (for PF1) WP1_400 (for RCS) NERP001 Chemplex NERP006 Itanbul Kimya | Mandatory – key for update | Global Sales does not contain other sources as in the P&L |
Year & Month of forecast | YYYYMM | Mandatory – key for update | |
BFC GBU | BFC format (2 digits), for example SD = Soda Ash | Mandatory – key for update | |
Legal Company code | 4 digits | Optional – key for update | Warning : it’s NOT the PRS code |
BFC Group of Activity | 5 digits | Optional | = BFC BU |
BFC Sub-activity | 4 digits | Optional | = BFC Market |
Sales Rep | Optional | ||
Ship-to Country | 2 digits | Optional | (1) See table below |
Ship-to Zone | Optional | (1) See table below | |
Ship-to KA | GRCL****** | Optional | (3) See table below |
Ship-to code | 10 digits max : 1234567890 | Optional | (1) See table below |
Distribution Channel | Optional | ||
Product Hierarchy/LIP03 | Product line level 3 for RCS (LIP003) Product hierarchy for PF1 (example MHE) | Optional | (2) See table below |
Product | Commercial product for RCS (example 90031318) Material group for PF1 (example Z10-12791) | Optional | (2) See table below |
Material Code | Should exist in Material master data | Optional | (2) See table below |
Unit Quantity | KG | Mandatory | Only KG could be loaded |
Financial Forecast Quantity | without decimal places | Mandatory | |
Currency code | EUR | Mandatory | Only EUR could be loaded |
Financial Forecast Sales | without decimal places | Mandatory | |
Financial Forecast Contrib | without decimal places | Mandatory | |
Enterprise Segment | 10 char | Optional | |
Sold to | 10 digits max : 1234567890 | Optional | Available since end of January 2021 |
Transformation Rules from Files to BW Reports
(1) | Regarding the customer axis, you can enter your forecasts with the detail - by GBU zone (if no country, no ship to) or - by country (if no ship to, no GBU zone) - in this case, GBU zone is derived or - by ship to (if no country, no GBU zone) - in this case, country and GBU zone are derived - if material code is given, KA can be also derived |
(2) | Regarding the material axis , you can enter your forecasts with the detail - by product-hierarchy/LIP03 (if no material) or - by commercial-product/material-group (if no material) or - by material (if no Hierachy/LIP03, and if no product/mat-group) - in this case, Heirachy/LIP03, and product/mat-group are derived |
(3) | Regarding the customer/material axis , you can enter your forecasts with the detail - by KA (if no material and no ship to) if only the material, or only the ship to, or none of them, you can enter the KA |
Other | Other data are not depending on each-other : Group of activity, sub-activity, sales-rep, DC Budget & BFR forecast can't be loaded by ship to GEO-zone |
One file contain data for ONE GBU only.
When you assign your XLS file in the transaction to be loaded in BW, your XLS file should be CLOSED.
Warning : the file name is limited in number of characters and should not be too long.
Your XLS file should contain headers on the first line (warning : mandatory, because the first line is never loaded in the system).
You can load more than one file by day.
As already indicated, the key for data replacement in BW is “Version/GBU/Month/Legal-Entity”.
- If you load more than one file on the same day, with the same key “Version/GBU/Month/Legal-Entity”, the last one will be the last saved, and will replace previous forecasts previously loaded.
- If you load more than one file on the same day, with different keys “Version/GBU/Month/Legal-Entity”, all of them will be saved in BW.
Load Forecast into BW
1- Access the program via transaction code ZBW_SD_PC
2- Inform GBU / Year / Version and select the forecast file on your PC, which has to be excel and with correct format.
Warning : the selected XLS file should be closed to be loaded into BW.
3- Click on Preview in order to check the authorization (for GBU) and data control (all data should exist in the global BW master data).
4- Click on Check File to get the summary of the data correction.
If data is incorrect, it will tell how many error and what line is incorrect on the file. Correct the file and try step 2 again.
ERROR explanation is indicated on the right part of the line :
- If data is OK, the Load File button will be available
-5- Click on Load File, it will save the data into BW system.