Siebel Order Management Guide Addendum for Communications > Employee Asset-Based Ordering > About Bulk Request Processing >

About Exception Data in Bulk Requests

The bulk request functionality evaluates the validity of the action sets, instances, and actions. The bulk request functionality also enforces eligibility and compatibility rules. Violations are shown in the Bulk Requests screen, Exceptions view. If errors occur during an Explode action, then these errors are also logged in the Bulk Requests screen, Exceptions view. For more information about the Exceptions view, see Managing Exception Data in a Bulk Request.

Action Set Exception Types

Some exceptions that can occur in bulk request processing of action sets are as follows:

• The service account associated with the action set is not valid.
• The service account is not a child of the customer account.

If an action set fails validation, then the associated instances and actions are not evaluated.

Instance Exception Types

Some exceptions that can occur in bulk request processing of instances are as follows:

• The contact does not exist.
• The contact is not associated with the customer account or the service account specified in the action set.
• The asset does not exist.
• The configuration of the asset violates product definition constraints.
• An unprocessed order exists to disconnect the asset.

Action Exception Types

Some exceptions that can occur in bulk request processing of actions are as follows:

• The component to be deleted or updated does not exist in the asset.
• The value of the Attribute Name to update is not valid.

Eligibility and Compatibility in Bulk Requests

Your Siebel application enforces eligibility and compatibility rules for bulk requests. An eligibility check is performed when a user selects a product. Eligibility and compatibility checks are run when a user submits the bulk request.

In the Action Sets view, Actions list, the bulk request functionality evaluates eligibility in the Base Product and Upgrade Product fields in pre-pick mode. Consequently, only eligible products are available for selection in those fields. Child component eligibility is evaluated when the bulk request is submitted. Likewise, compatibility is evaluated when the bulk request is submitted. However, no eligibility or compatibility checks occur in the Action Set Template view, Actions list.

The levels of eligibility and compatibility enforcement are as follows:

0. No eligibility or compatibility checks occur.

1. Creation of quotes and orders with ineligible products is allowed. Eligibility comments are displayed as exception records. Additionally, eligibility and compatibility messages and status values are carried over to the bulk request-generated quotes and orders.

2. Creation of quotes, orders, quote line items, and order line items is only allowed for eligible products. Ineligible items are removed from the bulk requests. If none of the added products meet eligibility and compatibility rules, then an exception is generated and the bulk request is not completed.

You can set the enforcement level in the Eligibility Display Mode parameter. For more information, see the chapter on eligibility and compatibility in Siebel Product Administration Guide.

About Controlling Eligibility and Compatibility Calls

You can control the eligibility and compatibility calls by setting the properties shown in Table 21 in the respective Synchronize steps of the ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow and the ABO Bulk Request - Inclusive Process Action Sub-Process Workflow.