Siebel Consumer Sector Guide > Sales Volume Planning > Initial SVP Administrator Procedures >

Setting Up a Category-Product Hierarchy

You must establish an explicit category-product hierarchy before beginning the sales volume planning process. Categories and products that are participants in sales volume planning must have a single designated sales volume planning parent category.

To set up a category-product hierarchy

1. Navigate to the Administration - Catalog screen > SVP Categories view.
2. In the All Categories list, create a new record and complete the necessary fields.

   Some fields are described in the following table.

   Field	Comments
   Category Name	The name of the category in the category-product hierarchy.
   Parent SVP Category Name	The parent sales volume planning name of the category (for example, All Products). This field is automatically populated when category-subcategory relationships are established later.
   SVP Level	The sales volume planning level of the category. This field is automatically filled in when an association to a subcategory is made.
   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 associated with category-product hierarchy.

3. Repeat Step 2 until all categories are specified.
4. In the All Categories list, select the root category.
5. Drill down on the Category Name field hyperlink.

   The SVP Category Details view appears.

6. In the Sub-Categories list, select the subcategory or subcategories for which you will designate the parent category as its SVP parent.

   NOTE:  It is possible for many subcategories to be designated SVP adoptees for the SVP parent. However, if a subcategory already has another category as its SVP parent, this designation ends the previous SVP parent relationship and creates a new one.

Associating Products to Categories

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

CAUTION:  Even though adding products to the upper levels of the category hierarchy is possible, it is not a recommended activity and is not enforced during SVP Actions.

To associate products with categories

1. Navigate to the Administration - Catalog screen > SVP Categories view.
2. Drill down on the Category Name field hyperlink for a selected category.

   The Subcategory list appears.

3. In the Subcategories list, drill down on the Name field hyperlink. Click the hyperlink until you reach the lowest level sub-category.

   The SVP Category Details form appears.

4. In the Products list, add a new record.
5. In the Add Internal Products dialog box, choose a product or products and click Add.
6. In the Products list, select the product or 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 mark. 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 will not appear in sales volume planning that concerns the parent category.

   NOTE:  If products to category links are created through other methods (that is, externally to the Siebel application), then you will need to perform an Acquire Categories action to create the associations. Please see Acquiring Categories for more details.

Acquiring Categories

Associating products to categories as described in Associating Products to Categories creates the links required by the Siebel application to enable the Allocation process. If you choose to make these associations through another method (that is, external to the Siebel application), you will need to perform an Acquire Categories action to establish these links. You must perform this action whenever changes are made to the Category-Product hierarchy.

To perform the Acquire Categories action

1. Navigate to the Sales Volume Planning Administration screen.
2. Click the Other Actions view tab.
3. In the Other Actions form, create a new record.
4. From the Action Type field drop-down list, select Acquire Categories.
5. Fill in the Description field. For example, Fall Forecast - Acquire Categories.
6. Click Execute Action.

   The Status changes to Pending. After the categories are acquired, the Status changes to Complete and a dialog box appears, confirming that the action was successful.

Deleting Products and Categories

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

To unadopt a Product

1. Navigate to the Administration - Catalog screen > SVP Categories view.
2. Drill down on the Category Name field hyperlink for a selected category.

   The Subcategory list appears.

3. In the Subcategories list, drill down on the Name field hyperlink until you reach the lowest level sub-category.
4. In the Products list, select the product or products you want to delete.
5. Click SVP Adopt.

   The check mark in the SVP Adoptee field of the selected product is automatically removed. This product is no longer active for the parent category in sales volume planning functions.

   NOTE:  If you do not delete products and categories through the method described here, then the Acquire Categories action must be run to make sure that the Allocation functionality works correctly within the new hierarchy. The Acquire Categories action can also be run to synchronize the category-product hierarchy when inconsistencies have been introduced through error. Failing to keep this hierarchy synchronized will adversely affect the Allocation process and functionality.

Importing Workflow Processes into Siebel Workflow Manager

Depending on your current implementation, you may need to import workflow processes into Siebel Workflow Manager.

To import workflow processes into Siebel Workflow Manager

