Siebel Developer's Reference > Business Component Classes > CSSBCForecast Class >

Dependencies and Limitations for Forecast Classes

The business components whose names begin with Forecast 2000 depend on each other and depend on revenue business components. If you modify one of these business components, then you must also modify any dependent business components. For example:

• If you modify the Forecast 2000 -- Forecast Item Detail business component, then you must modify the Forecast 2000 -- Forecast Item Detail Flat business component.
• Siebel CRM uses the Forecast 2000 -- Forecast Item DynCol business component to display the Forecast Details spreadsheet. Each record that resides in the Forecast Item DynCol business component corresponds to a row in the spreadsheet, and the child forecast details provide data for the dynamic columns, such as dates. For more information about the dynamic column user properties, see Siebel Forecasting Guide.
• Siebel CRM uses the Forecast 2000 -- Forecast Item Detail Flat business component to join the Forecast Item and Forecast Item Detail business components. It uses this join to create a flat view. The Forecast Item business component typically stores the nonnumeric properties that the child details can share. To support this configuration, you must add new fields and user properties that reference this field to these business components.
• If you add a field to a revenue business component, and if a forecast must include data from this field, then you must add a corresponding field to a forecast business component and you must add a column to the table that this forecast business component references.