Siebel Order Management Guide Addendum for Communications > Employee Asset-Based Ordering > Process of Managing Bulk Requests >

Adding Bulk Request Data Manually

To add action sets, instances, and actions to a bulk request manually, follow the procedures in this topic.

NOTE:  When you copy a bulk request record to create a new bulk request, the action sets, contacts, services, and actions for the original bulk request are copied to the new bulk request, if your company has enabled this functionality by setting the value of the Enable ACR499 BulkRequest system preference to Y.

This process is a step in Process of Managing Bulk Requests.

Adding Action Sets to a Bulk Request

An action set identifies an account for which to run the bulk request. To add action sets to a bulk request, follow this procedure.

NOTE:  If you copy an action set to create a new action set, then the instances and actions for the old action set are copied to the new action set.

To add action sets to a bulk request

1. Navigate to the Bulk Requests screen, then the Bulk Requests List view.
2. Find a bulk request for which to add action sets, instances, and actions.
3. Click the link in the Request Name field.

   The Action Sets view, Users & Actions subview appears. The Bulk Request form appears first on the screen. After the Bulk Request form, lists of action sets, instances, and actions appear.

4. In the Action Sets list, add an action set for the new bulk request and complete the necessary fields.

   Some fields are described in the following table.

   Field	Description
   Sequence	The order in which the action set is processed. The sequence number is automatically generated, and you cannot change this field. By default, action sets for a bulk request are processed asynchronously by available workflow process managers when you submit the bulk request to create a bulk quote or a bulk order. The sequence number is used in processing to pass action sets to available workflow process managers or if you process action sets sequentially (synchronously). For more information about processing action sets synchronously, see (Optional) Changing Processing for Action Sets.
   Type	The type of action set. Select one of the following values: New. Creates line items with Add actions. Select this value to add products, bundled promotions, or services. An action set, when processed, generates either an order or a quote, depending on the Mode value in the bulk request header. After an order or quote is created, the asset-based ordering cycle must be followed to generate an asset. Modify. Changes an existing asset. Select this value to update products and services for an asset, suspend services for an asset, resume services for an asset after suspension, or delete obsolete products and services for an asset. Upgrade. Upgrades an asset. Select this value to upgrade existing assets.
   Account	The customer account for the action set.
   Service Account	The service account for the action set.
   Due Date	By default, displays a date that is one week from today. The value in this field populates the Due Date fields of the bulk quote or bulk order that this action set creates.
   Active	If you want to bypass the action set when you submit this bulk request for processing, then deselect the check box to set the field to N.
   File Name	The name of the template file that was imported to create the action set. This field has a value only if you import bulk request data. For more information about importing bulk request data, see Importing Bulk Request Data from a Template File.
   Comment	A description of the action set.
   Child Type	The type of instances to associate with this action set. The fields in the Instances list change dynamically with the value selected in this field. Select one of the following values: Contact ID. The instances are contacts that are associated with the account specified in the Account field of this action set. The bulk request will act on all assets associated with the contacts in the Instances list. Service ID. The instances are services that are associated with the account specified in the Account field of this action set. The bulk request will act on all assets associated with the services in the Instances list. Agreement ID. The instances are agreements. The bulk request will act on all assets associated with the agreements in the Instances list. Network ID. The instances are networks. The bulk request will act on all assets associated with the networks in the Instances list.
   Scope	Identifies the assets that are included in or excluded from the bulk request. Values include the following: All. For the account in the action set, include all assets associated with the instances for the account. If you select this value, then you cannot specify individual instances. Include. For the account in the action set, select this value to include only the assets identified by the instances that you specify in Adding Instances to a Bulk Request Action Set. Exclude. For the account in the action set, select this value to include all assets associated with the account except for the assets identified by the instances that you specify in Adding Instances to a Bulk Request Action Set. NOTE:  The scope of assets is governed by the Child Type value. If, for example, the Child Type value is Contact ID, then a Scope value of All means all contacts for the account in the action set.
   Status	Read only. Processing status of the action set. Values include the following: To Process. Processing is not yet started because the bulk request has not been submitted. Partially Processed. Processing is complete, but some of the data in the action set was not processed to create the bulk quote or bulk order. Processed. Processing is complete, and all data in the action set was processed to create the bulk quote or bulk order. Error. Processing failed because of an error.
   Valid	Read only. Validation status of the action set. An action set is evaluated against validation rules when you click Validate or Submit in the Bulk Request form. Values include the following: Y. The action set complies with validation rules. N. The action set does not comply with validation rules, or the action set has not yet been evaluated against validation rules.

Adding Instances to a Bulk Request Action Set

An instance specifies a contact, asset, network, or agreement to which to apply a bulk request action. To add instances to a bulk request action set, follow this procedure.

To add instances to a bulk request action set

1. In the Action Sets list, select an action set to which you want to add instances.
2. In the Instances list, add the instances that are applicable to the action set by performing one of the steps listed in the following table.

   If the Child Type of the action set is...	Then go to...
   Contact ID	Step 3
   Service ID	Step 4
   Agreement ID	Step 5
   Network ID	Step 6

