Siebel Developer's Reference > Business Component User Properties > Controlling Siebel CRM Data >

Controlling Revenues

This topic describes business component user properties that you can use to control revenues.

Specifying Revenue Aggregation Fields

The Revenue Aggregation Field n user property specifies the business component field that Siebel CRM rolls up into the summary record from the detail records. Details and summaries reside in the same business component. A summary record sums the values from one or more fields that reside in the detail records for the summary date range. The value of this user property must contain the name of a field that resides in the Forecast 2000 -- Forecast Item Detail business component. For example, if you use the following value, then Siebel CRM sums the Amount Revenue field from the detail records, and then stores this sum in the summary record:

Amount Revenue

You can configure Siebel CRM to deactivate this user property.

You can specify this user property with or without the numeric suffix. For more information, see Numbering Instances of a User Property.

Specifying Pop-up Revenues Lists

The Revenue Associate List user property displays an association list if the user clicks New to create a new detail. The value for this user property is a Boolean value. If Y, and if the user clicks New to create a new detail, then Siebel CRM displays a pop-up list that lists revenues. The associated search specification for the current forecast series identifies the revenues that Siebel CRM displays. The user must associate one of these revenues with the forecast instead of adding free text data.

You define this user property on the Forecast 2000 -- Forecast Item business component.

You can configure Siebel CRM to modify the value for this user property, but not to deactivate it or to create a new instance of it.

Specifying the Field That Siebel CRM Copies for New Revenue Forecasts

The Revenue Field Map: fieldname user property specifies the field that Siebel CRM copies from the Revenue business component to one of the following business components. It copies this value if the user creates a detail in the Forecast Item business component:

• Forecast 2000 -- Forecast Item
• Forecast 2000 -- Forecast Item Detail

Note the following:

• The value of this user property must contain the name of a field that resides in the Revenue business component.
• The fieldname must identify the name of a field that resides in the Forecast 2000 -- Forecast Item business component.

For example, assume you define the user property that Table 20 describes. You define it on the Forecast 2000 -- Forecast Item business component. In this example, Siebel CRM copies the value of the Sales Rep Organization Id field of the Revenue business to the Organization Id field.

You can configure Siebel CRM to modify the value for this user property, create a new instance of it for each field that Siebel CRM must copy, or deactivate it.