Siebel Consumer Goods Guide > Sales Volume Planning >

About the SVP Aggregate Action

SVP is the process of modeling projected sales of a product at one or more accounts in a future time period. Companies establish sales volume plans to forecast or plan the quantity of products they expect to sell to these accounts during the SVP period. The SVP Aggregate action models this complex account-category-product-period hierarchy and allows for the allocation and aggregation of data through this hierarchy.

The SVP Aggregate action uses the account-category links that an administrator creates to construct the account-category-product hierarchy, and associates the imported source data with the appropriate SVP nodes. SVP nodes create records that represent the combination of accounts and category-products.

The SVP Aggregate action is an ongoing SVP task. Each time you run the action after the initial Aggregate action, a search is performed down the established account-category-product-period hierarchy structure and any new or missing nodes are created. The data is then reaggregated up through the account-category-product-period hierarchy.

Executing the SVP Aggregate action is a resource-intensive task because the action depends on the complexities of your account-category-product-period hierarchy and your source data set. The appropriate planning of this process is important when using the SVP module.

NOTE:  The SVP Aggregate action does not aggregate across period types. Changes to data stored in weeks do not aggregate up into the monthly periods, and changes to data stored in years do not allocate down throughout the periods in the year. You can aggregate data, however, using Oracle Business Intelligence for reporting purposes. It is recommended that you store data in the standard periods of weeks or months.

About Maximizing Aggregation Performance

The Aggregate action is the most resource-intensive action in the SVP module. To maximize performance, run Aggregate for only select period ranges. Also, use short intervals and run Aggregate only as frequently as your business requirements dictate. For example, if you store sales volume data by week, it is recommended that you run the aggregation at the end of each week and only for the that week.

NOTE:  Running Aggregate for the first time creates a large number of transaction records. It is recommended that you perform this function in an environment that allows optimum performance.

Follow these guidelines to maximize aggregation performance:

• Make sure that the Siebel database is configured according to the Siebel Installation Guide for the operating system you are using.
• Turn off transaction logging during Aggregate.
• Reextract all mobile clients. For more information, see Siebel Remote and Replication Manager Administration Guide.