Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Consumer Goods Guide > Sales Volume Planning > Performing the Initial AggregationThe SVP Aggregate action executes and builds the account-category relationships that are defined earlier in the physical database. After this process is complete, SVP users can navigate the associated account-category hierarchy to understand or change periodic product movement data. You can specify that the Aggregate action aggregates baseline data and rolls up incremental quantity from any level across the entire account-category-product hierarchy. You can also aggregate specific source fields (such as incremental quantity) rather than the entire source table. You must run the SVP Aggregate action independently for each product movement table: baseline, target, consumption, and shipment. For example, a planning administrator who wants to establish targets and a baseline basis must run the Aggregate action twice—the first time to establish the targets and a second time to establish a baseline basis. You use the same SVP hierarchy when performing the Aggregate action for targets and a baseline basis. The Aggregate action fails if the product movement tables do not contain data. NOTE: Before performing aggregation, make sure that products are associated with the authorized product distribution list for their respective account. For more information about distribution lists, see Creating Distribution Lists. This task is a step in Roadmap for Sales Volume Planning.
|
![]() ![]() |
Siebel Consumer Goods Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |