Setting Up Forecasting

This chapter contains information about setting up Siebel Forecasting. It includes the procedures that an administrator must perform to create a forecast series, and it discusses the different types of forecast series.

This chapter includes the following topics:

About Forecast Series

A forecast series defines the rules for forecasting in Siebel Forecasting. Typically, a forecast series involves a unique group of individuals with some unique set of forecasting requirements.

The following example illustrates the concepts involved in the forecast series.

At company XYZ, the sales organization consists of district managers who forecast aggregate revenues once a week. The sales managers and executives have requested that each sales representative list their opportunities and provide a committed total that can equal, or not equal, the sum total of the opportunities that they have listed.

The manufacturing organization at this same company wants a monthly snapshot of what is in the pipeline, at a product line level, without allowing sales representatives or sales management to make adjustments. They want to see how the forecast changes from month to month, and want access to historical information on earlier months’ forecasts.

In this situation, the administrator can set up two separate forecast series: one series for the sales representatives and the other for manufacturing. The sales forecast series has a weekly frequency, with every sales representative as a participant, and a search specification that finds only opportunity revenue records. The manufacturing forecast series has a monthly frequency, an administrator or manufacturing manager as the participant, and a search specification that finds just product specific revenue records.

In general, a small number of forecast series is better than a large number of forecast series. It is easier to maintain and explain just two or three forecast series rather than 10 or 12. In the preceding example, the administrator would not want manufacturing product managers and sales managers both creating forecasts in the same series because they would end up double-counting the revenues involved. (The product managers would count an opportunity once as a set of products. The sales representatives would end up counting that opportunity twice.)

Note: If you think you will end up double-counting, if your company has groups with fairly different requirements, or if you have overlays, consider adding additional forecast series.

Scenario for Setting Up Forecasting

This scenario gives one example of how to set up forecasting. You can set up forecasting differently, depending on your business model.

The forecast administrator is told to create a number of different forecast series that the company will use for different sets of business requirements. The forecast administrator 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 users to better work with revenues and forecasts. Spreadsheet views are set up automatically in the default Siebel application so that users can view revenue data for revenues and forecasts. To allow 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 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.

Creating a Forecast Series

The following procedure describes how to create a forecast series.

To create a forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.

In the More Info form, create a new record and complete the necessary fields. Some fields are described in the following table.

Field Name	Description
Series Name	Typically gives some insight as to how the forecast series is used, what the forecast series includes, or how often it is run.
Detail Depth	Determines whether the user’s forecast details are included in the manager’s forecast (Revenue Detail, or Standard) or summarized in a set total (Summary Only). The default value for this field, Summary Only, is the recommended setting for most customers.
Visibility	The visibility mode applied to the Revenue table in the selection of forecast records. Choices are: My Revenues My Team’s Revenues All Revenues All Revenues Across Organizations My Revenues - Indirect Sales The default value for this field is My Revenues.
Interval Period Type	The type of forecast interval period. Choices are: Day, Week, Month, Quarter, and Year. The default type is Month.
Interval	Determines the time between creation of new forecasts of a given series. The value is a number of units of the Interval Period Type. For example, for the default interval value 1, and the default interval period type, forecasts are created monthly.
Summary Period Type	Determines the summary periods into which revenues are aggregated for each forecast in this series. The choices are based on the period types defined and can include periods from a day to a year. The default type is Month, meaning that the Forecast Summary view shows monthly totals. For more information about summary periods, see Viewing the Forecast Summary.
Active	Indicates whether the forecast series is available for forecasting purposes to anyone listed in the Forecast Series Participants list on the dates indicated on the Forecast Series Dates list. By default, this box is selected.
Public Access	Read-only. When selected, allows each employee within the selected organization to access the forecast series and create a forecast. It is only selected when an organization is added. For more information about adding an organization, see Adding Forecast Series Organizations.
Auto Forecast Search Spec	Determines which revenue items are automatically included when a forecast is created. If a query is not specified here, then the sales representative’s revenue records, within the applicable date range, are included in the forecast. For more information, see Creating Search Specifications for Forecast Series.
Associate Search Spec	The filter that is applied to the Add New Records list on the Forecast Details view. This field determines which revenue items the user can manually add to a forecast. For more information, see Creating Search Specifications for Forecast Series.
Rollup Search Spec	Indicates which detail records are included in the forecast summary amounts. The Rollup Search Spec can vary from one forecast series to another, and can be based on revenue type, revenue class, probability, or any other field on the forecast detail record. Note: The Rollup Search Spec is based on fields from the Forecast 2000 -- Forecast Item Detail Flat business component, not Revenue.

Add dates.
You must define the dates required for the forecast.
For instructions, see Defining Forecast Series Dates.
Add participants or organizations.
You must either define participants or organizations, which provide a useful means of creating forecast series for a large group of participants.
For more information, see Adding Forecast Series Participants, and Adding Forecast Series Organizations.
Add the required aggregation levels.
You can set aggregation fields and aggregation levels for Accounts, Products, and Product Line fields. You can also use custom fields if you require fields specific to your business requirements.
For instructions, see Adding Aggregation Levels.

Forecast Visibility

The following table describes the different forecast visibility modes.

Visibility	Description
My Revenues	This mode allows the forecast access only to records assigned to the sales representative who owns the revenues that are included in the forecast. My Revenues is used for standard forecasts.
My Team’s Revenues	This mode allows the forecast access to each revenue record attributed to the user’s subordinates. This mode is recommended for departmental or group forecasts in which a manager wants a snapshot of the revenues attributed to their department or group. Use caution when using the My Team’s Revenues setting; limit the number of participants to only one level of the forecast tree (that is, only directors or only VPs or only first level managers). If a manager and a subordinate are both listed as participants in a forecast series with this setting, the subordinate’s revenue records are counted at least twice: once at the subordinate level and then a second time at the manager’s level, and so on up the tree for every level in which there is a participant listed. For more information about creating a departmental forecast series, see Creating a Departmental Forecast Series.
All Revenues	This mode allows the forecast access to each revenue record within the organization. This mode is recommended for organizational snapshots, in which just one person (typically an administrator) creates one forecast with a snapshot of each forecastable revenue record within that organization.
All Revenues Across Organizations	This mode allows the forecast access to each revenue record in the Siebel database, across all organizations. This mode is recommended for global snapshots, in which just one person (typically an administrator) creates one forecast with a snapshot of each forecastable revenue record within the Siebel database. For more information about creating global snapshots, see Creating a Global Forecast Series.
My Revenues - Indirect Sales	This mode allows the administrator to define a forecast-specific hierarchy; that is, define which participants will submit their forecasts to which manager. The forecast-specific hierarchy may or may not match the Siebel Position Based Reporting Hierarchy. Use this m ode only if the reporting hierarchy for a forecast series is different from the position based reporting hierarchy. For more information about defining a forecast-specific hierarchy, see Setting Up Customer Adaptive Forecasting.

