Siebel Order Management Guide Addendum for Communications > Workflows for Employee Asset-Based Ordering > Workflows for Bulk Requests >

ABO Bulk Request - Upgrade Sub-Process Workflow

This workflow creates an order line item when the consolidated action is Upgrade. To upgrade an asset, this workflow deletes the old products for the asset and adds the new products for the asset. To create the order line items for the upgraded asset, this workflow cycles through the existing components of the asset, adds these components as new order line items, and copies the existing field and attribute values for these components to these new order line items. This workflow adds new configured components to the asset and uses attributes for these new configured components on the new order line items. Figure 65 shows this workflow.

The ABO Bulk Request - Inclusive Process Action Sub-Process Workflow and the ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow call this workflow as a subprocess when the action code is Upgrade.

Figure 65. ABO Bulk Request - Upgrade Sub-Process Workflow

Workflow Description. This workflow performs the following actions:

1. Build Instance Asset. This step calls the BuildInstanceAsset method of the ABO Bulk Request Processing Service business service and queries the Product ID field of the assets to load the asset records to upgrade.
2. Asset(s) Exists? This decision step checks if any assets were loaded in the previous step.
3. Next Asset. This step calls the NextObject method of the ABO Bulk Request Processing Service. From the instance asset records created in the previous step, this step loads into memory the next asset to upgrade.
4. Is Null. This decision step checks if there are any other assets for processing, If not, it routes the flow to step Exception? If so, it routes the flow Set Requested Product Instance.
5. Exception? This decision step checks if there are any exceptions in the processing. If so, it routes the flow to Is RAF. If not, it routes the flow to End.
6. Is RAF. This decision step checks if the flow is called from an RAF flow. If so, it sets the exception error message by routing the flow to Stop. If not, it routes the flow to Process Exception, where the exception is synchronized to the database before going to End.
7. Process Exception. If exceptions exist, this step uses the WriteException method of the ABO Bulk Request Processing Service business service to process exceptions.
8. Set Requested Product Instance. This step calls the Set Product Instance method of the SIS OM PMT Service business service, which sets the current asset as the instance from which to create order line records.
9. Is RAF. This condition step checks whether the flow is called from RAF. If so, it routes the flow to Reset Header, which uses the quote or order header from the input. If not, it routes the flow to Get Active Document flow, which queries for the active quote or order from database.
10. Reset Header. This step calls the Echo method of the Workflow Utilities business service to assign the quote or order header stored in the Instance argument in memory to the delta document, which is used for further processing, rather than using a database query to get the document.
11. Create Delta for Deleted Items. Creates order line item records with Delete action codes.
12. Add Deleted Items to Collection. Adds the Deleted order line items to a collection in memory for synchronization.
13. Mode = Order ? This decision step determines whether the flow calls for an order or quote. If Mode = Order ? is evaluated to TRUE, meaning that the flow calls for an order, it routes the flow to Customized Items ? If Mode = Order ? is FALSE, meaning that the flow calls for a quote, it routes the flow to Customize Items ?
14. Customized Items ? If the mode is order, this decision step checks whether the line items of the order include customized items. If Customized Items ? is evaluated to TRUE, this step routes the flow to Load Customized Instance. If not, it routes the flow to Load Default Instance.
15. Load Default Instance. If the new base product is not customizable, then this step calls the LoadDefaultItems method of the ABO Bulk Request Processing Service business service to load the default instance.
16. Load Customized Instance. If the Mode is Order and the new base product is customizable, then this step calls the LoadCustomizedItems method of the ABO Bulk Request Processing Service business service to load the customized instance.
17. Customize Items ? If the mode is not order, this decision step checks whether the line items of the quote include customized items. If Customize Items ? is evaluated to TRUE, this step routes the flow to Load Customized Instance_Quotes. If not, it routes the flow to Load Default Instance.
18. Load Customized Instance_Quotes. If the Mode is not Order and the new base product is customizable, then this step calls the LoadCustomizedItems method of the ABO Bulk Request Processing Service business service to get the list of instances according to the Scope and child Instance Type. For example, if the Scope is Exclude, then this step removes the specified instances from the list of instances.
19. BatchValidate. This step uses the BatchValidate method of the ABO Bulk Request Processing Service business service to validate the line item details using the configurator rules.
20. Merge Items. This step calls the MergeItems method of the ABO Bulk Request Processing Service business service to merge the default instance, customized instance, and instance assets into new order line items.
21. Auto Match Port Ids. This step uses the AutoMatch method of the Complex Product AutoMatch Service business service to validate the line item with product configurations and to fix any ambiguities.
22. Create Upgrade Asset. This step uses the Convert Product Instance method of the SIS OM PMT Service business service to convert the upgrade quote or order instance to a product instance.
23. Clear Product Instance. This step uses the Set Product Instance method of the SIS OM PMT Service business service to load an empty asset instance into memory.
24. Is RAF. This decision step checks whether the flow is called from an RAF Flow. If so, it routes the flow to Reset header to use the in-memory instance of the quote or order header. If not, it route the flow to Get Active Header for added item to load the quote or order instance from data base.
25. Reset header.This step uses the Echo method of the Workflow Utilities business service to assign the in-memory instance of quote or order as the header of the active quote or order.
26. Get Active Header for added item. This step uses the Query method of the EAI Siebel Adapter business service to load the active quote or order header instance.
27. Set Output Header for added item. This step uses the Set Output Header method of the SIS OM PMT Service business service to load the quote or order header instance to memory.
28. Create Delta for Added Items. This step uses the Delta method of the SIS OM PMT Service business service to compare the updated line details with the asset and compute the action code for each of the line items.
29. Add Added Items to Collection. This step uses the AddItemtoCollection method of the ABO Bulk Request Processing Service business service to add the update order structure to the collection in memory for synchronization.