Siebel Order Management Guide Addendum for Communications > Telco Subscription Management in Open UI > Workflow Reference for Telco Subscription Management in Open UI >

TOUI AssignBar Generate Order Process Workflow

TOUI AssignBar Generate Order Process Workflow, shown in Figure 6, is invoked when the user clicks the Submit button on the Add/Remove Bar view after updating the action code details for the selected services to generate an order based on the selected services and Add/Remove option selected for child products for the mobile phone services. This workflow also validates the request, validates eligibility and compatibility, and generates and submits the order. If there is any invalid selection, an error message is displayed.

Figure 6. TOUI AssignBar Generate Order Process Workflow

Workflow Description. This workflow performs the following actions:

1. Get Account Details. This step queries the Account business component based on the Account Id, and it returns the Currency Code, Price List id, Document Type (Order or Quote), Primary Billing Profile Id and Exchange Date properties.
2. Reset PMT Cache. This step resets the cache, clearing the product instance from the cache, to prevent an incomplete workflow from polluting the Product Manipulation Toolkit (PMT) cache.
3. Get AssignBar Selected Service. This step calls the child workflow TOUI AssignBar Get Selected Services Sub Process. This workflow returns all the root selected services in the Selected Services applet. For example, if the Selected Services applet has ten root product services selected of the type mobile phone service, and if each of the mobile phone services has multiple child products of the type Bar, then this returns only the details related to the mobile phone services that are the root products.
4. Get Next Selected Service. This step extracts one of the root selected services from the selected list returned by the last step. This step is called for each of the selected services in a loop.
5. IsEmpty? This step checks if there are any further service available to be processed. If so, it repeats the Get Selected Service Values step. If not, it synchronizes order details to the database.
6. Get Selected Service Values. This step reads the values related to selected services from the hierarchical property set and stores them in the process property, which is used in the later steps.
7. Pre-exist Error2? This step checks whether there is an existing error.
8. Reset Error. If there is an existing error, this step clears that error.
9. Load Asset. This step performs an EAI Siebel Adapter query on the SIS OM Asset IO based on the Integration Id to get the Asset Document. The output of this step is a hierarchical property set of the asset details.
10. Get Delta. This step calls the TOUI AssignBar Get Delta Sub Process child workflow, which updated the Order document based on the Action Code.
11. Error? This step checks whether there was an error during execution of the child workflow. If there is no error, then it processes the order document.
12. Action Occurrence. This step checks whether any action was processed in the child workflow. If so, then a later step converts the IO document to a property set, so that the property set document can be merged to the final order document.
13. Aggregate Exception. This step checks whether any exception occurred in any of the Delta Sub process calls, and it sets a flag accordingly.
14. Exit On Error? This step checks whether the processing needs to be terminated immediately once the exception has occurred.
15. Transfer Order IO TO PS. This step converts the IO document into a property set document. Because the Batchvalidate output document is in IO form, this processing is required before merging the document into the Order document.
16. Merge Header. This step merges the currently selected services document with Order Header details, creating an aggregate document used for synchronizing the document.
17. Increment Count. This step increments the counter, indicating that one available service has been successfully processed. This counter is also used in deciding whether any request has been processed.
18. Any Occurance. This step checks whether any available service has been processed successfully to generate an order. If so, execution of the workflow continues. If not, the workflow is terminated and an error message is displayed.
19. Stop 0. This step displays a pop-up error message saying, "Error occurred while generating the order. Please select a valid option."
20. Get Next Order Number. This step sets the order number for the order document.
21. Set Order Type. This step sets the Order Type field for the order document.
22. Transfer PS to Output IO. This step takes the aggregate order document in property set format and converts it into IO format.
23. Validate Eligibility and Compatibility. This step calls the EligCompValidation method of the ABO Bulk Request Processing Service business service. This method prepares the payload and calls eligibility and compatibility validation of the order document.
24. Upsert Doc. This inserts the order document into the database.
25. Submit Order. This step calls the SISOMBillingSubmitOrderWebService workflow, which submits the order document.
26. Get Order Detail. This step queries the order based on the integration id to retrieve the values of the Order Number, Order Status and Revision fields.
27. Delete Selection. This step deletes all the line items from the Selected Services list, because they have already been submitted as an order.
28. Goto Order Summary View. This step navigates to the Order Summary view.