Note: A hybrid forecast uses My Revenues and My Team’s Revenues simultaneously by adjusting the Visibility field in the Forecast Series Participants view. For more information about hybrid forecasts, see Creating a Hybrid Forecast Series.

Creating Search Specifications for Forecast Series

The Auto Forecast Search Spec determines which revenue line items are automatically included in the forecast when it is created.

The Associate Search Spec determines which revenue line items can be manually added to the forecast by the sales representative after the forecast is created.

The Auto Forecast Search Spec and the Associate Search Spec can vary from one forecast series to another, and can be based on revenue type, revenue class, probability, or any other field on the revenue record. The user sees the results of the Associate Search Spec displayed as a list of records in the Add New Records pop-up on the Forecast Details form.

The Auto Forecast Search Spec uses the same syntax and grammar that the Associated Search Spec uses. However, it is usually more restrictive in scope. For example, you can create a forecast series with the following search specifications:

Associate Search Spec: [Revenue Type] = 'Shipped' or [Revenue Type] = 'Booked'

Auto Forecast Search Spec: ([Revenue Type] = 'Shipped' or [Revenue Type] = 'Booked') 
and [Committed] = 'Y'

In this example, the user can manually copy into the forecast any revenue record with a Revenue Type of Shipped or Booked, whether it is committed or not. However, the automatically included forecast details only include revenue records that were actually marked as committed.

As in this example, typically the Associate Search Spec is slightly less restrictive than the Auto Forecast Search Spec, allowing users to copy into their forecast some revenue records that did not meet the more restrictive Auto Forecast Search Spec criteria.

The Rollup Search Spec determines which detail records are included in the forecast summary.

The Rollup Search Spec can vary from one forecast series to another, and can be based on revenue type, revenue class, probability, or any other field on the forecast detail record.

Rollup Search Spec is used in scenarios where the History View Date and History Edit Date fields are specified in the dates for the forecast series. If when rolling up the forecasted revenue, the user wants to include only those revenues having a close date between the specified Start Date and End Date of the forecast series, the administrator must define the following Rollup Search Spec:

([Detail Date] >= "&FCST_START_DATE" and [Detail Date] <= "&FCST_END_DATE")

The following table shows some common search specifications.

Search Specification	Description
[Committed] = 'Y'	Allows the user to add committed revenue records.
[Committed] = 'Y' and ([Revenue Type] = 'Shipped' or [Revenue Type] = 'Booked')	Allows the user to add committed revenue records with Revenue Types of Shipped or Booked.
[Calculated Primary Flag] = 'Y'	Allows the user to add only primary revenue records into the forecast. Each opportunity has one primary revenue record associated with it. The primary revenue line includes the revenue amount for the opportunity as a whole. The opportunity can have other revenue records, but those line items have [Calculated Primary Flag] set to null or ‘N’.
[Partner] is NULL	Allows the user to manually add revenue records in which the Partner field is null.
[Product] is NULL	Allows the user to manually add revenue records in which the Product field is null.

Note: Test the search specification before deploying the forecast. To test the search spec, navigate to the Revenues screen and create a new query. Type or paste the exact search specification into the Description field in the query and then run the query to see if it delivers the correct results.

Defining Forecast Series Dates

Forecast series dates determine when each forecast of that series occurs. Create a record in the Forecast Series Dates view for each date a forecast is to be run in that series. Forecasts typically occur according to a set pattern or frequency (for example: weekly, monthly, or quarterly) determined by the Interval and Interval Period Type fields in the Forecast Series form, and include some range of revenue records (for example, January 1 through June 30).

Forecasts can be static, with the user almost always seeing the same range of dates, or rolling, with the user seeing the effective date range for the forecast move each week or month. Typically, forecasts within a series involve some set amount of time, covering a range of six months or one year.

The forecast Start Date, End Date, History View Date, and History Edit Date are established using entries in the Siebel Periods table (see About Using the Periods Table in Forecasting). While the Start Date and End Date provide the range of dates for active (future) forecasting, the History View Date and History Edit Date provide the range of dates for historical forecasting. The historical information allows the user to spot trends in opportunity, account, or product-related revenues when creating a forecast.

The Archive Date is the date on which a forecast is deemed to be completed and ready for archival in the data warehouse.

To define dates for a forecast series, complete the steps in the following procedure.

To define dates for a forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
In the Forecast Series list, select the forecast series for which you want to define dates.
Click the Forecast Series Dates tab.

In the Forecast Series Dates list, add a new record and complete the necessary fields. Some fields are described in the following table.

Field Name	Description
Forecast Date	The date for which the forecast is created. Typically, this is the beginning or end of some logical period. Some organizations forecast on the first of every month. Other organizations forecast at the end of each week.
Start Date	The beginning of the date range for a selected forecast. This is the first date for which Siebel Forecasting pulls revenue records into the forecast.
End Date	The end of the date range for a selected forecast. The last date for which revenues are pulled into the forecast.
History View Date	The first date for which forecast information appears in the forecast. The periods between this date and the History Edit Date are read-only. This allows users to view their earlier month’s performance when creating a new forecast.
History Edit Date	The first date for which forecast information is editable. Typically, the History Edit Date occurs a period or two before the Forecast Start Date. This allows a user to fill in actual revenue from the earlier period during the current forecast.
Archive Date	The date on which to freeze a forecast snapshot completely so that the forecast: Cannot be changed at all after this date Can be pulled into the Oracle Business Intelligence data warehouse In this way, data warehouse reports remain consistent over time. Once a forecast passes its archive date, the forecast is not editable or usable, and the archive date is not editable either.

