7Sales Volume Planning

Sales Volume Planning

This chapter describes how to set up and perform sales volume planning (SVP). Topics include:

• About Sales Volume Planning

• About the SVP Aggregate Action

• Scenario for Using Sales Volume Planning

• Roadmap for Sales Volume Planning

• Process of Setting Up Category-Product Hierarchies

• Process of Defining SVP Hierarchies

• Performing the Initial Aggregation

• Running Aggregation Processing in Parallel

• Populating Locks

• Process of Establishing Baseline Basis Quantities

• Copying Baseline Information to Other Fields

• Manually Entering SVP Data

• Process of Performing Ongoing SVP Administrative Tasks

• Viewing SVP Data (End User)

• Skipping SVP Source Data (End User)

• Locking and Modifying SVP Data (End User)

• About SVP Algorithms

• About Category and Account Level Allocation

• About Number Handling and Percentage-Basis Calculations

• About Configuring Sales Volume Planning

• Configuring Sales Volume Planning

About Sales Volume Planning

Sales volume planning (SVP) is an iterative process in which consumer goods manufacturers model the projected sales for an upcoming period. Companies capture and update salesperson-influenced data pertaining to the quantity or value of product that their customers will purchase during a period of time. Uses of SVP include the following tasks:

• Top-down volume planning of target sales, usually starting with a high level number from a financial planning system.

• Bottom-up total sales forecast planning, usually with sales of the previous year as the starting point.

• Baseline volume estimating, usually starting with a derived baseline from Demantra or a Demand Planning system such as APO, I2, or Manugistics.

Note: This chapter uses the term quantity to represent any amount in SVP. You can also use a monetary amount, such as currency. However, you cannot use quantity and monetary amounts at the same time in SVP.

As part of their annual forecasting process, companies use SVP based on the data sets. These data sets make the SVP process possible and provide feedback, in the form of baseline and target quantities, for current and future sales volume plans. You can develop this data internally, or a third party can supply this data.

Note: It is recommended that companies perform complex trending and data modification on the initial load of historical records, such as shipment history, before importing this data into Siebel base tables.

See the following table for definitions of the data sets.

Data Set	Definition
Baseline	This data set is the quantity of product that would have been shipped, sold, or consumed without an account promotion for a period of time. The Baseline view also shows incremental quantity, the quantity of product that is shipped, sold, or consumed as a direct result of an account promotion for a period of time. For example, because a product is on sale, a customer purchases two incremental pallets of the product in addition to the one the customer regularly purchases. Incremental quantity is generated during account promotion planning. For more information about account promotions, see Trade Promotions
Incremental	This data set is the quantity of product that is sold over and above the baseline quantity and that is attributed to an account promotion.
Target (Also referred to as quota or objective)	This data set is the quantity of product that a manufacturer expects to sell in a period of time. Targets can incorporate growth or decline rates for the SVP period.
Shipment	This data set is the quantity of product that is shipped to customers during a period of time. Because shipments are always historical data, end users can view, but not modify, the shipment data.
Consumption	Also called Consumption Volume. This data set is the quantity of product that customers purchase and use during a period of time. Because consumption is always historical data, end users can view, but not modify, the consumption data.

See the following table for possible sources of these data sets.

Data Set	Possible Sources
Baseline	Obtain from shipments to accounts information. Obtain from customer warehouse withdrawals that a customer provides to the manufacturer or that a third-party data source provides. Derive from consumption data.
Incremental	Derive by calculating the difference between customer warehouse withdrawals, or shipments, and baseline. Obtain from a third-party data source. Incorporate lift matrices or use an educated estimate.
Target (Also referred to as quota or objective)	Derive from shipment, baseline, or consumption data from a prior period. Modify data based on a factor such as a growth or decline rate expected for the upcoming period.
Shipment	Import from an order processing system or a customer data warehouse.
Consumption	Obtain from a third-party data source. Use customer warehouse withdrawals as a proxy to derive.

About Basis, Planning, and Baseline Data Elements

The SVP module supports the following three-step baseline and target planning process:

1. The Baseline Basis (or Target Basis) fields are populated with data that you previously import or copy into the sales volume plan. These read-only fields serve as the basis data for the planning process.

2. The SVP process promotes this data into Baseline Planning (or Target Planning) values, which are then released to sales planners or account managers for adjustment. Sales planners and account managers make their adjustments based on known elements that impact trends for the planning periods.

3. After users make these adjustments, the values are promoted into the Baseline (or Target) fields where the values are also used as the account promotion baseline.

Your company can choose to use some or all of these elements in its planning process.

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.

For more information about aggregation, see Performing the Initial Aggregation.

Scenario for Using Sales Volume Planning

SVP administrators, senior managers, and account managers perform the process in this example scenario for using SVP. Your company might follow a different process according to its business requirements.

An SVP administrator for a large beverage manufacturer knows that her company is beginning its annual planning effort. To generate the SVP, she performs several tasks. First, she identifies the source of the sales volume planning data. This source might be shipment or consumption data from previous periods. After she identifies the data, she reviews it to determine its relevancy for future SVP periods. As a result of the review, the SVP administrator chooses to skip certain account-product periods because of discontinued products or inactive accounts in those periods.

Next, she uses the data to establish a baseline for all products and accounts in the specified planning periods. She can modify the data directly or use it as a basis for populating the baseline planning field. In this case, the SVP administrator chooses to copy the values into the baseline planning fields for comparable periods and, while doing so, she uses the percentage change algorithm to increase the values by 5%. After the baseline planning column is populated, the SVP administrator informs the senior managers and region managers that they can manually adjust the values.

The senior managers modify the data and allocate these changes down the account-category-product hierarchy. The SVP administrator then informs the subordinate managers and account managers that the data is available.

The account managers then modify the baseline data based on their knowledge of their local accounts and markets. They use this information to plan account promotions for these accounts, and they enter the incremental quantity that they anticipate as a result of these account promotions. Finally, at the end of the planning cycle, the SVP administrator reaggregates the baseline and incremental data and exports the data to a demand planning tool that she can use in the consensus forecasting.

Roadmap for Sales Volume Planning

This topic lists the tasks and processes that administrators and end users typically perform to successfully execute the SVP process. Your company might follow a different roadmap according to its business requirements.

Administrator Procedures

The following list shows tasks and processes that administrators typically perform to execute sales volume planning:

1. Process of Setting Up Category-Product Hierarchies

2. Process of Defining SVP Hierarchies

3. Performing the Initial Aggregation

4. (Optional) Running Aggregation Processing in Parallel

5. Populating Locks

6. Process of Establishing Baseline Basis Quantities

7. Copying Baseline Information to Other Fields

8. Manually Entering SVP Data

