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

About Bulk Request Processing Logic

This topic describes the effects of Siebel Order Management for Industry Applications processing logic on bulk quotes or bulk orders generated by bulk requests.

Before creating bulk quotes or bulk orders for a bulk request, the processing logic recognizes any open quotes or orders for the base products in that bulk request.

For example, if an open quote or order exists to add a component for a customer, and if you delete that component for that customer in the bulk request, then the processing logic recognizes the component as a customer asset before creating the bulk quote or bulk order. The resulting bulk quote or bulk order includes a line item to delete that component. This follow-on quote or order is a change to the asset before the asset is fulfilled.

Also, for example, if an open order exists to disconnect an asset for a customer, and if you update that asset in the bulk request, then a run-time error occurs. This is because you cannot update an asset that will be disconnected.

A bulk quote or bulk order can include a complex line item for a base product in the bulk request. Complex line items contain additional line items for the actions and component products applicable to the base product. Identical action codes and component products for a base product in a bulk request are combined into a single line item in the bulk quote or bulk order.

Unspecified Line Items in a Bulk Quote or Order

A bulk quote or bulk order can include component line items that you do not specify in the bulk request under any of the following circumstances:

• Exclude constraint. In the bulk request, you select a component with an exclude constraint. For example, if a customer wants component A, then the customer cannot also have component B. If you add component A to a bulk request for a customer who currently has component B, then the resulting bulk quote or bulk order automatically includes a line item to delete component B, even though you do not delete component B in the bulk request for the customer.

  CAUTION:  If you delete the BatchValidate step in the ABO Bulk Request - Add Sub-Process Workflow or the ABO Bulk Request - Modify Sub-Process Workflow, then the exclude constraint has no effect. Consequently, in this example, the resulting bulk quote or bulk order does not automatically include a line to delete component B. Additionally, deleting the BatchValidate step can result in incorrect and inconsistent quotes or orders, because no rule of the iLog engine is applied to the quotes or orders.

  Bulk requests do not use the eCfg API to create child items or to modify attributes. In a bulk request, you can define actions for background processing as you can in Siebel Configurator. However, Siebel Configurator runs product scripts that are part of the product description, while bulk ordering does not. Only the validation step at the end of the bulk request process runs Cfg_InstInitialize.

• Require constraint. In the bulk request, you select a component with a require constraint. For example, if a customer wants component A, then the customer must also have component B. If you add component A to a bulk request for a customer who does not currently have component B, then the resulting bulk quote or bulk order automatically includes a line item to add component B, even though you do not add component B in the bulk request for the customer.

  CAUTION:  If you delete the BatchValidate step in the ABO Bulk Request - Add Sub-Process Workflow or the ABO Bulk Request - Modify Sub-Process Workflow, then the require constraint has no effect. Consequently, in this example, the resulting bulk quote or bulk order does not automatically include a line to add component B.

• Parent component. In the bulk request, you select a component with a parent component. For example, component B is the parent component of component A. If you add component A to a bulk request, then the resulting bulk quote or bulk order automatically includes a line item for component B, even though you do not select component B in the bulk request. However, the line item for component B has no action code in the bulk quote or bulk order.
• Default component. In the bulk request, you select a base product with a default component. For example component B is a default component of base product A. If you add base product A to a bulk request, then the resulting bulk quote or bulk order automatically includes a line item for component B, even though you do not select component B in the bulk request. However, the line item for component B has no action code in the bulk quote or bulk order.