Note: When you change the value in the Start Date field, the value in the End Date field is updated automatically. However, when you change the value in the End Date field, the value in the Start Date field remains the same.

Tip: To produce multiple forecast start dates, you can copy the first record or click Add Next Date and it automatically moves the forecast date forward according to the defined interval. This only applies if it is set up as such by the Siebel administrator. For information on setting this up, see Deactivating Auto-Forecast.

Adding Forecast Series Participants

The Forecast Series Participants view lists the employees who will participate in the forecast series. Where the visibility of a forecast series is set to My Revenues - Indirect Sales, the Forecast Series Participants view gives you the option of defining a forecast-specific hierarchy for each participant in the forecast. The participant determines:

Whether an employee can create a forecast within a given series
The list of individuals for whom an auto-forecast is created when a manager creates a forecast

Although the Forecast Series Participants view appears person-based, it is actually position-based. As employees move from one job to another, Siebel Forecasting maintains the correct participant links.

Adding Participants to a Forecast Series

To add participants to a forecast series, complete the steps in the following procedure.

To add participants to a forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
In the Forecast Series list, select a forecast series.
Go to the Forecast Series Participants tab.
Click Add to a new record, as follows:
1. In the Add Participants dialog box that opens, select the required participants.
2. Click OK to add the new participants to the Forecast Series Participants list.
Note: By default, according to the position hierarchy, all participants in a forecast series report their forecasts to their manager; that is, unless a forecast-specific hierarchy is defined for participants in the forecast, as described in the following procedure.

Defining a Forecast-Specific Hierarchy For Participants in a Forecast Series

To define a forecast-specific hierarchy for participants in a forecast series, complete the steps in the following procedure.

To define a forecast-specific hierarchy for participants in a forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
In the Forecast Series list, select a forecast series.
Go to the Forecast Series Participants tab, and define a forecast-specific hierarchy for participants in the forecast series, as follows:
- For each participant in the forecast series, specify a different Submit To position.
  
  Note: A forecast-specific hierarchy can only be defined for participants in a forecast series when the visibility for that forecast series is set to My Revenues - Indirect Sales.

For more information about defining a forecast-specific hierarchy for a forecast series, see Setting Up Customer Adaptive Forecasting.

Adding Forecast Series Organizations

The Forecast Series Organizations view lists the organizations who will participate in the forecast series. It is useful when you are creating a forecast for a large set of participants. Like the Forecast Series Participants view, the organization determines whether an employee can create a forecast within a given series.

To add an organization to a series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
In the Forecast Series list, select a forecast series.
Click the Forecast Series Organizations tab and add a new record.
In the Add Organization dialog box, select the organization you want to add, and then click OK.
The new organization is added to the Forecast Series Organizations list. Note that the forecast series’ Public Access check box is now selected.

Note: Organization-defined forecasts do not use auto-forecast as this can cause confusion in very large organizations. Because auto-forecast is not enabled for organization-defined forecasts, make sure that your forecast series process allows users to create their own forecasts, or managers create and add absentee forecasts when appropriate.

Adding Aggregation Levels

The Aggregation view lists the revenue fields and aggregation levels that are used in the Summary view of a forecast. These aggregation levels are used to break down a forecast according to business requirements. For example, you can break down revenue figures by Account by Product Line by Product.

For each field, you specify a level of aggregation in the hierarchy. Level 1 represents the highest level of aggregation, level 2 the next highest level, and so on. For example, to aggregate revenues by Account by Product Line by Product you define aggregation levels as shown in the following table:

Field	Level
Account	1
Product Line	2
Product	3

In the Forecast Summary view, the fields are displayed from first to last according to the defined aggregation level. The Date field is considered to be at level 0 and is always the first column. So for the example shown in the previous table, the columns from first to last would be Date, Account, Product Line, and Product, corresponding to levels 0, 1, 2, and 3 respectively.

There is no limit on the number of aggregation levels that you can define. However, only six levels are available for the preconfigured applications. For help with adding more levels, create a service request (SR) on My Oracle Support. Alternatively, you can phone Oracle Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support.

Caution: The higher the number of aggregation levels, the greater the impact on performance.

You can add new revenue fields as required, as described in Adding a Custom Field for Aggregation.

To add aggregation levels to a forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
In the Forecast Series list, select a forecast series.

Click the Aggregation tab and add a new record by completing the fields shown in the following table:

Field	Description
Field	The aggregation field.
Level	The aggregation level for the field.
Field Description	A description of the field and aggregation level.
Mapped Field	The field of the Forecast Item Detail business component to which the value in the Field column is mapped.

Click OK. The new aggregation levels are added.

Adding a Custom Field for Aggregation

You can add a custom field, such as Global Business Unit or Fulfillment, for use in the Aggregation view. To do so, you must first add the custom fields as a column in the S_REVN table, add the field to the Revenue business component, and add appropriate columns to the appropriate applets. You must then add the field to the appropriate LOV (Type FCST_AGGR_FLD) so that it is available in the Administration - Forecast Aggregation view.

For more information about the relevant business components and adding custom fields to the forecasting process, see Forecasting User Properties

To add a custom revenue field

Start Siebel Tools.
Select the S_REVN Table.

Create a column for the custom field (for example, for the Global Business Unit field), and complete the fields as shown in the following table:

Field	Value
Name	X_GLOBAL_BUSINESS_UNIT
User Name	Global Business Unit Ext
Physical Type	Varchar
Length	15

Click Apply/DDL to save the changes to the S_REVN table.

Lock the Project Symbolic Strings.

Click on Symbolic Strings and create a Symbolic String with the same names as used in the column in the S_REVN table. For example, for the Global Business Unit field.

Field	Value
Name	X_GLOBAL_BUSINESS_UNIT
User Name	Global Business Unit Ext
Physical Type	Varchar
Length	15

Select the Revenue business component.
Click Fields and create a new field, for example, Global Business Unit.
Select Applets and query on the appropriate applet, for example, Opportunity Revenue Schedule List applet.
Click Lists and create a new list column, for example, Global Business Unit.
Select the applet to which you added the field, for example, Opportunity Revenue Schedule List applet.
Right-click the applet and select Edit Web Layout.
Select Mode: 2: Edit List.
Select the custom field (for example, Global Business Unit) in the Columns/Controls template; select it and move it into Applets Web Template (Edit) - Layout.
Save the changes and submit the changes to the Siebel runtime repository.