9. Process of Performing Ongoing SVP Administrative Tasks

End-User Procedures

The following list shows tasks that end users typically perform to execute sales volume planning:

1. Viewing SVP Data (End User)

2. Skipping SVP Source Data (End User)

3. Locking and Modifying SVP Data (End User)

Process of Setting Up Category-Product Hierarchies

The following list shows the tasks that administrators perform to set up a category-product hierarchy:

• Setting Up Account Hierarchies

• Creating Category-Product Hierarchies

• Associating Products with Categories

• Acquiring Categories

• Deleting Products and Categories

This process is a step in Roadmap for Sales Volume Planning.

Setting Up Account Hierarchies

You must establish an account hierarchy in which every account in the hierarchy has a parent account except the root account (the highest-level account in an account hierarchy). Organizational entities that are part of sales volume plans must exist in this SVP account hierarchy. For instructions about setting up account hierarchies, see Setting Up Account Hierarchies.

This task is a step in Process of Setting Up Category-Product Hierarchies.

Creating Category-Product Hierarchies

You must establish an explicit category-product hierarchy before beginning the SVP process. Categories and products in SVP must have a single designated SVP parent category.

This task is a step in Process of Setting Up Category-Product Hierarchies.

To create a category-product hierarchy

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. In the All Categories list, create a new record, and complete the necessary fields. Repeat this step for all categories.

   The following table describes some fields.

   Field	Comments
   Category Name	The name of the category in the category-product hierarchy.
   Parent SVP Category Name	The parent SVP name of the category (for example, All Products). This field is automatically populated when you later establish category-subcategory relationships.
   SVP Level	The SVP level of the category. This field is automatically populated when you make an association to a subcategory.
   Description	A description of the category-product hierarchy.
   Effective Start Date	The starting date and time of the category.
   Effective End Date	The ending date and time of the category.
   Catalog Name	The name of the catalog that is associated with this category-product hierarchy.

3. In the All Categories list, select the root category, and drill down on the Category Name field hyperlink.

   The SVP Category Details view appears.

4. In the Subcategories list, add the subcategory or subcategories for which you want to designate the parent category as the subcategory’s SVP parent.

   Note: You can designate many subcategories as SVP adoptees for the SVP parent. However, if a subcategory has another category as its SVP parent, your designation ends the previous SVP parent relationship and creates a new one.

Associating Products with Categories

After establishing your multiple-category hierarchy, you associate products with each of the appropriate categories. Associate only products at the lowest level of the category hierarchy.

Caution: Even though you can add products to the upper levels of the category hierarchy, it is not recommended because the products are not recognized during SVP actions.

Note: If you create product to category links through other methods that are external to the application, you need to perform an Acquire Categories action to create the associations. For more information about this action, see Acquiring Categories.

This task is a step in Process of Setting Up Category-Product Hierarchies.

To associate products with a category

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. Drill down on the Category Name field hyperlink for a category.

   The SVP Category Details view appears.

3. In the Subcategories list, drill down on the Name field hyperlink until you reach the lowest level subcategory.

4. In the Products list, create a new record.

5. In the Add Internal Products dialog box, select one or more products, and click Add.

6. In the Products list, select one or more products for which you want to designate an SVP parent category.

7. Click SVP Adopt.

   The SVP Adoptee field of the selected product is automatically populated with a check. This product now has the selected parent category as its SVP parent. The other products in the Products list, for which the SVP Adoptee field is cleared, are not active products for the parent category. They do not appear in sales volume plans for the parent category.

Acquiring Categories

Associating products with categories creates the links that the application needs to enable the allocation process. If you make these associations through another method that is external to the application, you need to perform an Acquire Categories action to establish these links. You must perform this action when the category-product hierarchy changes.

This task is a step in Process of Setting Up Category-Product Hierarchies.

To perform the Acquire Categories action

1. Navigate to the Administration - Sales Volume Planning screen, then the Other Actions view.

2. In the Other Actions form, create a new record.

3. From the Action field drop-down list, select Acquire Categories.

4. Enter text in the Description field (for example, Fall Forecast - Acquire Categories).

5. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field. After the categories are acquired, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Deleting Products and Categories

When deleting products, you must first unadopt the product. Similarly, when deleting a category, first unadopt all products associated with that category.

Caution: If you do not delete products and categories using the method described in this topic, you must run the Acquire Categories action to make sure that the allocation functions correctly in the new hierarchy. You can also run the Acquire Categories action to synchronize the category-product hierarchy when inconsistencies are introduced through error. Failing to keep this hierarchy synchronized adversely affects the allocation functionality.

This task is a step in Process of Setting Up Category-Product Hierarchies.

To unadopt a product

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. Drill down on the Category Name field hyperlink for a category.

3. In the Subcategories list, drill down on the Name field hyperlink until you reach the lowest level subcategory.

4. In the Products list, select one or more products that you want to delete.

5. Click SVP Adopt.

   The check in the SVP Adoptee field of the selected product is cleared. This product is no longer active for the parent category in SVP functions.

Process of Defining SVP Hierarchies

Connecting the account hierarchy with the category-product hierarchy establishes the SVP hierarchy, also known as the account-product tree. You can connect these hierarchies by associating accounts in the account hierarchy with the categories in the category-product hierarchy.

Caution: Make sure the account hierarchy is explicit and contiguous, with every account in the hierarchy having a parent account except the root account. All organizational entities that are part of sales volume plans must exist in this SVP account hierarchy.

The following list shows the tasks that administrators can perform to define the SVP hierarchy:

• Manually Associating Categories with Accounts

• Manually Associating Subcategories with Accounts

• Modifying Account-Category Hierarchies

• Deleting Account-Category Hierarchies

• Importing the associations with the data from a back-office system

Caution: Running Aggregate can take you less time than manually establishing associations between every account and category-product hierarchy. However, the Aggregate action aggregates sales volume data and can take a long time to complete. Therefore, if you run Aggregate to create these associations, import the SVP data before running Aggregate.

This process is a step in Roadmap for Sales Volume Planning.

Manually Associating Categories with Accounts

You can manually associate categories with accounts.

This task is a step in Process of Defining SVP Hierarchies.

To manually associate a category with accounts

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. Drill down on the Category Name field hyperlink for a category.

   The SVP Category Details form appears.

3. From the visibility filter, select SVP Category Accounts.

4. Scroll down to the Accounts list and create a new account record.

5. In the Pick Account dialog box, select the accounts that you want to add to the category, and click Add.

Manually Associating Subcategories with Accounts

You can manually associate subcategories with accounts.

This task is a step in Process of Defining SVP Hierarchies.

To manually associate a subcategory with accounts

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. In the All Categories list, select the subcategory that you want to associate with accounts.

