Activity Description for Generate Baseline
Explanation
A planning baseline can be generated from two locations within the Business Planning module:
- Planning Unit page: Select one or multiple time series (a combination of ordinary
code parts) and use the Generate Baseline command. This method is typically used when planning
for a specific combination of planning dimensions for the first time.
- Planning Units page: Select one or multiple units and use the Generate
Baseline command. This approach is suitable for generating a baseline for several time series covered in
a range of accounts. Note that only valid planning unit versions will be considered.
- Business Planning Baseline page: Select one or multiple time series and use the
Generate Baseline command. This option allows users to select only the required time series.
Note that only valid planning unit versions will be considered.
Prerequisites
- The individual must be assigned as an Administrator or Planner for the
planning unit.
- Historical actuals must be available in the General Ledger or Internal
Ledger for the selected time range.
- Code string combinations should be the same across planning companies when actuals are derived from a
different company than the planning company.
- Planning entities should be defined along with the Company Connection on the
General Planning Basic Data /Planning Entities page to import balances from a different
company.
- The planning unit must be in Open state.
System Effects
Upon completion of the assistant from any of the three locations, historical balances (minimum of 24 periods)
from the selected ledger and optionally from selected business plans are processed using various forecasting
models. The system automatically selects the most appropriate model to generate the baseline.
The resulting baseline is stored in the Business Plan Baseline transaction source.
Manual planning transactions can be created during or after the baseline generation process. This posts the
difference between the generated baseline and all non-manual transactions for the code part combination to a manual
transaction row.
Note: If manual planning transaction rows already exist for the period, the system replaces
them.