Bookshelf Home | Contents | Index | PDF     

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

ABO Bulk Request - Modify Sub-Process Workflow

This workflow creates an order line item when the consolidated action is Update. Figure 62 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 consolidated action is Update.

Figure 62. ABO Bulk Request - Modify Sub-Process Workflow

Workflow Description. This workflow performs the following actions:

  1. Build User Assets. This step calls the BuildInstanceAsset method of the ABO Bulk Request Processing Service business service, which uses the contact ID and account ID for the user and the product ID to load the asset records for the user.
  2. Use Input Instance ? This condition step checks whether the input includes a quote or order structure to be used in the processing that is called from a RAF flow.
  3. Build Org User Assets. This step calls BuildInstanceAsset method of ABO Bulk Request Processing Service business service for loading the asset based on the input, and it also considers the input quote or order which has been provided in the input argument.
  4. Num Assets More Than Zero. This decision step checks to see whether asset records exist. If no asset records exist, then an exception occurs, and the workflow terminates.
  5. Input Instance. This condition step checks whether the input includes a quote or order structure to be used in the processing that is called from a RAF flow.
  6. Next Asset For Open Instance. This step calls the NextObject method of the ABO Bulk Request Processing Service business service to traverse to the next root product in the quote or order structure that is passed as input argument.
  7. Next Asset. This step uses the NextObject method of the ABO Bulk Request Processing Service business service to load into memory the next asset for the user from the instance asset records created in the earlier step.
  8. Null. This decision step checks whether the asset id for the list of product which is being loaded in to memory in the step Next Asset is Null. If so, there is no remaining asset to apply the actions to.
  9. Input Instance. This decision step checks whether the input includes a quote or order structure to be used in the processing and whether it is called from a RAF flow. If so, it routes the flow to the step Set Requested Product Open Instance and the subsequent steps to load and apply actions the quote or order instance passed as input. If not, it routes the flow to the step Set Requested Product Instance and the subsequent steps to apply actions to the quote or order that are based on user asset.
  10. Set Requested Product Open Instance. This step calls the Set Product Instance method of the SIS OM PMT Service business service to load the current root product instance details into memory for processing.
  11. Automatch With Instance. This step calls the AutoMatch method of the Complex Product AutoMatch Service business service to match the line items of the quote or order with the product configuration using the Configurator engine and to fix any inconsistency.
  12. Apply Consolidated Action With Instance. This step calls the MergeConsolidatedAction method of the ABO Bulk Request Processing Service business service to apply consolidated actions to the user asset to form the future state of the asset.
  13. Exception Flag? This condition step checks whether there are any exceptions while applying the modify actions. If so, it routes the message to the Process Exceptions step. If not, to the Merged? step.
  14. Set Requested Product Instance. This step calls the Set Product Instance method of the SIS OM PMT Service business service, which uses the asset for the user and the consolidated action (converted into asset hierarchy) to build the future state of the asset.
  15. Automatch. This step calls the AutoMatch method of the Complex Product AutoMatch Service business service to match the line items of the quote or order with the product configuration using the Configurator engine and to fix any inconsistency.
  16. Apply Consolidated Action. This step calls the MergeConsolidateAction method of the ABO Bulk Request Processing Service business service, which compares the future state of the asset to the initial state of the asset to create the order line item records with appropriate action codes.
  17. Merged. This decision step checks if the action must be applied on another instance of the product or if the final structure is merged. If all the actions are applied on the instances, it routes the flow to Has Input Instance and subsequent steps to calculate delta. If not, it routes the flow to the step Next Asset For Open Instance to apply actions to the next instance of the product.
  18. Has Input Instance? This decision step checks whether the flow is called from an RAF Flow and has a quote or order instance as input. If so, it routes the flow to the step Set Original Requested Product Instance. If not, to the step Set Header.
  19. Set Original Requested Product Instance. This step calls the Set Product Instance method of the SIS OM PMT Service business service to reload the original instance of the product from the asset to memory, enabling the action code to be calculated based on the original instance of the asset during the delta flow.
  20. Set Header. This step uses the Set Output Header method of the SIS OM PMT Service business service to lead the quote or order structure to memory which is required for the Delta calculation in the step Delta.
  21. Delta. This step uses the Delta method of the SIS OM PMT Service business service to compare the updated line items with those of the asset and to update the action code for each of the line items
  22. Batch Validate. This step uses the BatchValidate method of the ABO Bulk Request Processing Service business service to validate order or quote line items against configurator rules.
  23. Exception. This decision step checks whether Batch Validate found any exceptions.
  24. Process Exacerbations. This step uses the WriteException method of the ABO Bulk Request Processing Service business service to extract and update the error message to the database.
  25. Add Item to Collection. If exceptions do not exist, then this step uses the AddItemtoCollection method of the ABO Bulk Request Processing Service business service to add the order line items to a collection in memory for synchronization.
  26. Has Instance ? This decision step checks whether the quote or order is specified in the input.
  27. Add Instance to Collection. This step calls the AddItemtoCollection method of the ABO Bulk Request Processing Service business service if the quote or order is specified in the input, adding the nonmodified line item details from the quote or order to the collection.
      
Siebel Order Management Guide Addendum for Communications Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.