3. Drill down on the Category Name field hyperlink for the subcategory.

   The SVP Category Details view appears.

4. From the visibility filter, select SVP Category Accounts.

5. Scroll down to the Accounts list and create a new account record.

6. In the Pick Account dialog box, select the accounts that you want to associate with the subcategory, and click Add.

Modifying Account-Category Hierarchies

You can modify account-category hierarchies to reflect changes to accounts and categories in your organization. An account-category hierarchy changes when you change a parent-child account relationship. Perform changes to a parent-child account relationship by designating a new or different parent account for an account record. You can make these changes from one of the Sales Volume Planning views or from the general Data Administration views for accounts.

After making these changes, you must perform the Aggregate action. Take special consideration if the hierarchy change removes all associated subaccounts from a parent account. For information about the Aggregate action, see Performing the Initial Aggregation.

This task is a step in Process of Defining SVP Hierarchies.

To modify an account-category hierarchy

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. In the All Categories list, select a category record.

3. From the visibility filter, select SVP Category Accounts.

4. Scroll down to the Accounts list, select an account record, and modify the Parent Account field.

Deleting Account-Category Hierarchies

You can delete an account-category association by removing the account from the SVP Category Accounts view. After making this change, you must perform the Aggregate action. For information about the Aggregate action, see Performing the Initial Aggregation.

This task is a step in Process of Defining SVP Hierarchies.

To delete an account-category hierarchy

1. Navigate to the Administration - Catalog screen, then the SVP Categories view.

2. In the All Categories list, select a category record.

3. From the visibility filter, select SVP Category Accounts.

4. Scroll down to the Accounts list, select an account record, and delete it.

Performing the Initial Aggregation

The 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.

To perform an aggregation

1. Navigate to the Administration - Sales Volume Planning screen.

2. In the Aggregate view, create a new record.

3. From the Action field drop-down list, select Aggregate.

4. Complete the necessary fields.

   The following table describes some fields.

   Field	Comments
   Description	The name of the sales volume plan.
   Source Table	The complete data set (baseline, shipment, consumption, or target) that you want to aggregate. Select a source table if you want to aggregate the entire data set.
   Source Field	The subset of data that you want to aggregate (for example, incremental quantity or shipped quantity). Select a source field if you want to limit the aggregation to a specific column of SVP data.
   Start Period	The starting period of the source field or table.
   End Period	The ending period of the source field or table.
   Starting Account Level	The level of the hierarchy from which you want to begin the aggregation. If this field is blank, aggregation starts at the lowest level of the account hierarchy.

5. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field.

   Note: If you prepare sales volume data for multiple periods and want to track the progress of the action, click the Sub Actions view tab to see the status of the periods as they are processed.

   After the aggregation is built, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Running Aggregation Processing in Parallel

You can expedite aggregation processing by running parallel SVP Aggregate actions.

Note: You must enable the Workflow Process Manager component for each Siebel Server. For information about enabling components on a Siebel Server, see Siebel System Administration Guide.

To facilitate parallel processing, you partition your 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 Aggregate action record, create four Aggregate action records of three weeks each.

After you create the aggregation actions, you can run the actions in parallel, as multiple tasks on one server or as tasks on multiple servers.

To set up parallel aggregation processing, perform the following tasks:

1. Make sure Siebel Workflow Manager is started. For more information, see Setting Up Siebel Workflow Processes for Consumer Goods.

2. Enable the Workflow Process Manager component on each Siebel Server. For information about enabling components on a Siebel Server, see Siebel System Administration Guide.

3. Start the Workflow Monitor Agent on each Siebel Server. For more information, see Siebel Business Process Framework: Workflow Guide.

   Note: To run multiple aggregation processes in parallel, each process needs a Workflow Monitor Agent. For example, if you want to run five processes in parallel, you must start five Workflow Monitor Agents. Similarly, if you want to run six parallel processes on a single server, you must start six Workflow Monitor Agents on that server.

4. Modify the CG SVP Action business component to enable the Mass Invoke button. For more information, see Modifying the CG SVP Action Business Component.

5. Set up and run parallel SVP Aggregate actions from a single-server or multiple-server environment. For more information, see Performing Parallel Aggregation Processing.

This task is a step in Roadmap for Sales Volume Planning.

Modifying the CG SVP Action Business Component

To enable the Mass Invoke button, which you need for parallel processing, you must modify the CG SVP Action business component. If you do not modify the CG SVP Action business component as described in the following procedure, you cannot use the Mass Invoke button.

To modify the CG SVP Action business component

1. Log in to Siebel Tools.

2. In Object Explorer, select the Business Component object, and in the Object List Editor, query for the following business component: CG SVP Action.

3. In the Object Explorer, select the Business Component User Prop child object.

4. For the Generate Account Category user property, change the value to FALSE.

Performing Parallel Aggregation Processing

Before beginning this procedure, confirm that the AOM parameters for the eConsumer Object Manager (ENU) are as follows:

Minimum MT Servers = n plus 1

Maximum MT Servers = n plus 1

Where n is the number of servers that you use.

Caution: If you are configuring parallel SVP processing for the first time, you can use Workflow Simulator to test the following procedure before using Workflow Monitor Agent. For more information about Workflow Simulator, see Siebel Business Process Framework: Workflow Guide.

To perform parallel aggregation processing

1. Log in to the Siebel Consumer Goods application, and navigate to the Administration - Sales Volume Planning screen, then the Other Actions view.

2. Create an SVP Populate Locks action and click Execute Action.

   All records are unlocked and available for aggregation.

3. Create an SVP Acquire Categories action and click Execute Action.

   Account category records are created for each combination of accounts and categories.

4. After you determine how to divide the aggregation into subperiods, create and execute an SVP Aggregate action record for each subperiod aggregation using the instructions in Performing the Initial Aggregation.

5. For each Siebel Server running Consumer Goods that you want to use to process this aggregation, log in and launch a new instance of the Consumer Goods application Web client.

6. On each client, navigate to the Administration - Sales Volume Planning screen.

7. From the Aggregate view, click Mass Invoke.

   Repeat this step for each client.

8. Close each client.

9. To monitor the progress of your parallel aggregations, launch a new instance of the Consumer Goods application Web client and navigate to the Administration - Sales Volume Planning screen.

   The SVP Action list displays the status of each Aggregate action. Make sure that at least two Aggregate actions have a status of Executing at the same time. This condition confirms that the processing is running in parallel.

Populating Locks

After building an SVP hierarchy, you populate the hierarchy’s locks. When you populate locks, multiple users cannot simultaneously edit data, and you can remotely edit forecast data.

Note: Until you populate the locks, end users cannot view SVP data.

Locks are populated at the account level, preventing users at lower account levels from overwriting modifications that users make at higher account levels.

