Siebel Forecasting Guide > Setting Up Forecasting >

Modifying Spreadsheet Applets for Forecasting

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

To change the configuration of a spreadsheet applet

  1. Identify the business component that includes the static information of the spreadsheet. This is the primary business component.
  2. 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.

  3. 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.
  4. 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.
  5. 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.
  6. Configure the business components.

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

    User Property

    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.

    NOTE:  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


    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 left to right.

    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


    If specified and set to TRUE, the total for each row appears in an additional column to the right of 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.

Siebel Forecasting Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.