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

ABO Bulk Request - Submit Process Workflow

This workflow submits a bulk request for processing. The execution of this workflow can result in one or more exceptions that are logged in the exception table. Figure 47 shows this workflow.

The resubmit process is handled natively in this workflow and is accomplished by loading only those action sets, actions, and users who have the appropriate status.

• Only those action sets with a status of To Process or Partially Processed and no exceptions are loaded. Action sets that are completely processed have a Processed status, and the records are read-only.
• Only those action records with a status of To Process or Partially Processed are loaded. Action records that are completely processed have a Processed status, and action records that have errors have an Error status.
• Only those user records with a status of To Process or Partially Processed are loaded. User records that are completely processed have a Processed status, and user records that have errors have an Error status.

The ABO Bulk Request - Submit Driver Process Workflow calls this workflow as a subprocess.

Figure 47. ABO Bulk Request - Submit Process Workflow

Workflow Description. This workflow performs the following actions:

1. Updates the status of the header for the bulk request to Processing.
2. Loads the bulk request record into memory using the EAI Query method that takes as input a search specification that contains the bulk request ID.
3. Validates the action sets, actions, and users for the bulk request.
4. Gets the valid action sets to process.
5. Stores these action sets.
6. Calls the Next Action Set business service method to retrieve from memory the next valid action set record to process.
7. Checks whether the action set is stored, and gets the Action Code of the promotion.
8. Checks if the bulk request is canceled.
9. If the bulk request is not canceled, checks if an action set to process exists for the bulk request.
10. If an action set exists, calls the ABO Bulk Request - Parallel Sub Process Workflow for action sets that are processed in parallel or the ABO Bulk Request - Sub Process Workflow for action sets that are not processed in parallel. For more details, see ABO Bulk Request - Parallel Sub Process Workflow and ABO Bulk Request - Sub Process Workflow.
11. Queries the order header to obtain the total number of jobs present for the entered bulk request ID.
12. For bulk request headers to update, updates the status of the header to appropriate value and total number of jobs obtained in previous step. The successful or unsuccessful completion of the process to submit the bulk request determines the appropriate value.
13. Calls the ABO Bulk Request - Notify User Sub-Process Workflow that notifies the user or creator of the bulk request about the status of the bulk request. For more details, see ABO Bulk Request - Notify User Sub-Process Workflow.
14. For bulk request headers to not update, removes the action set for the bulk request, if appropriate.

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