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

ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow

When the scope of the action set is All or Exclude, 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 60 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 60. ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow

Workflow Description. This workflow performs the following actions:

1. Get Instances. This step gets the list of instances, using as criteria the scope and child instance type values. For example, if the scope is Exclude, then this step removes the specified instances from the list of instances.
2. Is Service Id Present? This step determines whether a service ID is present.
3. Consolidate Actions - To Process. This step consolidates the To Process actions for the instance.
4. Consolidate Exception? This step checks for exceptions from the consolidation step.
5. ProcessException. This step processes any found exceptions.
6. Next Consolidated Action. This step gets the next valid consolidated action record to process.
7. Is Null? This step determines if the action code is null.
8. Action = Add. This step determines if the action code is Add.
9. 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.
10. Action = Update. This step determines if the action code is Modify.
11. 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.
12. Action = Delete. This step determines if the action code is Delete.
13. 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.
14. Action = Upgrade. This step determines if the action code is Upgrade.
15. 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.
16. Action = Suspend/Resume. This step determines if the action code is Suspend or Resume.
17. 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.
18. Exception? This step determines if exceptions are present.
19. Process Exception. This step processes any found exceptions.
20. Update Action Set Actions. This step updates the status of the actions for the action set to Processed or to Error (for found exceptions).
21. 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.
22. Promotion Action Code = New? This step checks whether the action code of the promotion is New.
23. GetCollection for Upgrade Modify Promotion. This step gets promotion-related information from the document to be used when calling the Modify Promotion and Disconnect Promotion subprocesses.
24. Promotion Action Code = Upgrade. This step checks whether the Promotion Action Code is equal to Upgrade.
25. Disconnect Promotion. This step calls the Disconnect Promotion workflow.
26. Promotion Action Code = Modify? This step checks whether the action code of the promotion is Modify.
27. Modify Promotion. This step calls the Modify Promotion workflow.
28. Promotion Action Code = Modify or Upgrade or New. This step checks whether the action code of the promotion is Modify, Upgrade, or New.
29. Get Collection for ApplyPromotion. This step removes the entire document for the instance from the collection and proceeds to the Apply Promotion step.
30. Apply Promotion. This step checks the missed items and the matched items in the promotion.
31. Get Document. This step removes the entire document from the collection.
32. Ensure New Line Items. This step generates a new Integration Id for each line item in the document.
33. Set Document. This step gets the document back in the collection before synchronization occurs.
34. Synchronize. This step synchronizes the order line items for the instance with the price calculation and with the eligibility and compatibility check, if specified.
35. Exception & Mode=2? This step checks whether the E&C mode is 2 and whether any exception exists.
36. 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.
37. Set Promotion Instance Id. After the document is synchronized, this step adds the promotion instance Id to the promotion-related line items.
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 52 shows the steps in this workflow that call business service methods.