For more information about locking SVP data, see Locking and Modifying SVP Data (End User).

This task is a step in Roadmap for Sales Volume Planning.

To populate SVP hierarchy locks

1. Navigate to the Administration - Sales Volume Planning screen, then the Other Actions view.

2. In the Other Actions form, create a new record.

3. From the Action field drop-down list, select Populate Locks, and enter text in the Description field.

4. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field. After the locks in the hierarchy are populated, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Process of Establishing Baseline Basis Quantities

After importing the SVP data, you copy the data to the Baseline Basis Qty field. Typically, your first step in creating a baseline is generating a baseline basis quantity. A baseline basis quantity is generated from imported SVP source data and represents the preadjusted quantity that would have been sold without an account promotion.

The following list shows that tasks that administrators perform to establish a baseline basis quantity:

• Generating Baseline Basis Quantities for Existing Products

• Generating Baseline Basis Quantities for New Products

• Precalculating Adjusted Baseline Basis Quantities

This process is a step in Roadmap for Sales Volume Planning.

Generating Baseline Basis Quantities for Existing Products

For existing products, you can use shipment or consumption data from an earlier period or baseline data from a demand planning tool as the source data for generating a baseline basis. After determining the source of the baseline basis, for example, historical shipments, you copy these records to the baseline basis quantity.

This task is a step in Process of Establishing Baseline Basis Quantities.

To generate a baseline basis quantity for an existing product

1. Navigate to the Administration - Sales Volume Planning screen, then the Copy Actions view.

2. In the Copy Actions form, create a new record.

3. From the Action field drop-down list, select Copy Field.

4. In the Account field, select the highest level account structure, for example, All Accounts or Company HQ.

5. Select a value in the Category field or the Source Product field.

   Note: You must select the Account field before you select the Category field or the Source Product field.

6. Complete the rest of the fields in the form.

   The following table describes some fields.

   Field	Comments
   Description	A description of the action that creates the sales volume plan, for example, copy Shipped Qty to Baseline Basis Qty.
   Category	The category in the category-product hierarchy.
   Source
   Source Product	The product in the category-product hierarchy.
   Source Field	The source field of the baseline basis, for example, Shipped Qty or Consumed Qty.
   Start Period	The starting period of the source field.
   End Period	The ending period of the source field.
   Include Skipped	Select this field to include skipped account-product periods.
   Algorithm
   Algorithm	The algorithm, for example, Percentage Change or Trended Volume-Period. For more information about algorithms, see About SVP Algorithms.
   %Change	The percentage change from the source field to the target field. You must select Percentage Change in the Algorithm field to enter data in this field.
   Target
   Target Field	The target field of the baseline basis, for example, Baseline Basis Qty.
   Start Period	The starting period of the target field.
   End Period	The ending period of the target field.

7. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field.

   Note: If you prepare sales volume data for multiple periods and want to track the progress of the action, click the Sub Actions view tab to see the status of the periods as they are processed.

   After the fields are copied, the Status field changes to Complete and a dialog box appears, confirming that the action was successful. On the Sales Volume Planning screen, the Basis Qty field in the Category Baseline list is now populated for this product.

Generating Baseline Basis Quantities for New Products

For new products, you can copy baseline shipment or consumption data from a similar existing product to generate a baseline basis. After determining the source of the baseline basis, for example, historical shipments of a similar product, you copy these records to the new product’s baseline basis quantity.

This task is a step in Process of Establishing Baseline Basis Quantities.

To generate a baseline basis quantity for a new product

1. Navigate to the Administration - Sales Volume Planning screen, then the Copy Actions view.

2. In the Copy Actions form, create a new record.

3. From the Action field drop-down list, select Copy Product.

   Note: If you want to copy information between products, the products must be part of the same account. If products are part of the same account hierarchy but at different account levels, you cannot copy product information from an existing product to a new product.

4. Select the Apply ADL check box if you want to create records for only the accounts that are already added to the ADL (Authorized Distribution List) for the new product:

   • If no ADL is established for the new product, or if you want to sell the new product to the same accounts to which you sell the source product, leave this check box blank.

   • If you select the Apply ADL check box, the Default Value field is available, and you can enter an estimated value for those ADL accounts that do not buy or receive the source product.

5. Complete the rest of the fields in the form..

   Step 6 of Generating Baseline Basis Quantities for Existing Products describes the available fields.

6. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field.

   After the fields are copied, the Status field changes to Complete and a dialog box appears, confirming that the action was successful. On the Sales Volume Planning screen, the Basis Qty field in the Category Baseline list is now populated for this new product.

Precalculating Adjusted Baseline Basis Quantities

After you establish a baseline basis quantity, you can adjust this quantity to reflect growth or decline rates by using a percentage change algorithm or a trended volume by period algorithm.

You can precalculate changes to the baseline basis quantity. This predetermination of the quantity shows values for this data and provides you with a quick reference to the total quantity. If you think that quantity values were skipped and want to understand the source value (predetermination) for all periods (including skipped periods), select the same periods before performing the predetermination.

After making all of the needed adjustments to the baseline basis quantity, you copy the values to the baseline basis planning quantity.

This task is a step in Process of Establishing Baseline Basis Quantities.

To precalculate an adjusted baseline basis quantity

1. Navigate to the Administration - Sales Volume Planning screen, then the Copy Actions view.

2. In the Copy Actions form, create a new record.

3. In the Account field, select the account in the account-product hierarchy to use to calculate the adjusted baseline basis.

4. Select a value in the Category field or the Source Product field for the category or product in the category-product hierarchy to use to calculate the adjusted baseline basis.

   Note: You must select the Account field before you select the Category field or the Source Product field.

5. Complete the rest of the fields in the form.

   Step 6 of Generating Baseline Basis Quantities for Existing Products describes the available fields.

6. Click Calculate Source.

   The Source Value field displays the unadjusted Source field quantity, and the Target Value field displays the adjusted Source field quantity.

7. (Optional) Enter a quantity value in the Override field.

   The value in the Override field appears in the Target Value field, and the %Change field is adjusted to reflect the value in the Override field.

Note: The Override field does not depend on the values in the Algorithm field or %Change field.

Copying Baseline Information to Other Fields

The baseline quantity is the quantity of product that would have been sold without an account promotion. After establishing a baseline quantity, account managers can use this value in conjunction with the Trade Promotions module to better plan incremental quantity for account promotions. You can also use the baseline quantity to establish and generate target quantities.

When you copy baseline information to other fields in the Siebel Consumer Goods application, you can copy baseline information:

• From the Baseline Basis Qty field to the Baseline Planning Qty field.

