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

ABO Bulk Request - Inclusive Process Action Sub-Process Workflow


When the scope of the action set is Inclusive, this workflow cycles through the consolidated actions in the action set of a submitted bulk order to call the appropriate subprocess to create order line items for the users in the bulk order. Figure 59 shows this workflow.

The ABO Bulk Request - Parallel Sub Process Workflow or the ABO Bulk Request - Sub Process Workflow calls this workflow as a subprocess.

Figure 59. ABO Bulk Request - Inclusive Process Action Sub-Process Workflow

Workflow Description. This workflow performs the following actions:

  1. Is Service Id Present? This step determines whether a service ID is present.
  2. Check Instance Status. This step determines the status of the instance.
  3. Consolidate Actions - Partially Processed. This step consolidates the partially processed actions for the instance.
  4. Consolidate Actions - To Process. This step consolidates the To Process actions for the instance.
  5. Consolidate Exception? This step checks for exceptions from the consolidation steps.
  6. ProcessException. This step processes any found exceptions.
  7. Next Consolidated Action. This step gets the next valid consolidated action record to process.
  8. Is Null? This step determines if the action code is null.
  9. Action = Add. This step determines if the action code is Add.
  10. Add Sub Process. This step creates order line items for Add action codes. For more information, see ABO Bulk Request - Add Sub-Process Workflow. The subprocess uses the consolidated action and the list of action set users as input.
  11. Action = Update. This step determines if the action code is Modify.
  12. Modify Sub Process. This step creates order line items for Modify action codes. For more information, see ABO Bulk Request - Modify Sub-Process Workflow. The subprocess uses the consolidated action and the list of action set users as input.
  13. Action = Delete. This step determines if the action code is Delete.
  14. Delete Sub Process. This step creates order line items for Delete action codes. For more information, see ABO Bulk Request - Delete Sub-Process Workflow. The subprocess uses the consolidated action and the list of action set users as input.
  15. Action = Upgrade. This step determines if the action code is Upgrade.
  16. Upgrade Sub Process. This step creates order line items for Upgrade action codes. For more information, see ABO Bulk Request - Upgrade Sub-Process Workflow. The subprocess uses the consolidated action and the list of action set users as input.
  17. Action = Suspend/Resume. This step determines if the action code is Suspend or Resume.
  18. Suspend/Resume Sub Process. This step creates order line items for Suspend and Resume action codes. For more information, see ABO Bulk Request - Suspend/Resume Sub-Process Workflow. The subprocess uses the consolidated action and the list of action set users as input.
  19. Exception? This step determines if exceptions are present.
  20. Promotion Action Code = New or Upgrade or Modify or Delete? This step checks whether the Promotion Action Code is equal to New, Upgrade, Modify, or Delete.
  21. Promotion Action Code = New? This step checks whether the action code of the promotion is New.
  22. GetCollection for Upgrade Modify Promotion. This step gets the collection to upgrade a modify promotion.
  23. Promotion Action Code = Upgrade. This step checks whether the Promotion Action Code is equal to Upgrade.
  24. Disconnect Promotion. This step calls the subprocess to delete promotions.
  25. Promotion Action Code = Modify? This step checks whether the action code of the promotion is Modify.
  26. Modify Promotion. This step calls the subprocess to modify the promotion.
  27. Promotion Action Code = Modify or Upgrade or New. This step checks whether the action code of the promotion is Modify, Upgrade, or New.
  28. GetCollection for Apply Promotion. This step gets the collection to apply the promotion.
  29. Apply Promotion. This step calls the subprocess to apply promotions.
  30. Get Document. This step gets information about the overall document.
  31. Ensure New Line Items. This step checks new line items.
  32. Set Document. This step sets the document.
  33. Synchronize. This step synchronizes the order line items for the instance with the price calculation and with the eligibility and compatibility check, if specified.
  34. Exception & Mode=2? This step checks whether the E&C mode is 2 and whether any exception exists.
  35. Promotion Action Code = New or Upgrade or Modify or Delete. This step checks whether the action code of the promotion is New, Upgrade, Modify, or Delete.
  36. Set Promotion Instance Id. This step sets the promotion instance Id.
  37. Exception & Mode=2? This step checks whether the E&C mode is 2 and whether any exception exists.
  38. Next Instance. This step loops through the list of instances and return one instance at a time for processing.
  39. Update Action Set Actions. This step updates the status of the actions for the action set to Processed or to Error (for found exceptions).

Table 53 shows the steps in this workflow that call business service methods.

Table 53. Associated Business Service Methods
Workflow Step
Method Called
In Business Service

Ensure New Line Items

Set Field Value

SIS OM PMT Service

Get Document

GetCollection

ABO Bulk Request Processing Service

GetCollection for Apply Promotion

GetCollection

ABO Bulk Request Processing Service

GetCollection for Upgrade Modify Promotion

GetCollection

ABO Bulk Request Processing Service

Set Document

AddItemtoCollection

ABO Bulk Request Processing Service

Set Promotion Instance Id

SetPromInstanceId

ABO Bulk Request Processing Service

Siebel Order Management Guide Addendum for Communications Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.