To add a field to an LOV, complete the steps in the following procedure.

To add a custom field to the aggregation LOV

Navigate to Administration - Data screen, then List of Values view.
Click New to create a new record, and then enter the list-of-values type FCST_AGGR_FLD in the Type field.
Enter the name of the custom field in the Display Value field.
Save the record.

Moving Forecast Dates Ahead Automatically

In the Administration, then the Forecast screen, when you create a new forecast series, the start and end dates, as well as history and edit dates, can be set up to move ahead automatically.

Modify the value of the user property Auto-Set Start/End Dates in the business component, Forecast 2000 - Forecast Series Date. The values of the Auto-Set Start/End Dates user property are shown in the following table.

Value	Description
Y	Copying the forecast sets the start and end dates so that the first period within the interval encompasses the forecast date and the interval is the same length.
N	Copying the forecast does not preset the start and end dates. They remain the same as the original that was copied. This is the default setting for this user property.

For a list of the user properties associated with forecasting, see Forecasting User Properties

About Copying a Forecast Series

You can copy a forecast series, including the forecast dates and forecast participants defined for the forecast series, by selecting Menu, then Copy Record from the Administration - Forecast screen.

Types of Forecast Series

You can create different types of forecast series, including the following:

Creating a Personal Forecast Series with Details
Creating a Personal Forecast Series without Details
Creating a Standard Personal Forecast Series
Creating a Global Forecast Series
Creating a Departmental Forecast Series
Creating a Hybrid Forecast Series
A forecast-specific forecast series where the forecast visibility is My Revenues - Indirect Sales. For more information, see Setting Up Customer Adaptive Forecasting
A partner forecast series. For more information, see About Creating a Partner Forecast Series

Creating a Personal Forecast Series with Details

The personal forecast with details assumes that sales representatives and their managers want to participate in the forecasting process. After a personal forecast is created, other managers are allowed to adjust the forecast. The personal forecast with details is an example of a rollup forecast.

The personal forecast with details:

Is hierarchical and structured, allowing visibility to an entire organization’s forecast efforts
Rolls up from the lowest to the highest level of an organization, one level at a time
Allows sales representatives, sales managers, and their subordinates to create their own forecasts

Use the personal forecast with details if:

Your company has a small number of opportunities with high revenue potential
Managers are involved with every aspect of the opportunities and want the ability to change a forecast’s line items
You want to be able to view several forecasting perspectives

Do not use the personal forecast with details if:

Management is not interested in an opportunity’s specific details
The amount of work involved with creating the forecast has no real advantage

The following image shows an example as follows:

A sales representative creates a forecast for an opportunity that is predicted to be worth $1 million dollars and will close in January.
The sales representative’s manager can review the forecast, and change the value of the opportunity and the closing date.
The manager’s manager can review the forecast and make additional changes. See the following figure for an illustrated example of this process.

Example of a Forecast Process: This image is described in the surrounding text.

To create a personal forecast series with details

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series as described in Creating a Forecast Series.
In the new forecast series, from the Detail Depth drop-down list, select Revenue Detail.
This causes the user’s forecast detail records to be copied into their manager’s forecast without being summarized.
From the Visibility field, select My Revenues.
This limits the user’s forecast to their own revenue records.
Click the Forecast Series Dates tab and add forecast dates.
For information about adding dates, see Defining Forecast Series Dates.
Click the Forecast Series Participants tab and add the appropriate users.
Alternatively, click the Forecast Series Organizations tab and add the appropriate organization.
For information about adding participants, see Adding Forecast Series Participants. For information about adding organizations, see Adding Forecast Series Organizations.
Click the Aggregation tab and add the required aggregation levels.
For information about adding aggregation levels, see Adding Aggregation Levels.

Creating a Personal Forecast Series without Details

The personal forecast without details allows sales representatives and managers to participate in the forecasting process. The personal forecast without details is an example of a rollup forecast.

The personal forecast without details offers a compromise between the global forecast and the personal forecast with details. It is faster than the personal forecast with details, while allowing less intervention and adjustment.

The personal forecast without details:

Rolls up from the lowest to the highest level of an organization, one level at a time
Automatically creates missing subordinate forecasts when the manager forecasts
Summarizes subordinates’ forecast information for the manager
Allows a manager to prorate a user’s contribution to the manager’s forecast totals
Provides the manager with forecast details for subordinates only when they drill down into the subordinate’s forecast record

Sales managers are not always concerned about the details; they are primarily interested in the revenue potential of each subordinate.

Like the personal forecast with details, the personal forecast without details has many participants, each of whom must create a forecast or have one created for them. In large organizations, this approach to forecasting can take a long time, as each level of the reporting structure needs some time to create, review, and adjust their forecasts.

Note: Personal forecasts tend to have fairly high maintenance requirements. Although the participant lists are position-based, they still require updating as positions are added or removed from the Siebel application.

Use the personal forecast without details if:

Managers will only adjust the total revenues, and not the sales representative’s forecast details
There are many opportunities, with fairly low revenue amounts
Managers want the forecast summaries rolled up on a monthly basis

Do not use the personal forecast without details if:

Managers need to be more involved with opportunities
Managers need to adjust the details without the user’s knowledge

Because the managers do not have access to the details, they cannot change the details. Managers can only add a subordinate’s contribution to their forecast. Forecast details are revenue line items, and there is a forecast summary that is rolled up monthly.

Example: Company XYZ closes a large number of opportunities each quarter. Each opportunity has a small dollar value. The managers are rarely involved in these opportunities, and would prefer summary level information to seeing every detail. The manager and the sales representative review the Revenues list view on a regular basis and make their changes directly in that view. The managers want to see, for each of their subordinates, a monthly commit number that is somewhat arbitrary and not always based on the user’s forecastable revenues for that forecast period.