1. Navigate to the Administration - Business Process screen.
2. In the Workflow Processes list, click Menu and choose Import.

   The Workflow Process Import dialog box appears.

3. Click Browse and navigate to CG SVP Process.xml.
4. Click Open.

   In the Workflow Processes list, CG SVP Process.xml appears.

   NOTE:  Consult your technical account manager before modifying CG SVP Process.xml.

Enabling Siebel Workflow Manager

Siebel Workflow Manager must be enabled before you can begin the sales volume planning process. If Siebel Workflow Manger is not already enabled, you must complete the following procedure. If Siebel Workflow Manager is already enabled, you can skip the following procedure and begin generating triggers in Siebel Workflow Manager.

To enable Siebel Workflow Manager for sales volume planning

1. Navigate to the Administration - Server Configuration screen > Enterprises view.
2. In the Component Groups list, select the record containing Workflow Management, click Menu, and then choose Enable Component Group.
3. Click the Synchronize view tab.
4. In the Synchronize list, click Synchronize.

   NOTE:  If Siebel Workflow Manager has not previously been enabled, you may need to stop and restart the server.

Generating Triggers in Siebel Workflow Manager

The Generate Trigger (GenTrig) component on the Siebel Server allows you to create database triggers. Policy Manager uses these database triggers to identify records that may match policy conditions. Generate Triggers needs to be regenerated whenever you create or delete new policies.

To generate triggers in Siebel Workflow Manager

1. Navigate to the Administration - Server Management screen > Jobs view.
2. In the Jobs list, click New.
3. From the Component/Job drop-down list, select Generate Triggers.

   Selecting Generate Triggers creates a new line entry but does not start the task.

4. In the Job Parameters list, click New to modify parameter settings.

   The component-specific parameters for Generate Triggers are in Table 12.

5. Enter your Privileged User name and password.
6. In the Job Detail form applet, click Menu and choose Start Job.
7. To view changes to the state, refresh the screen by clicking Menu and choosing Run Query.
8. Upon completion, the Status field contains either Success or Error.

   It is recommended that you view the log details.

   Table 12.  Component-Specific Parameters for Generate Triggers

   Name	Value	Description
   Remove	TRUE or FALSE (default)	Set to TRUE to generate "DROP TRIGGER" statements to clean up the triggers. Remove does not generate "CREATE TRIGGER" statements.
   Trigger File Name	Valid filename on the Siebel Server	Name and output location for the SQL script file. The default is TRIGGER.SQL. The file is created in the root directory of the Siebel Server during installation.
   EXEC	TRUE or FALSE (default	Determines if the SQL script file runs automatically or manually. If TRUE, the SQL script file runs automatically. EXEC should be set to FALSE if you are running a Sybase server (all Siebel versions) or MS_SQL server (Siebel versions 4.x). This is to prevent connected users from getting an error message when Siebel generates database triggers. Make sure that no one is logged in to the database before you generate triggers. Also, if you are creating a large number of triggers because there are too many workflow policies, the triggers should be applied by the user and not by the Generate Triggers server process. The Exec parameter should be set to FALSE in this case.
   Mode	ALL or WORK or ASGN	Set to ALL to create both Workflow Policy triggers and Assignment Manager triggers. Set to WORK to create only Workflow Policy triggers. Set to ASGN to create only Assignment Manager triggers.
   Privileged User Name/ Privileged User Password	Assigned Privileged User name and password	All users must enter a Privileged User name and password. The Table Owner is considered a Privileged User, so you may enter the Table Owner name and password in the Privileged User name and password fields.

Starting Workflow Monitor Agent Components

You need to start Workflow Monitor Agent to execute your policies. Workflow Monitor Agent checks to see when the conditions of policies are met.

To stop or restart a Workflow Monitor Agent component

1. Navigate to the Administration - Server Management screen > Jobs view.
2. In the Jobs list, click New.
3. From the link bar, click Servers.
4. Click the Component Groups tab.
5. In the Components list, select the component you would like to stop or restart, then click Shutdown or Startup.

   NOTE:  For more information on Workflows see Siebel Business Process Designer Administration Guide.