Siebel Developer's Reference > Business Component Classes >

CSSBCForecastItemDetail Class

CSSBCForecastItemDetail is used with the CSSBCForecastItem Class to store the detail and summary records for forecasts. The CSSBCForecastItemDetail class specifically stores data relevant to certain aspects of the records (for example, Quantity, Price, and Revenue). There can be many CSSBCForecastItemDetail records for each CSSBCForecastItem record. Records of type CSSBCForecastItem are also used in the spreadsheet view to determine each row of the spreadsheet while the CSSBCForecastItemDetail is used to determine the individual columns within the spreadsheet.

Usage Guidelines

You can use the CSSBCForecastItemDetail class for adding and deleting of detail and summary records to forecasts. It should not be used in other instances.



Accessible Methods

The following methods are accessible from CSSBCForecastItemDetail. For more information on these methods, see CSSBCForecastItemDetail Methods.

Business Component User Properties

The following business component user properties are available for use in CSSBCForecastItemDetail. For more information on these and other user properties, see User Properties.

Field User Properties

Not applicable

Dependencies and Limitations

The Forecast business components are tightly integrated together. The business components that start with Forecast 2000 are heavily dependent on each other. Even small changes can lead to many unexpected behaviors. The Revenue business component is also tied into this, so be careful when making changes to the Revenue business component.

The Forecast 2000 -- Forecast Item Detail business component is used internally by the forecast engine, while the Forecast 2000 -- Forecast Item Detail Flat business component joins both the Forecast Item and Forecast Item Detail business components to form a flat view (the Forecast Item business component usually stores the nonnumeric properties which can be shared by child details). In general, this means that new fields (and user properties referencing that field) should be added to both business components.

Siebel Developer's Reference