To create a personal forecast series without details

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series.
For information, see Creating a Forecast Series.
In the new forecast series, from the Detail Depth drop-down list, select Summary Only.
This causes the user’s forecast detail records to be summarized in the manager’s forecast.
From the Visibility drop-down list, select My Revenues.
This restricts the user’s forecast to their own revenue records.
Click the Forecast Series Dates tab and add forecast dates.
For information about adding dates, see Defining Forecast Series Dates.
Click the Forecast Series Participants tab and add the appropriate users.
Alternatively, click the Forecast Series Organizations tab and add the appropriate organization.
For information about adding participants, see Adding Forecast Series Participants. For information about adding organizations, see Adding Forecast Series Organizations.
Click the Aggregation tab and add the required aggregation levels.
For information about adding aggregation levels, see Adding Aggregation Levels.

Creating a Standard Personal Forecast Series

The standard personal forecast series combines the features of the personal forecast with details (Revenue Details) and the personal forecast without details (Summary Only) to provide the manager with a detailed view of all subordinate forecasts, including a roll up of any adjustments made from the summary view. The standard personal forecast is an example of a rollup forecast.

The standard personal forecast series:

Is hierarchical and structured, allowing visibility to an entire organization’s forecast efforts
Rolls up from the lowest to the highest level of an organization, one level at a time
Eliminates the need of creating multiple forecast series
Shows a summarized as well as a detailed view of subordinate forecasts
Allows sales representatives and managers to make revenue adjustments in the Summary view only

Use the standard personal forecast series if:

You want to be able to review several forecasting perspectives
Managers need to be able to obtain a detailed view of revenue opportunities from subordinates and at the same time make adjustments to aggregated forecasts from the Summary view before submission

Do not use the standard personal forecast series if:

Management is not interested in an opportunity’s specific details
The volume of records for each forecast is high
Sales representatives, managers, and their subordinates need to be able to adjust their forecasted revenue from the Details view of forecasts

Example: Sales representatives and managers who participate in the forecasting process typically need to see details of the revenue projection over a period of time, line by line, as well as the aggregated revenue in the summary view where they can make appropriate adjustments and roll up to management as required.

To create a standard personal forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series.
For information, see Creating a Forecast Series.
In the new forecast series, from the Detail Depth drop-down list, select Standard.
This provides the manager with a detailed view of all subordinate forecasts, and enables adjustments to be made from the summary view.
From the Visibility drop-down list, select My Revenues.
This restricts the user’s forecast to their own revenue records.
Define an Auto Forecast Search Spec.
For information about defining a search specification for the forecast, see Creating Search Specifications for Forecast Series.
Click the Forecast Series Dates tab and add forecast dates.
For information about adding dates, see Defining Forecast Series Dates.
Click the Forecast Series Participants tab and add the appropriate users.
Alternatively, click the Forecast Series Organizations tab and add the appropriate organization. Then, select the name (or position) of the sales representatives and sales managers that need to participate in the forecast.

For information about adding participants, see Adding Forecast Series Participants. For information about adding organizations, see Adding Forecast Series Organizations.

Note: Sales representatives and sales managers have opportunity revenue records.
Click the Aggregation tab and add the required aggregation levels.
For information about adding aggregation levels, see Adding Aggregation Levels.

Creating a Global Forecast Series

The global forecast allows a user to take a snapshot of the corporate revenues that qualify for forecasting. Organizations using the global forecasting approach place a high level of emphasis on the Revenues screen, and a low level of emphasis on the Forecasting views. The global forecast is an example of a corporate snapshot type of forecast.

The global forecast:

Allows an individual user to take a snapshot of corporate revenues
Does not require user or management intervention
Captures the revenue that meets the forecast series criteria, including partner and third-party related revenues
Avoids a lengthy and involved adjustment process as forecasts are rolled from manager to manager to executive

Sales managers and executives review revenues in real time using queries in the My Team’s Revenues view. Using this view, sales managers conduct their weekly or monthly one-on-one meetings with their account managers or sales representatives, before the global forecast.

The sales manager, along with the sales representative, adjusts the revenues, close dates, win probabilities, and commit statuses in the Revenues view so that the sales representative and the manager have a single consensus opinion on the revenue items that end up in the forecast. They finish this process before the deadline of the corporate forecast.

As administrator, you create the forecast and make it available to high-level managers and executives from the All Forecasts view.

Use global forecasts if:

Your sales representative is likely to have the most accurate perspective on the value of an opportunity, account, partner, project, or product line over time
The manager is unlikely to adjust the sales representative’s forecast, or if the manager is able to adjust the sales representative’s projected revenues before the creation of the corporate forecast
You want to reduce the amount of overhead and time spent in forecasting

Do not use global forecasts if:

The manager wants the opportunity to adjust revenues without the sales representative’s knowledge
It is important for sales representatives to actually visit the forecast form and submit their forecasts to a manager
Sales representatives must make a revenue commitment that is different from the sum of the revenue line items they are tracking in the Siebel product

To create a global forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series.
For information, see Creating a Forecast Series.
From the Visibility drop-down list, select All or All Across Organizations.
This causes the manager’s view to include each of the subordinates’ revenue records.
Click the Forecast Series Dates tab and add forecast dates.
For information about adding dates, see Defining Forecast Series Dates.
Click the Forecast Series Participants tab and add one or more forecast series participants, such as yourself or another administrator who runs the forecast for the company.
For information about adding participants, see Adding Forecast Series Participants.
Click the Aggregation tab and add the required aggregation levels.
For information about adding aggregation levels, see Adding Aggregation Levels.

Creating a Departmental Forecast Series

The departmental forecast can be used as a supplement to other forecasting methods mentioned in this chapter. In many companies, the global forecast is only be available to a few individuals. The departmental forecast provides divisional or departmental managers with a way of taking a snapshot of their revenues for historical or analytical purposes. The departmental forecast is an example of a corporate snapshot type of forecast.

The departmental forecast:

Allows an individual user to take a snapshot of each departmental revenue at once
Requires no user or management intervention
Captures each revenue that meets the forecast series criteria, including partner and third-party related revenues
Avoids a lengthy and involved adjustment process as forecasts are rolled from manager to manager to executive

Compared to the personal forecasts, the departmental forecast requires a very low amount of overhead and almost no administration. It gives timely information with no requirement for intervention and adjustment.

Example: At company DEFG, there is an overlay sales group for every product line. The managers of these sales groups need periodic snapshots of their product specific revenues. Although each manager runs a small business, no individual manager is allowed to see how the other product lines are doing. When the managers do not think a revenue item is realistic, they ask the user to change it. The user’s committed forecast total is equal to the sum of each of their revenues that meet the company’s forecasting rules.

