Bookshelf Home | Contents | Index | PDF |
Siebel Consumer Sector Guide > Sales Volume Planning > Initial SVP Administrator Procedures > Performing the Initial AggregationThe Sales Volume Planning Aggregate action executes and builds the account-category relationships defined earlier in the physical database. After this process is complete, Sales Volume Planning users can navigate the associated account-category hierarchy to understand or change periodic product movement data. You can specify the Aggregate action to aggregate baseline data and roll up incremental volume from any level of the hierarchy across the entire account-category-product hierarchy. You can also choose to aggregate particular source fields (such as incremental volume) rather than the entire source table. Make sure that products are associated with their respective account's authorized product distribution list. For more information, see Creating and Modifying Distribution Lists. Maximizing Aggregation PerformanceThe Aggregate action is the most resource-intensive action in the SVP module. To maximize performance, run Aggregate for select period ranges only. Also, keep the intervals small and run Aggregate only as frequently as dictated by your business requirements. For example, if you are storing volume data by week, it is preferable to run the aggregation at the end of each week, and then only for the week just completed. Running Aggregate for the first time creates a large amount of transaction records. It is recommended that you perform this function in an environment that allows optimum performance. To maximize aggregation performance
Optional: Parallel Aggregation Processing on Multiple ServersIf you have a multiple Siebel server environment, you can expedite aggregation processing by running parallel SVP aggregation actions. NOTE: Each Siebel server must have the Workflow Process Manager component enabled. For more information, see Siebel System Administration Guide and System Monitoring and Diagnostics Guide for Siebel eBusiness Applications. To facilitate parallel processing, you must partition your desired aggregation into multiple aggregation actions. For example, if you want to aggregate Consumption data for the first 12 weeks of the year, instead of creating a single 12-week SVP action (Aggregate) record, you create four Aggregate action records of three weeks each. After you create the aggregation actions, the actions can be run separately on the multiple servers until each aggregation action is complete. The following procedure describes how to perform parallel processing. To perform parallel aggregation processing:
|
Siebel Consumer Sector Guide |