After copying, SVP administrators release the imported SVP data to their senior managers. These managers modify the data to reflect their markets and allocate the modified quantities down the account-product hierarchy. For more information about modifying the data, see Skipping SVP Source Data (End User).

• From the Baseline Planning Qty field to the Baseline Qty field.

  After senior managers modify and allocate the baseline planning quantities, you can copy the Baseline Planning Qty field to the Baseline Qty field.

• From the Baseline Qty field to the Baseline PY Qty field.

  To establish baseline quantities for the prior year, you can copy the Baseline Qty field to the Baseline PY Qty field.

• From the Baseline Qty field to the Baseline Target Qty field.

  To establish baseline quantities for expected targets, you can copy the Baseline Qty field to the Baseline Target Qty field.

This task is a step in Roadmap for Sales Volume Planning.

To copy baseline information into other fields

1. Navigate to the Administration - Sales Volume Planning screen, then the Copy Actions view.

2. In the Copy Actions form, create a new record.

3. From the Action field drop-down list, select Copy Field.

4. Complete the necessary fields.

   The following table describes some fields.

   Field	Comments
   Description	A description of the action that creates the sales volume plan, for example, copy Baseline Basis Qty to Baseline Planning Qty.
   Account	The account in the account-product hierarchy to copy.
   Category	The category in the category-product hierarchy to copy. Select a value in the Category field or the Source Product field. You must select the Account field before you select the Category field or the Source Product field.
   Source
   Source Product	The product in the category-product hierarchy to copy. Select a value in the Category field or the Source Product field.
   Source Field	The source field to copy from.
   Start Period	The starting period of the source field.
   End Period	The ending period of the source field.
   Source Value	The source value to copy.
   Apply ADL	Select the Apply ADL check box if you want to create records for only the accounts that are already added to the ADL (Authorized Distribution List) for the new product. If no ADL is established for the new product, or if you want to sell the new product to the same accounts to which you sell the source product, leave this check box blank. For more information about Authorized Distribution Lists, see Product Distribution .
   Default Value	If you select the Apply ADL check box, the Default Value field is available. Enter a default value for those ADL accounts that do not buy or receive the source product.
   Include Skipped	Select this field to include skipped account-product periods.
   Algorithm
   Algorithm	The algorithm, for example, Percentage Change or Trended Volume-Period. For more information about algorithms, see About SVP Algorithms.
   %Change	The percentage change from the source field to the target field. You must select Percentage Change in the Algorithm field to enter data in this field.
   Override	If the target field value already exists in the database, you can use this field to specify a value that overrides that value.
   Target
   Target Product	The product in the category-product hierarchy to which a value is copied. Select a value in the Category field or the Source Product field.
   Target Field	The target field to which a value is copied.
   Start Period	The starting period of the target field.
   End Period	The ending period of the target field.
   Duration	The length of the target field from the start period to the end period.
   Target Value	The value of target. This constant target value overwrites all other values.

5. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field.

   Note: If you prepare sales volume data for multiple periods and want to track the progress of the action, click the Sub Actions view tab to see the status of the periods as they are processed.

   After the fields are copied, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Manually Entering SVP Data

Marketing administrators who want to prepare sample databases for training or testing purposes can manually enter account-product data for use in the SVP process. Manually entering this data eliminates the need to import these records.

Note: Use caution when entering this data manually. It is recommended that you establish and use a separate SVP hierarchy for training purposes.

This task is a step in Roadmap for Sales Volume Planning.

To manually enter account-product data

1. Navigate to the Administration - Data screen, then the Account Product view.

2. Enter the account-product data that you want.

Process of Performing Ongoing SVP Administrative Tasks

The following list shows the tasks that administrators typically perform for ongoing SVP administration:

• Creating SVP Periods

• Importing or Copying SVP Data

• Resetting Account and Category Levels

• Performing Periodic Aggregations

• Allocating Changes Down Multiple Levels of the Account Hierarchy

• Resetting SVP Hierarchy Levels

• Resetting SVP Hierarchy Locks

This process is a step in Roadmap for Sales Volume Planning.

Creating SVP Periods

You must create periods to represent the units of time that you work with in the SVP process. SVP supports period types of weeks or months. For information about creating periods, see Creating Periods.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

Importing or Copying SVP Data

You must import the data to use in the SVP process. You can import SVP source data into any of the standard product movement tables (baseline, target, consumption, and shipment) using Siebel Enterprise Integration Manager (EIM). Data that is imported into these tables is copied or staged to the appropriate catalog-category tables for the same product movement types. The SVP module uses predefined interface tables for importing source data. For more information, see Siebel Enterprise Integration Manager Administration Guide.

Note: SVP source data is recorded at the lowest level of your account and product hierarchies. Therefore, when importing SVP source data, you must import this data at the lowest level of your hierarchies—for example, at the Ship To-SKU level.

You can also copy SVP data from existing products to records for similar new products. You can then use this data as the source records for your upcoming SVP actions. For more information about copying SVP data from existing products to records for similar new products, see Generating Baseline Basis Quantities for New Products.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

Resetting Account and Category Levels

Resetting levels displays the current levels associated with each account that is represented in your SVP hierarchy. If you want the Account Level field to auto-populate in SVP views and forms, you must reset account and category levels. Resetting account levels allows you to view an account’s level.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

To reset Account and Category levels

1. Navigate to the Administration - Sales Volume Planning screen, then the Other Actions view.

2. In the Other Actions form, create a new record.

3. From the Action field drop-down list, select Reset Levels, and enter text in the Description field.

4. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field. After the levels in the account-product hierarchy are reset, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Performing Periodic Aggregations

You need to run Aggregate to incorporate account, category, or product changes into the SVP hierarchy. You also need to run the process to aggregate baseline data changes or to create SVP data for future periods. For information about running Aggregate, see Performing the Initial Aggregation.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

Allocating Changes Down Multiple Levels of the Account Hierarchy

If you need to allocate changes down multiple levels of the account hierarchy, use the Administration - Sales Volume Planning screen and run an Allocate action. For example, if the Vice President of Sales mandates a change in the forecast at the root account level that applies to all accounts in the hierarchy, run the Allocate action. This action pushes changes down the account hierarchy from the selected account to any of the 10 hierarchical levels. For more information about allocating changes, see Locking and Modifying SVP Data (End User) and About Category and Account Level Allocation.

When changes are made to a volume, they are automatically rolled up and pushed down the category-product hierarchy with the account node being worked on. To push the changes down to the next level of account nodes, click the Allocate button. Because the allocation process can involve updating thousands of records, the system is designed to allow end users to only allocate down one level of the account hierarchy at a time. To allocate down more than one level or to aggregate up the account hierarchy, an administrator must initiate this action from the SVP Administration view. When a value is changed at the Category Baseline level, that change must be pushed down to the Product Baseline level and converted to the other units of measure before being rolled-up back to the original category baseline level.