3. Add contacts to the action set by completing the following actions.
   1. Perform one of the following actions:
      • To add a single contact, click New and, in the new contact record, complete the Email Address field.
      • To add a single contact, click New and, in the Email Address field of the new instance, click the select button, select a contact in the Add Contact dialog box, and click OK.
        
        The fields in the instance are populated from the selected contact record.
      • To add multiple contacts, click Add Users, select the contacts in the Add Users dialog box, and click Add Selected.

        The Add Users dialog box lists all contacts, and is not constrained to the contacts belonging to the selected account. This is because, when you import a template XML file, your Siebel application is configured to accept all imported contacts to generate instances. When the bulk request is processed or validated, invalid contacts will generate errors and can be removed at that stage.

   2. (Optional) To bypass this instance when you submit this bulk request for processing, deselect the check box in the Active field of the instance to set the field to N.

      NOTE:  If the value of the Active field of the action set is N, then this value supersedes any Y values in the Active fields of instances associated with that action set.

   3. Go to Step 7.
4. Add services to the action set by completing the following actions.
   1. If the Instances list contains no data, then click New to display the fields in the Instances list relating to services.
   2. Perform one of the following actions:
      • To add a single service, click New and, in the Service Id field of the new instance, click the select button, select a service in the Add Service dialog box, and click OK.
        
        The fields in the instance are populated from the selected service record.
        
        If the value of the Type field in the action set is New, then the select button in the Service Id field is not available. This is because you are creating a new asset, and therefore you cannot select the service ID for an existing asset. In this case, enter a service ID for the new asset manually.
      • To add multiple services, click Add Instances, select the services in the Add dialog box, and click Add Selected.
        
        If the value of the Type field in the action set is New, then the Add Instances button is unavailable. This is because you are creating a new asset, and therefore you cannot select existing assets.

        The Add dialog box lists all services, and is not constrained to the services belonging to the selected account. This is because, when you import a template XML file, your Siebel application is configured to accept all imported services to generate instances. When the bulk request is processed or validated, invalid services will generate errors and can be removed at that stage.

   3. (Optional) To bypass this instance when you submit this bulk request for processing, deselect the check box in the Active field of the instance to set the field to N.

      NOTE:  If the value of the Active field of the action set is N, then this value supersedes any Y values in the Active fields of instances associated with that action set.

   4. Go to Step 7.
5. Add agreements to the action set by completing the following actions.
   1. If the Instances list contains no data, then click New to display the fields in the Instances list relating to agreements.
   2. Perform one of the following actions:
      • To add a single agreement, click New and, in the Agreement Name field of the new instance, click the select button, select an agreement in the Add Agreement dialog box, and click OK.
        
        The fields in the instance are populated from the selected agreement record.
      • To add multiple agreements, click Add Agreements, select the agreements in the Add Agreements dialog box, and click Add Selected.

        The Add Agreements dialog box lists all agreements, and is not constrained to the agreements belonging to the selected account. This is because, when you import a template XML file, your Siebel application is configured to accept all imported agreements to generate instances. When the bulk request is processed or validated, invalid agreements will generate errors and can be removed at that stage.

   3. Go to Step 7.
6. Add networks to the action set by completing the following actions.
   1. If the Instances list contains no data, then click New to display the fields in the Instances list relating to networks.
   2. Perform one of the following actions:
      • To add a single network, click New and, in the Network field of the new instance, click the select button, select a network in the Add Network dialog box, and click OK.
        
        The fields in the instance are populated from the selected network record.
      • To add multiple networks, click Add Networks, select the networks in the Add Networks dialog box, and click Add Selected.

        The Add Networks dialog box lists all networks, and is not constrained to the networks belonging to the selected account. This is because, when you import a template XML file, your Siebel application is configured to accept all imported networks to generate instances. When the bulk request is processed or validated, invalid networks will generate errors and can be removed at that stage.

7. Step off the record to save it.

Adding Actions to a Bulk Request Action Set

An action specifies an operation to perform on the instances associated with a bulk request action set. To add actions to a bulk request action set, follow this procedure.

To add actions to a bulk request action set

1. In the Action Sets list, select an action set to which you want to add actions.
2. In Actions list, add the actions applicable to the action set in the exact order in which the actions are to be processed on each product, and select a base product, by performing one of the following actions:
   • To add an action for a single base product, click New and, in the new action record, select a product in the Base Product field.
   • To add actions for multiple base products, click Add Items, enter a quantity for each product in the Pick Products dialog box, click Add to display the added products at the end of the dialog box, and click OK to add those products.

     The Add Items button is available only if you select New in the Type field of the action set.

