Budget

→ Link to the detailed wiki user "DP - User Management#5.NOVECARE"

Budget Data

• Initial Sales Team Budget
• To build the budget, initial budget is provided, it corresponds to the copy of History and Last validated forecasts.

• Sales Team Budget
• It has to be registered in requested Month of Delivery at customer (ETA).

• Current year estimation & Budget preparation
• For the current year forecast, it should not be registered. It is automatically populated by the last validated forecast (Demand consensus) in the data field.
• Then, automatically, the Budget will be calculated in departure month Gross History (ETD) and Final Sales Team Budget  (ETD), which will be used by the Finance.

User models

List of the key user models to use in the Budget Process in Dynasys (for instance, to activate the exports, read only mode, etc.) → “Budget - Data Table”

• Budget

This user model takes into account all the important data fields, visible in the Budget Workspaces:

• Sales team budget ETA (Used by the Sales Rep. to validate the budget)
• Initial Sales team budget ETA (filled by the last validated forecast)
• Final forecast ETA
• Budget review ETD (Used by the S&OP planners)
• Gross history and Final Sales Team Budget (a calculation from the ETA to the ETD is performed)

• Budget Settings Data

The horizon has to be modified: Once it is done, the Budget data fields are modifiable.

• Budget Review Freeze

The DP Team has to check manually and block the year that will be impacted by the Budget Process for Year+1.

• Budget at CommercialProduct-ShiptoKA-Country@BU [CS]

This budget is sent by the Finance Department by quarter (not by month). However, The DP Team usually works on the Budget by DFU. So, the DP Team will:

• Mass upload the information sent by the Finance Department
• The data is automatically calculated by month (divided by 4)
• Then, it will be disaggregated at the DFU level. The disaggregation is done thanks to the coefficients (calculated automatically by Dynasys depending on the data that already exists for the statistical forecast) in the “Budget Upload Coefficient”.
  • For the item: The weight of each DFU in comparison to the historical data (historical percentage) is taken into account
  • For the horizon: The seasonality and the sales trend in comparison to the historical data is taken into account
    
    

Global Budget Process Overview

Detailed Budget Process

→ Link to the complete documentation

Budget Summary

• Horizon until 2022 + opened
• Open security 
• Add new workspace for Opportunities [xxNV02b - Similar to NV02 Budget]
• Add Class 0 in Budget Forcing Loop Calculation as for Class 1

• Initialize Budget by the Last Validated Forecast (From June, Y-1)

• Highlight the Budget Horizon for all DFUs (if possible)
  • Modification possible only within the horizon
  • Trick Y+1

• Rename "Initial Budget (ETA)" to "Initial Sales Team Budget (ETA)"
• Review documentation

Budget Initialization

• Specific process with new screens for Budget Preparation purpose
  • New workspace opened only during defined period (ex. 1st of July → End of July)
  • Initialization: Initialization from Final Sales Team Forecast (Raw Forecast + Sales Team Forecast)
  • Sales Rep. Input from the Sales Rep. in a dedicated line: "Working Budget" line at Ship-to KA Adjusted / Country / Commercial Product on a Monthly Basis
  • RMD Review: Review and follow-up of Sales Rep. input (same principle as Collaborative forecast)

• Extract to Finance / Adjustment out of Dynasys

• Final Budget Loaded in Dynasys
  • Specific cases to review: Prospects, New Materials to be covered