Sales volumes (in currency, units, cases, and so on) can be entered at any level of the account or product hierarchy and pushed down or rolled-up the hierarchy, to keep all numbers in the hierarchy in synchronization.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

Resetting SVP Hierarchy Levels

During the SVP period, you can reset the levels of an account-product tree. Perform this task if new accounts are added or if the category-product hierarchy is changed. Resetting account-product tree levels resets the account level and category level designations to reflect the updated hierarchical change. For more information, see Resetting Account and Category Levels.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

Resetting SVP Hierarchy Locks

You can reset the locks of an SVP hierarchy to allow users at lower account levels to modify SVP data. You can also reset SVP hierarchy locks if an account team lock prevents a user from modifying that user’s data, and the members of the account team cannot resolve the lock. For example, the members of the account team might be out of the office or on vacation, or a lock error might occur. Resetting SVP hierarchy locks overrides the established lock and allows other users to modify the previously locked records.

This task is a step in Process of Performing Ongoing SVP Administrative Tasks.

To reset SVP hierarchy locks

1. Navigate to the Administration - Sales Volume Planning screen, then the Other Actions view.

2. In the Other Actions form, create a new record.

3. From the Action field drop-down list, select Reset Locks, and enter text in the Description field.

4. Click Execute Action.

   In the SVP Action list, the status of Pending appears in the Status field. After the locks in the hierarchy are reset, the Status field changes to Complete and a dialog box appears, confirming that the action was successful.

Viewing SVP Data (End User)

Throughout the SVP period, sales managers view SVP data to monitor shipment or consumption quantities, gather feedback about the effectiveness of account promotions, and track their progress in meeting their targets. For more information about SVP data, see About Sales Volume Planning.

When you create a query to find data in the Category Baseline and Product Baseline lists, the query definition is applied to your subsequent selections in the Accounts and Category lists. For example, to view category baseline records for a quarter, you define the query to return results for the three months in that quarter. When you drill down to the next level, the previously defined query automatically returns records for only that quarter. Similarly, queries that you create in the Product Baseline list are applied when you select subsequent records in the Products list. For more information about creating, executing, and canceling queries, see Siebel Fundamentals.

This task is a step in Roadmap for Sales Volume Planning.

To view SVP data

1. Navigate to the Sales Volume Planning screen.

2. In the Sales Volume Planning link bar, for the data that you want to view click one of the following links:

   • Baseline. If you click this link, the Category Baseline list and Product Baseline list appear with the Accounts list, Category list, and Products list.

   • Shipment. If you click this link, the Category Shipment list and Product Shipment list appear with the Accounts list, Category list, and Products list.

   • Consumption. If you click this link, the Category Consumption list and Product Consumption list appear with the Accounts list, Category list, and Products list.

   • Target. If you click this link, the Category Target list and Product Target list appear with the Accounts list, Category list, and Products list.

   • Baseline - Flat. If you click this link, the Product Baseline - Flat list appears with the Accounts list and Category list. You can click Prior Year, Current Year, or Next Year, to see baseline data for the time period.

3. In the Accounts list, select an account.

4. In the Category list, select the root category, or drill down on the Name field hyperlink to navigate through the subcategories until you reach the level that you want to view:

   • To return to a higher level, click Go Up.

   • To return to the root, or highest-level category, click the browser Back button.

5. In the Category Baseline list, Category Shipment list, Category Consumption list, or Category Target list, select a value from the drop-down list that is next to the list buttons.

   The Period Analysis value shows data in a graphical chart by period.

6. Scroll down to the Products list, and drill down on the Name field hyperlink for a product to view the data.

7. In the Product Baseline list, Product Shipment list, Product Consumption list, or Product Target list, select a value from the drop-down list that is next to the list buttons.

   The Period Analysis value shows data in a graphical chart by period.

Skipping SVP Source Data (End User)

After importing the SVP source data, managers can make adjustments to reflect changes in the account-product hierarchy. For example, an account might no longer be part of your organization, a product might be discontinued, or a period might not apply to SVP. You make these adjustments by excluding or skipping some of the source data. You can skip data at any level of the hierarchy. For any parent records that you skip, all associated child records are also skipped. You can skip data for baseline or shipment data.

The following procedure uses shipment data as the source for the SVP process. Your company might use a different source depending upon its business requirements.

This task is a step in Roadmap for Sales Volume Planning.

To skip source data

1. Navigate to the Sales Volume Planning screen and click either of the following links, as appropriate to your needs:

   • Baseline. To view the Baseline view.

   • Shipment. To view the Shipment view.

2. In the Accounts list, select an account record.

3. In the Category list, select the product record for which you want to view shipments.

   In the Category Shipment list, the quantity of shipped product for the selected account-product pair appears

   .

4. In the Category Shipment list, select the Skip check box for each period that you want to skip.

   You can skip data at any level.

   Note: If you skip a category, all products in that category are skipped. If you do not want to skip all products in a category, you can skip at the product level.

   When the administrator aggregates this data, the periods for which you select the Skip check box are not included in the final numbers.

Locking and Modifying SVP Data (End User)

Locking allows users to modify data throughout the account-product-category hierarchy without interfering with the modifications of other users.

The SVP module offers two options for locking account-product nodes:

• Automatic locking based on the account-product node’s position in the SVP hierarchy. Any user in the account hierarchy can automatically lock a node to prevent users at lower positions in the account hierarchy from modifying their account-product nodes.

• Manual locking.

This task is a step in Roadmap for Sales Volume Planning.

Automatically Locking Account-Product Nodes

To prevent overwriting numbers, account nodes must be locked before their numbers can be edited. Locking a node prevents other people from making any modifications to any ascendant account node or any descendant account node. The SVP module uses an allocation lock process during the allocation and aggregation process. An allocation lock is a Boolean variable that is kept at the highest account level. When an allocation lock is set, the lock prevents all subordinate account levels from updating SVP data. Before an allocation lock is granted, the application checks the current account node to confirm that its upper lock is active and searches to ascertain that no allocation lock is currently held in the superior account node.

Allocation locks are maintained for the account hierarchy. In a single instance of the category-product hierarchy, all updates are allocated and aggregated immediately.

After a user completes SVP allocation-related updates, the actual allocation is invoked, and the application modifies the locks as follows:

• By updating the upper lock in the originating allocation node

• By disallowing further changes there until the user performs the Aggregate action

• Note: You can see the nodes that are locked by viewing the Allocate Lock column in the Accounts list in the Sales Volume Planning screen. You might need to manually refresh this view to see the results of a recently attempted lock request.

Locking, Modifying, and Allocating Account-Product Nodes