Use the departmental forecast if:

One manager wants to forecast for an entire team
Periodic snapshots of data are necessary

Do not use the departmental forecast if:

Data needs to be rolled up, or different levels of management need access to the snapshot
You do not need a mid management view of forecasting

To create a departmental forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series.
For information, see Creating a Forecast Series.
In the new forecast series, from the Visibility drop-down list, select My Team’s Revenues.
This causes the manager’s view to include each of the subordinates’ revenue records.
Click the Forecast Series Dates tab and add forecast dates.
For information about adding dates, see Defining Forecast Series Dates.
Click the Forecast Series Participants tab and add a few forecast series participants, including only one level of the hierarchy.
For information about adding participants, see Adding Forecast Series Participants.
Click the Aggregation tab and add the required aggregation levels.
For information about adding aggregation levels, see Adding Aggregation Levels.

Creating a Hybrid Forecast Series

A hybrid forecast allows you to have My Revenues and My Team’s Revenues visibility in the same Forecast series, therefore combining a rollup and departmental snapshot forecast.

The hybrid forecast allows for a forecast process to include both a rollup forecast and a departmental forecast in the same forecast series.
Use the hybrid forecast if one manager does not want or cannot have subordinates creating a formal forecast each period, yet another manager wants to have subordinates running a formal forecast rollup.
Do not use the hybrid forecast if both managers want either just a rollup or departmental forecast.

To create a hybrid forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a forecast series.
For information, see Creating a Forecast Series.
Click the Forecast Series Participants tab and add the appropriate users.
For information about adding participants, see Adding Forecast Series Participants.
Once you have added a participant, choose their visibility from the Visibility drop-down list by selecting either My Revenues or My Team’s Revenues.

Note: For a forecast series where visibility is set to My Revenues - Indirect Sales, the Visibility column is not available from the Add Participants view.

Caution: Do not select My Team’s Revenues for a manager that has included a participant as this results in double-counting.

Note: If you cannot see the Visibility field in the Forecast Series Participants list, check to see which columns are being displayed.

Setting Up Customer Adaptive Forecasting

Forecast participants in large enterprises are typically part of a matrix organization where the reporting structure does not necessarily match the forecast rollup hierarchy. For such situations, the customer adaptive forecasting feature was introduced to provide support for a forecast-specific hierarchy.

Customer adaptive forecasting:

Allows sales representatives to roll up and submit forecasts to managers outside of their reporting hierarchy
Allows sales managers to view forecasts from cross-functional teams across organizations

Use customer adaptive forecasting if you have a matrix organization where the forecasting hierarchy is not always the same as the reporting hierarchy.

Do not use customer adaptive forecasting if you want to maintain the Siebel Position Based Reporting Hierarchy.

Setting up customer adaptive forecasting involves defining a forecast-specific hierarchy that is specific to a particular forecast series. Sales administrators do this by specifying the visibility of the forecast as My Revenues - Indirect Sales, and the Submit To position for each participant in the forecast series (as required). The forecast-specific rollup hierarchy that you define for a forecast series does not need to match the sales reporting hierarchy.

To create a forecast-specific forecast series

Navigate to the Administration - Forecast screen, then the Forecast Administration view.
Create a new forecast series where Visibility is set to My Revenues - Indirect Sales.
For information about creating a forecast series, see Creating a Forecast Series.

Note: A forecast-specific hierarchy can only be defined for participants in a forecast series when the visibility for that forecast series is set to My Revenues - Indirect Sales.
Go to the Forecast Series Participants tab and:
1. Add the appropriate participants to the forecast series.
  For information about adding participants, see Adding Participants to a Forecast Series.
2. Define a forecast-specific hierarchy for participants in the forecast series.
  
  The forecast-specific hierarchy that you define for participants in a forecast series can be different to the sales reporting hierarchy. For more information, see Defining a Forecast-Specific Hierarchy For Participants in a Forecast Series.
  
  Note: By default, according to the position hierarchy, all participants in a forecast series report their forecasts to their manager; that is, unless a forecast-specific hierarchy is defined for participants in the forecast.

About Creating a Partner Forecast Series

Siebel Forecasting supports numerous partner forecasting scenarios. These scenarios include rollup forecasts, forecasts run by the partner only, forecasts of each partner, and forecasts of individual partner organizations. For details on setting up forecast series to support each of these scenarios, see Siebel Partner Relationship Management Administration Guide.

Deactivating Auto-Forecast

By default, the system preference Forecast: Auto-Forecast is set to true. This means that if you are a manager, when you forecast, the application automatically creates forecasts for subordinates who are listed as participants of that series who have not already created their forecasts. You can disable this feature if you want.

For more information about the Forecast: Auto-Forecast system preference, see Forecast: Auto-Forecast System Preference.

To deactivate auto-forecast

Navigate to the Administration - Application screen, then the System Preferences view.
In the System Preferences list, select the Forecast: Auto-Forecast record.
Change the System Preference Value to FALSE.
Restart the server.

About Configuring Revenue and Forecast Spreadsheets

Spreadsheets in Siebel Business Applications allow the user to view a list of values consolidated into a more concise format. For example, instead of seeing a long list of services delivered over a period of many months, the user sees just one row of information with the revenues listed out over time, with a series of dates as column headers.

The revenue spreadsheets are combined with revenue lists and revenue charts in Revenues views. You can move between the different displays by clicking the desired hyperlink in a Revenues view. This ability to view information in a variety of formats (list, chart, or spreadsheet) is useful when dealing with recurring revenues over time. This is especially true in cases where multiple products, employees, or revenue classes are involved in one user view.

Revenue and forecasting forms, lists, and charts are configured in Siebel Tools, using the standard properties and configuration techniques typically used for forms, charts, and lists. You can add columns, remove columns, change column headings, and apply calculations in Siebel Tools, using the same approach that you would use for almost any other Siebel applet.

Some revenue and forecast data displays in a spreadsheet-like applet. Spreadsheet applets are configured differently from forms, lists, and charts. This topic explains how to make changes to Revenue and Forecasting spreadsheet applets.

