|Bookshelf Home | Contents | Index | PDF|
The forecast administrator has been told to create a number of different forecast series that the company will use for different sets of business requirements. He needs to create a forecast series and include search specifications, forecast dates, forecast participants or organizations, and the required aggregation levels. The aggregation levels specify the fields by which forecasts are aggregated and the hierarchy of aggregation.
The forecast administrator creates a number of different forecast series: a personal forecast series with details, a personal forecast series without details, a global forecast series, a departmental forecast series, a hybrid forecast series, and a partner forecast series.
Spreadsheet views help end users to better work with revenues and forecasts. Spreadsheet views are set up automatically in the default Siebel application so that end users can view revenue data for revenues and forecasts. To allow end users to access spreadsheet views with additional or different data such as revenue and best case or quantity or price, the administrator needs to configure these views.
Finally, the administrator sets up the forecast series dates to move ahead automatically, to make it easier for users when they need to create the same forecast month after month. Setting up the dates to move ahead means that end users do not have to manually change the dates each time they create a forecast using this forecast series.
NOTE: This scenario, and the examples used throughout this chapter, illustrates the function of Siebel Forecasting in various customer environments. Each forecast series described addresses a different approach to forecasting and a different set of business requirements. Usually, no single company would create every one of the different forecast series described herein.
|Siebel Forecasting Guide||Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.|