You can lock and unlock an account-product node manually. However, you can unlock the account-product node only if no changes are made. If changes are made, the node remains locked until one of the following actions occurs:

• The changes are allocated.

• A user performs an aggregate action, and the specific updates are aggregated up the organizational hierarchy.

The following procedure uses baseline planning quantity as an example to describe how to lock and modify account-product nodes. It also includes information about how locking and unlocking can occur automatically.

To lock, modify, and allocate the baseline planning quantity

1. Navigate to the Sales Volume Planning screen, then the Baseline view.

2. In the Accounts list, select an account record.

3. Lock the category for which you want to modify the baseline planning quantity as follows:

   • To lock the category manually, click Lock.

   • To lock the category automatically:

     • In the Category list, select the category for which you want to modify the baseline planning quantity.

     • Optionally, navigate down to the product list, and select the product for which you want to modify the baseline planning quantity.

4. Scroll down to the Category Baseline or Product Baseline list, select the record that you want to modify, and edit the fields.

   Modifying a baseline planning value automatically locks the selected account nodes when connected to the server (even if you did not click Lock in Step 3).

5. To apply the same change to multiple periods, click Mass Change, complete the fields in the Baseline Mass Change dialog box, and click Execute.

   Adjustments that you make to the baseline planning quantity affect only the products and categories in the account.

6. Perform one of the following steps to view the navigation mechanism for the Product Baseline:

   1. Navigate to a category sublevel. In the Category Baseline list, from the Category Baseline drop-down list, select one of the following values:

      • Period Analysis

      • Sub-Account Baseline

      • Sub-Category Baseline

      • Sub-Product Baseline

   2. Navigate to a product sublevel, and perform the following steps:

      • In the Category List, select a product.

      • Scroll down to the Product Baseline list, and from the Product Baseline drop-down list, select Sub-Account Baseline.

   3. In the Category Baseline or Product Baseline lists, click Refresh.

      This step is for informational purposes only to see how Step 4 and Step 5 (if executed) impact the allocation of values for an account down through the category hierarchy. The Basis% field is recalculated to reflect the new proportions of the account-product hierarchy.

7. Repeat Step 4 until you finish modifying the basis planning quantity.

8. Scroll up to the Accounts list, and click Allocate.

   The baseline planning quantity is allocated to the next lower level of the account hierarchy. When the allocate action is complete, the account-product node is unlocked. Managers at the next lower level of the account hierarchy repeat this process until the baseline planning quantity is allocated to the lowest level of the account hierarchy.

Note: If the allocation does not complete (due to pending subaction records that are not processed), then the action does not complete, and the account remains in locked mode.

About SVP Algorithms

The following two algorithms are available in the SVP module:

• Percentage Change. Modifies the source value by a percentage and populates the target proportionately. A period definition is not required.

• Trended Volume Period. Compares the value in the Trended Volume Period to the value in the Source Period to obtain a variance, and uses this variance to extrapolate the value in the target period. A period definition is required. The following table shows an example of trended volume period calculations.

Source Period	Trended Volume Period	Variance	Target Period
Start: Week 1, 1998 (Quantity:100)	Start: Week 1, 1999 (Quantity: 110)	10% increase (from source period to trended volume period)	Start: Week 1, 2000 (Quantity: 121) Apply Variance to the value in the trended volume period to obtain the value in the target period.
End: Week 2, 1998 (Quantity:100)	End: Week 2, 1999 (Quantity: 90)	10% decrease (from source period to trended volume period)	End: Week 2, 2000 (Quantity: 81) Apply Variance to the value in the trended volume period to obtain the value in the target period.

About Category and Account Level Allocation

Category and account level allocation functionality allows users to push changes down the account and category-product hierarchies in segments to allow groups of users to make subsequent changes.

Also known as intra-account allocation, category allocation occurs automatically after a user changes baseline records. It occurs in the category-product structure associated with the specific account that a user modifies. When a user makes a change and commits that change by stepping off the record, the change is pushed out through the category-product hierarchy in that account.

Trigger account level allocation using one of the following methods:

• Down one level. You can allocate changes down one level using the Allocate button in the Sales Volume Planning screen.

• Down multiple levels. Only an administrator can allocate changes down multiple levels, using the Administration - Sales Volume Planning screen.

About Allocating Changes Down One Level of Account Hierarchy

By allocating changes while in the Sales Volume Planning screen, the end user can allocate changes down one level of the account hierarchy.

Note: Category-product changes are allocated in the account immediately when the user steps off of the record.

For more information about allocating changes, see Locking and Modifying SVP Data (End User).

About the Account Allocation Level Parameter

The Account Allocation Level parameter defines the scope of an allocation. It specifies the account level in the SVP hierarchy that is used when performing an SVP allocation action. For example, to allocate two levels, navigate to the Administration - Sales Volume Planning screen, and in the Action form, click the Allocation Level drop-down arrow, and select Allocation Level 2.

Note: The parent account is always Level 1, and each subaccount level is the next sequential number. These allocation levels are specific to the SVP account hierarchy.

About Number Handling and Percentage-Basis Calculations

Various actions handle negative and decimal numbers as follows:

• Copy Field and Copy Product actions:

  • Negative source records are converted to target records with a value of zero by default. To change this behavior, set the Allow Negatives field user property to TRUE, which transfers the unaltered number.

  • Floating point decimal numbers are truncated to integer values. To change this behavior, set the Decimal Number field user property to TRUE, which transfers the unaltered number.

• Aggregation actions. Both negative and floating point decimal numbers are supported and calculated as such. All negative cases are field zeroed-out when the user enters a value.

• Allocation actions. Negative and floating point decimal numbers are zeroed-out and not supported. Floating point decimals in the SVP quantity fields are truncated such that only the integer portion of the value is taken into consideration. For currency fields, two digits after the decimal point are calculated.

The percentage basis is calculated in each SVP-specific Category list (for example, Category Baseline or Category Target) as the proportion of the record to the total value of records in the referenced list.

About Configuring Sales Volume Planning

This topic contains information that might be useful when configuring SVP features.

The procedures documented in this chapter include buttons that invoke specialized methods, as described in the following table.