Modifying Spreadsheet Applets for Forecasting describes how to change the configuration of a spreadsheet applet so that users can use spreadsheets in views other than Revenues, Forecasts, or Time Sheets.
Configuring Spreadsheet Scrolling Buttons for Forecasting describes how to set up spreadsheet scrolling buttons.
Adding a Dynamic Column to the Spreadsheet describes how to add or change a dynamic column on a spreadsheet view.

Spreadsheet Column Types

Revenue and forecasting spreadsheets contain a set of static, or nonrepeating columns (displayed first in the spreadsheet), followed by a set of dynamic, or repeating columns. In the default Siebel application configuration, the Opportunity Revenues spreadsheet view consists of static columns including the Product Name and the Revenue Class (displayed first in the spreadsheet), followed by a repeating Revenue field. The Revenue field is a dynamic column that repeats once for each date in the Opportunity Revenues list.

You can configure both the static columns and the dynamic columns in the spreadsheet using Siebel Tools. You can add, hide, or change the order of columns in the spreadsheet. While the default configuration has just one repeating column, it is possible to have several repeating columns such as quantity, price, and revenue, or to have just margin and revenue, for example.

The Add Column button in the spreadsheet view allows users to dynamically add a new date column. The new column must be a valid date, such as 1/1/01. After the creation of the new date column, a new revenue record in the List view is automatically created with the appropriate default values consistent with the parent record, for instance Opportunity Name or Account Name.

Spreadsheet Groups

In the Opportunity and Account Revenue screens, when users click the Revenues tab, the items in the spreadsheet are automatically grouped together using a field called Dynamic Group Number. Items entered in the spreadsheet on the same row automatically receive the same Dynamic Group Number. Although these items are really individual records in the Revenue list and the Revenue table, they are grouped together in the spreadsheet using the Group Number. In the Forecasting views, it is the Forecast Item ID that ties the items in a row together.

When a user enters a value into a repeating cell in a Revenue and Forecasting spreadsheet view, a revenue record is automatically created with the appropriate default values. Typically, the default values include the static information in the spreadsheet, plus a few additional attributes. Changing the static values in the list can cause a revenue item to look different from other members of its group. In the default configuration of Siebel Sales, such records are automatically moved into their own groups. Changes to static values in the spreadsheet are automatically propagated to each of the corresponding revenue records. While the general behavior of the spreadsheet and list applets has already been defined, you can configure the content of these applets to meet user requirements.

Modifying Spreadsheet Applets for Forecasting

The following procedure describes how to change the configuration of a spreadsheet applet so that users can use spreadsheets in views other than Revenues, Forecasts, or Time Sheets.

To change the configuration of a spreadsheet applet

Identify the business component that includes the static information of the spreadsheet. This is the primary business component.
Identify the business component that includes the dynamic information of the spreadsheet. This is the data business component.

Note: In some cases, the primary business component already exists in Siebel Sales, while the data business component has to be created or modified so that it includes the columns that you want displayed in a repeating fashion.
The primary and data business components can exist in the same table. If they do, the property DC Data SameAsPrimary must be set to Y. The primary business component must include the subclass CSSBCDynCol. The Data Business component must include a subclass CSSBusiness component.
Configure the display applet to include the static columns and a required control called eDynamicColumns. This control acts as a placeholder for the data business component columns. Make sure that the primary business component is based on a subclass of CSSBCDynCol.
For the primary business component, configure a Web applet based on CSSSWEFrameDynCol (or subclass of CSSSWEFrameDynCol). Include controls for the static fields, followed by the eDynamicColumns control.

Configure the business components.

The following table provides instructions for configuring the user properties on the primary business component.

User Property	Value	Description
`Dynamic Columns Enabled`	Dynamic Columns Enabled	Required. Indicates that the applet uses the dynamic columns feature.
`DC Pri RowKey`	A field on the primary business component	Required. The primary key for grouping the items together on the same row in the spreadsheet. For example, in the Opportunities Revenues Spreadsheet view, this property is Dynamic Group Number.
`DC 1 Data BCName`	The name of the data business component	Required. This business component must be in the same BusObj as the primary business component.
`DC 1 Data DynColRowKey`	Row name	Required. Indicates in which spreadsheet row a data record appears, by matching Data.[DynColRowKey] with Primary.[DynColRowKey]. For example, in the Opportunities Revenues view, the DynColRowKey is the same as the DC Pri RowKey (Dynamic Group Number). However, in the Forecast Details view, these values are different.
`DC 1 Data DynColHdrKey`	Field name	Required. Indicates the data to be displayed as headers on recurring columns of the spreadsheet. For example, in the Opportunities Revenues view, the field name is Date, so each date in the group causes a new column to be displayed.
`DC 1 Data DynColCellValue`	Field, Model	Required. Field identifies the data to be displayed as the cell value in the spreadsheet. Model identifies the field on the primary business component that provides cell formatting information.
`DC 1 Data SubCol N (N ≥ 1)`	Field, Model	Use this property if you want to display more than one repeating column. Field identifies another column to be displayed after the column indicated by DynColHdrKey. Model identifies the field on the primary business component that provides formatting information for this field.
`DC 1 DataLink`	Link	Specifies the link to be used for driving records to be displayed in the spreadsheet. Typically, this is the link between the parent of the List applet and the data business component. For example, on the Opportunity or Account Revenues spreadsheet, this field is blank and the Siebel application uses the default parent link.
`DC 1 Data SameAsPrimary`	Y or N	If specified and set to Y, the Data 1 business component maps to the same table as the primary and uses the same fields for DynColRowKey, DynColHdrKey, DynColCellValue, and DynColCellValueId. This setting is necessary in a spreadsheet because every row displayed has at least one nonempty cell. This implies existence of a record in both the primary and data business components that includes that row key (master record). When the table is the same, only one record is needed.
`DC 1 Data SearchSpec`	Valid search specification	If specified, only records in the data business component that match the search specification are visible.
`DC 1 Data SortSpec`	Valid sort specification	The sort specification affecting the order of the dynamic columns in the spreadsheet, from first to last. For example, in the Opportunity Revenues spreadsheet, this property is Date, causing the columns to be sorted in ascending order by date. To sort in descending order by date, use Date (DESC).
`DC TotalsOnRight`	TRUE	If specified and set to TRUE, the total for each row appears in an additional column after the dynamic columns.
`DC DeleteDataRecords`	Y or N	Affects the behavior of the spreadsheet when the user deletes a record. It is recommended that you set this property to Y. If set to Y, records corresponding to nonempty cells in the row are deleted. If set to N (default), only the primary record for the row is deleted. The row no longer appears in the spreadsheet.