3. Continue to fill in the fields of the action record, as required.

   Some fields are described in the following table.

   Field	Comments
   Sequence	The number in the Sequence field records the order in which action records are entered. The Sequence number is automatically generated and read only. CAUTION:  The Sequence number is significant when you specify more than one action for the same product. For example, because a product must exist before you can update the product, the sequence number for an action that adds a product must be lower than the sequence number for an action that updates an attribute for that product. If you add the actions for a product in an incorrect order, then you must delete those actions and add them again to reorder them.
   Action Code	Identifies an action to perform on the assets listed for the associated action set. Values include the following: Add. Adds a new product or service for an asset. Update. Changes the product or service for an asset. Suspend. Suspends the service. Resume. Resumes the service after suspension. Delete. Disconnects a product or service. Upgrade. Upgrades an asset (product or service) or a promotion to a newer or improved version of the asset, or to a different promotion. Replace. Replaces an asset (product or service) with a different product or service.

   Note the following restrictions on Action Code field value selection:

   • When you add a single base product, though you can select any action code, the value in the Type field of the action set determines the valid Action Code values. If you select an invalid Action Code value, then an error (exception) occurs when you submit the bulk request.

     The following table shows the Action Code values that are valid for each action set Type value.

     Action Set Type	Valid Action Codes
     New	Add, Update NOTE:  Add must come first. A subsequent Update can update the fields of a base product added by Add.
     Modify	Add, Update, Suspend, Resume, Delete, Replace
     Upgrade	Upgrade

   • When you add multiple base products by using the Add Items button, the Action Code value for each base product is Add, and is read only.

     The Action Code value that you select determines the other fields in that action in which you can enter data. In the following table, Yes indicates that you can enter data in the field for the Action Code value, and No indicates that you cannot enter data in the field for the Action Code value.

Note the following exceptions for field entries:

• When you click the Add Items button to add multiple base products, the quantity that you selected in the Pick Products dialog box is carried over to the quote or order line items.
• When the action set Type value is Modify, a promotion can be attached to a promotion component. In this case, Field Name is set to Prod Prom Name, and Field Value is set to the name of the promotion.

4. Continue filling in the fields of the action record, as required.

   Some fields are described in the following table.

   Field	Comments
   Component Product	Select a single component product to associate with this action. You can enter a component product if you have selected an Action Code of Add, Update, or Delete, and if the base product or promotion has components. You cannot enter a component product for an Action Code of Upgrade, or for an Action Code of Add if you have used the Add Items button to create the action. To enter multiple component products, go to Step 5.
   Product Path	When you select a component product, this field is automatically populated for the component product. This field uses two vertical lines (||) to separate relationships (that is, ports), and two colons (::) to separate instances from the domain from the product model.
   Attribute Name	For an Action Code value of Update, select the applicable attribute name. If you select a component product, then only the attributes applicable to that component product are available for selection. If you do not select a component product, then only the attributes applicable to the base product are available for selection.
   Attribute Value	For an Action Code value of Update, enter the applicable attribute value for the selected attribute.
   Field Name	For an Action Code value of Update, select the applicable field. If you click the Add Items button to add multiple base products, then this field displays Quantity, and is read only. The available field names are the fields in the ABO Bulk Request Action Field Names business component. You can add new values by modifying this business component.
   Field Value	For an Action Code value of Update, enter the applicable field value for the selected field. If you click the Add Items button to add multiple base products, then this field displays the quantity that you select in the Pick Products dialog box, and is read only.
   Upgrade Product	Select an upgrade product for an Action Code value of Upgrade.
   Active	If you want to bypass this action when you submit this bulk request for processing, then deselect the check box to set the field to N. If the value of the Active field of the action set is N, then this value supersedes any Y values in the Active fields of actions associated with that action set.
   Upgrade Promotion	Select a promotion for an Action Code value of Upgrade.

5. To select multiple component products, perform the following steps.
   1. Click Customize.

      Siebel Configurator is launched and a separate configuration window appears.

   2. In the configuration window, select component products and attributes as you would in customizing a product for a quote or an order.

      For more information, see the chapter on creating a quote or sales order in Siebel Order Management Guide.

   3. Click Done.
   4. In the Action Template, click the Action Sets tab to return to the bulk request.

      The Customize button is available for selection for an Action Code value of Add or Upgrade, and if the applicable product has components. If you select an Add action code, then you can specify product components for the base product. If you select an Upgrade action code, then you can specify product components for the upgrade product.

      You can also select available attributes and fields when you click the Customize button. The component products, attributes, and fields that you select using the Customize button do not appear in the action record.

      If you use the Customize button to select component products, attributes, and fields, then Customize creates a template quote or order in the background. To this template, Customize adds the customizable product along with the configuration lines that you added in Siebel Configurator. You can click the link in the Base Product field to display the Action Template view containing the selected component products, attributes, and fields.

6. Repeat Step 2 through Step 5 for each action in the bulk request.

CAUTION:  After customizing products, do not change the value in the Mode field of the bulk request header (from Quote to Order or from Order to Quote). Changing this value can cause loss of your customizations or other undesired results.