Button	Method	Description	Supported On
Allocate	MthdAlloc	Changes the status of the allocate action to Pending (ready for Workflow Monitor to pick up).	Bus Comp Layer
Calculate Source	OnCalculate	Sums up the total value of the Source field that is specified between the Start and End fields.	Bus Comp Layer
Current Year	CurrentSVPYear	Displays baseline data for the current year in the Baseline - Flat view.	Bus Comp Layer
Execute	MassChange	Finds all Baseline or Target records with a period between the start period and end period, then updates the field specified with Value according to the Algorithm Type. For Percentage Change, the new value is (1 plus Value divided by 100) multiplied by old value; for Flat Change, the new value is Value.	Applet Layer
Execute Action	OnExecute	Changes the status of actions from Initialized to Pending (ready for the Workflow Monitor to pick up).	Bus Comp Layer
Save to File	CreatePopup	Exports selected columns from the SVP screen to an Excel spreadsheet.	Applet Layer
Load from File	LoadFromFileInBusComp	Imports selected columns in an Excel spreadsheet to the SVP screen.	Applet Layer
Lock	mthdlock	Locks a node and makes the node modifiable.	Bus Comp Layer
Mass Change	ShowPopup	Opens a dialog box that displays the following options: Algorithm type Field Value Period Start Period End The dialog box also contains the Execute button.	Applet Layer
Next Year	NextSVPYear	Displays baseline data for the next year in the Baseline - Flat view.	Bus Comp Layer
Prior Year	PriorSVPYear	Displays baseline data for the prior year in the Baseline - Flat view.	Bus Comp Layer
Refresh	OnRefresh	Refreshes the form and recalculates the planning percentages.	Bus Comp Layer
Skip All	SetAll	Sets the Skip flag to True.	Bus Comp Layer
SVP Adopt	mthdAdoptSVPParent	Adopts categories in a hierarchy and makes them a part of the SVP category hierarchy.	Bus Comp Layer
Unlock	mthdUnlock	Unlocks a node and makes the node not modifiable.	Bus Comp Layer

Configuring Sales Volume Planning

To configure sales volume planning, perform the following tasks:

1. Setting Up Siebel Workflow Processes for Consumer Goods

2. (Optional) Modifying the SVP Business Service

3. (Optional) Configuring SVP Category Aggregation and Mass Change

Modifying the SVP Business Service

You can modify the SVP business service. For example, you might want the business service to send an email message to alert the system administrator when the workflow process is complete. This alert eliminates the need for the system administrator to monitor the entire process.

Caution: Do not attempt to modify the SVP workflow process.

To modify the SVP business service

1. Navigate to the Administration - Business Process screen, then the Workflow Processes view.

2. In the Workflow Processes list, click Query.

3. In the Process Definition form, enter CG SVP Process in the Name field.

4. Click Go.

5. Drill down on the Name field hyperlink for the CG SVP Process that is active.

   The Workflow Process Designer view appears. You can use the graphical flowchart tool in this view to modify the business service. For more information about using Siebel Business Process Designer, see Siebel Business Process Framework: Workflow Guide.

Configuring SVP Category Aggregation and Mass Change

To view the SVP data in units, Gross Revenue, and Net Invoice Revenue, use SVP Category Aggregation in the Consumer Goods application. SVP Category Aggregation enables the user to specify those fields that are linked back to SVP from the promoted products in the plans through user properties for business components. Before you can use Category Aggregation, you must enable it using Siebel Tools. For more information about promoted products, see Trade Promotions .

The Mass Change button allows you to perform an update on the Baseline Planning Currency and the Baseline Planning Qty fields for Category Baseline records. You can make other fields visible in the Field drop-down list in the Mass Change dialog box and enable Mass Change functionality on custom fields.

Configuring Baseline Custom Fields for Category Aggregation

You can add a custom baseline field to the category aggregation process. This field must be based on an extension column.

To configure a custom baseline field for category aggregation

1. Log in to Siebel Tools.

2. Create the column for the custom field in the applicable tables (S_PROD_BASELINE and S_CG_CAT_BASELN) by performing the following steps:

   1. In the Object Explorer, select the Table object, and in the Object List Editor, query for the applicable table

   2. In the Object Explorer, select the Column child object, and create the column.

   3. Click Apply/DDL, select the Apply action, and click OK.

   For more information about extending columns in tables, see Configuring Siebel Business Applications.

3. Create the custom field in the following business components:

   • CG SVP Product Baseline

   • CG SVP Product Baseline - Aux

   • CG SVP Product Baseline - for Adding Data

   • CG SVP Category Baseline

   • CG SVP Category Baseline - Aux

   • CG SVP Category Baseline - for Adding Data

   To create the custom field, perform the following steps:

   1. In the Object Explorer, select the Business Component object, and in the Object List Editor, query for the business component.

   2. In the Object Explorer, select the Field child object, and create the custom field.

4. Create the list column for the custom field in the following applets:

   • CG SVP Product Baseline List Applet

   • CG SVP Category Baseline List Applet

   • CG SVP Account Product Baseline List Applet

   • CG SVP Account Category Baseline List Applet

   To create the list column, perform the following steps:

   1. In the Object Explorer, select the Applet object, and in the Object List Editor, query for the applet.

   2. In the Object Explorer, select the List child object, select the List Column child object, and create the list column for the custom field.

5. Create the user property for the custom field in the CG SVP Product Baseline-Aux business component by performing the following steps:

   1. In the Object Explorer, select the Business Component object, and in the Object List Editor, query for the CG SVP Product Baseline-Aux business component.

   2. In the Object Explorer, select the Business Component User Prop child object, and create a new user property with a name of the next available Build Tree name (for example, Build Tree 10) and a value of the custom field name.

   Note: You can use the Category Aggregation Field user properties to configure category aggregation for custom fields.

6. Deploy your changes to the Siebel Runtime Repository.

Using Category Aggregation

When it is enabled, you can use category aggregation to link fields back to SVP from the promoted products in the plans.

Note: A sales volume planning shipment record can be associated with many promoted products. However when an SVP shipment record is associated with a promoted product, no adjustment in shipment quantity is made for other promoted products with which the shipment record is associated. Therefore, each promoted product has the full shipment quantity associated with it.

To link fields back to SVP from the promoted products

1. Navigate to the Sales Volume Planning screen.

2. In the Accounts list, query for and select an account for which you want to link SVP fields back to the promoted products.

   Note: Account promotions with promoted categories, promoted products, and attributes must exist. For more information about account promotions, see Trade Promotions

3. In the Category list, select the required category, and scroll down to the Category Baseline list.

4. Click Calculate.

Making Extra Fields Available for Mass Change

You can update extra fields using the Mass Change button by adding new entries to the SVP Source LOV. After you add these extra fields, you can perform a mass change on these fields as described in Locking and Modifying SVP Data (End User).

To make extra fields available for mass change

1. Navigate to the Administration - Data screen, then the List of Values view.

2. In the List of Values list, create a new record. Repeat this step for all extra fields that you want to add.

   The following table describes some fields.

Field	Comments
Type	Enter SVP Source.
Display Value	The display value of the field that you want to add.
Language-Independent Code	The LIC of the field that you want to add.
Order	The order that you want the field to appear in the drop-down list.