Note: To configure static columns in the spreadsheet so that they make universal changes to each record in Group ID, modify the user properties in business component Revenue DynCol using Siebel Tools. Find user properties like DC 1 Data Field Default #, [FieldName], Primary.[FieldName]. Remove fields you do not want and add other fields as desired. For example, the request for Revenue Type is added as DC 1 Data Field Default 9, Revenue Type, Primary.Revenue Type. Also, you need to modify the same user properties in the business component Revenue Plan Item DynCol to maintain the same Dynamic Column grouping behavior.

Configuring Spreadsheet Scrolling Buttons for Forecasting

Scrolling buttons appear in the upper corner of spreadsheets in both the Forecasts and Revenues screens. These buttons allow users to view records containing multiple columns. The following table describes the buttons.

Button	Name	Description
	Previous column set	Click to scroll backward to view the previous column set (before the current column set).
	Previous column	Click to scroll backward to view the previous column (before the current column).
	Next column	Click to scroll forward to view the next column (after the current column).
	Next column set	Click to scroll forward to view the next column set (after the current column set).

The static columns found on the spreadsheet view such as, Opportunity, Product, Currency, and so on, are fixed and do not move when the date columns are scrolled. Similarly, persistent columns such as the Total column and any new columns that are added using the Add Column button are retained as the user scrolls. Newly added date columns are persistent until the next time the spreadsheet is refreshed at which time it becomes dynamic like the other date columns.

You can enable or disable spreadsheet scrolling buttons and set the Set Size, which controls the number of dynamic columns to scroll at any one time, and the Window Size, which controls the number of dynamic columns that can be displayed on one screen. Window Size, as defined, does not include static or persistent columns.

To configure spreadsheet scrolling buttons

From Siebel Tools set the following values in the Applet, then the User Properties:
- DC Scrolling: Enabled
- DC Scrolling: Set Size (Default = 6)
- DC Scrolling: Window Size (Default = 6)
  
  Note: Set Size and Window Size must be equal so that the functionality is predictable to users. If Set Size is greater than Window Size, some records that the user expects to see are not displayed by default. For example, if SetSize is 8 and WindowSize is 6, clicking the next column set button causes the window not to display the first two columns in SetSize. The user has to click the previous column button to see those columns. Likewise, if Set Size is less than Window Size, the window displays more records than the user expects. For example, if SetSize is 4 and WindowSize is 6, using the next column set button displays the next four records to be returned as well as the last two columns of the existing window.

Configuring the Position of Spreadsheet Scrolling Buttons

The following procedure describes how to configure scrolling buttons to jump to the start or the end of the spreadsheet.

To configure scrolling buttons to jump to the start or the end of the spreadsheet

Set the SetSize to a large number. For example, if SetSize = 1000, the scrolling button jumps to the end of the spreadsheet, assuming there are fewer than 1000 columns.
Use the Previous column or Previous column set buttons to scroll backward to the previous column or previous column set.

Deactivating Scrolling Spreadsheet Buttons

The following procedure describes how to deactivate scrolling spreadsheet buttons.

To deactivate scrolling spreadsheet buttons

Locate the following applets:
- Forecast 2000 -- Forecast Summary List Applet DC
- Forecast 2000 -- Forecast Item List Applet DC (ExecWS)
- Account Revenue Schedule List Applet DC
- Opportunity Revenue Schedule List Applet DC
For each applet, deactivate the following Applet, then the User Properties:
- DC Scrolling: Enabled
- DC Scrolling: Set Size
- DC Scrolling: Window Size
For each applet, deactivate the following Applet, then the Controls:
- GotoNextHorColumn
- GotoNextHorSet
- GotoPrevHorColumn
- GotoPrevHorSet
For each applet, deactivate the corresponding Applet, Web Template, and then the Web Template items:
- Opportunity Revenue Schedule List Applet DC:
  - GotoNextHorColumn (item identifier 150)
  - GotoNextSet (item identifier 151)
  - GotoPrevHorColumn (item identifier 164)
  - GotoPrevSet (item identifier 163)
- Account Revenue Schedule List Applet DC:
  - GotoNextHorColumn (item identifier 150)
  - GotoNextSet (item identifier 151)
  - GotoPrevHorColumn (item identifier 164)
  - GotoPrevSet (item identifier 163)
- Forecast 2000 -- Forecast Summary List Applet DC:
  - GotoNextHorColumn (item identifier 150)
  - GotoNextSet (item identifier 151)
  - GotoPrevHorColumn (item identifier 164)
  - GotoPrevSet (item identifier 163)
- Forecast 2000 -- Forecast Item List Applet DC (ExecWS)
  - GotoNextHorColumn (item identifier 150)
  - GotoNextSet (item identifier 151)
  - GotoPrevHorColumn (item identifier 164)
  - GotoPrevSet (item identifier 163)

Adding a Dynamic Column to the Spreadsheet

The following procedure describes how to add or change a dynamic column on a spreadsheet view. For example, users sometimes want to add Price and Quantity or Cost in addition to Revenue, which is the one dynamic column on the Revenue spreadsheet that is preconfigured. The following procedure uses the Quantity field as its example and is based on a standard configuration environment.

To add the dynamic columns Price and Quantity to a spreadsheet

Change the business component Revenue DynCol as follows:

Name: "DC 1 Data SubCol 1" 
Value: "Price , Price" 
Inactive: False

Name: "DC 1 Data SubCol 2" 
Value: "Quantity , Quantity" 
Inactive: False

Verify that the Quantity field is active on the data business component, Revenue. The Inactive property for this field is FALSE.
Verify the following for the applet: Opportunity Revenue Schedule List Applet DC. The properties for the List Column, Quantity are:
```
Available: TRUE
Inactive: FALSE 
Show In List: TRUE
```
Verify the following for the applet: Opportunity Revenue Schedule List Applet DC:
1. Edit the Web Layout.
2. Verify that the Quantity column is mapped into the Edit List Web template. (The location does not matter.)
Submit the changes.
The Quantity field is visible as a dynamic column in the Revenues Spreadsheet view.