Siebel Order Management Guide > Workflow Reference for Employee Asset-Based Ordering > Workflow to Apply an Order to the Service Profile >

SIS OM Apply Completed Service Order Line Item to Service Profile

This workflow creates assets from completed order line items or modifies a current asset. It therefore maintains the account's service profile, which consists of its associated assets. If there are multiple accounts in an account hierarchy, then service items are applied to the service account. This workflow is shown in Figure 40.

You must develop an order synchronization workflow that updates the status of order line items in your Siebel Business Application when your company's external order management application completes all or part of an order. After it updates all the order items, the order synchronization workflow must call this workflow to apply the completed changes to the customer's service profile, which is stored as a series of assets. You can disable this workflow if an external application maintains service profiles.

By default, a user initiates this workflow by clicking the Auto-Asset button in the Order Entry - Order Line Items view.

NOTE:  The Auto-Asset button is designed for testing and demonstration purposes, not for actual end use. It is recommended that you configure your Siebel Business Application to call this workflow as a subprocess of the order synchronization workflow mentioned previously.

Figure 40. SIS OM Apply Completed Service Order Line Item to Service Profile Workflow

Workflow Description. This workflow does the following:

1. Reset PMT Cache. Clears business service cache of existing product instances.
2. Load Order Line Item. Loads the selected order line item from the database.
3. Update OLI Completed Flag. Updates the Order Item Processed flag. The workflow updates the Order Item Processed flag of the topmost order line item. The workflow sets this flag to Y if all line items have a status of Complete, Failed, or -. Other workflows use this flag to determine whether a line item remains Open and must be applied to the current service profile to generate a requested future state.

   NOTE:  To set the flag for the other status values, add these status values to this step's I/O Argument Complete Statuses. The default value is: Complete, Rejected.

4. Trim Order Line Item. Applies the Trim method. Trim eliminates any incomplete or failed changes from the order line item. It eliminates line items whose products are not tracked as assets, line items whose status is not Complete, and line items whose action code is Existing. This causes the service profile to reflect the true state of the assets.

   NOTE:  To keep the line items with the other status values, add these status values to this step's I/O Argument KeepSpec. The default value is: (([Status] = LookupValue('FS_ORDER_STATUS', 'Complete')) OR ([Action Code] = LookupValue('DELTA_ACTION_CODE', 'Existing'))) AND ([Convert To Asset Flag] = 'Y').

5. Is Trim Result Empty? Checks whether line items exist. If Trim has eliminated all line items, then the workflow stops. Otherwise, the workflow continues.
6. Logical Delete Order Item. Converts Delete actions into Modified actions. The Logical Delete step converts Delete actions into Modified actions and sets the status to Inactive. This step supports the maintenance of a history of disconnected services.
7. Load Asset. Loads the service profile from the database. If the order line item is a change to an existing item, then the workflow loads the corresponding service profile, or asset, from the database.
8. Set Current Asset Details. Uses the SetOldAssetDetails method of the ISS Promotion Agreement Manager business service to store Row Id of the current asset, the Integration Id of the current asset, the Row Id of the promotion associated with the current asset, the Promotion Instance Id of the current asset, and so on, in internal storage, so these IDs can be used by the GetPromotionDetails method.
9. Does Asset Exist? Checks whether there are any existing assets, that is, whether the number of assets is greater than 0.
10. Set Product Instance. Calls the Set Product Instance method of the Set Product Instance business service, which loads the product instance of the asset if any asset exists. The next step, Apply Changes, applies to the product instance of the asset that is loaded in this step.
11. Apply Changes. Applies changes related the order line item to the asset. If the asset does not already exist, then the workflow creates a new asset.
12. Is Apply Result Empty? Checks whether the asset is empty. If, as a result of applying the changes, the asset is empty, then the workflow stops. Otherwise, the workflow writes the asset to the database.
13. Prepare Sync Input (Set EAI_Operation Codes). Determines the operation that will be used, Insert, Update or Delete. This operation is entered in the Operation field of the Siebel Message. Based on the value of this field, the Sync Asset step determines which operation to perform.
14. Convert Del Items. Uses the ConvertDelItemsFieldToChildren method of the SIS OM PMT Service business service to convert the details of deleted products from Line Item fields to Integration Component MACD Order User Deleted Item structure, which will be used to update the deleted item details in the asset table.
15. Data Transformation. Uses the Execute method of the EAI Data Transformation Engine business service to transfer the asset hierarchy from Header - Line - XA to Line -XA. The header and line items business components are based on the same table, and this reduced hierarchy reduces the time taken to synchronize the data in the table.
16. Sync Asset. Uses the Synchronize method of the EAI Siebel Adapter business service to synchronize the updated asset structure to the Asset tables.
17. Skip Create Agreement. Determines whether or not a new agreement is created based on the input value of Skip Agreement.
18. Create Agreements. Calls ISS Promotion Agreement Management Sub Process workflow, which creates a new agreement or updates an existing agreement.

Associated Business Service Methods. Table 41 shows the steps in this workflow that call business service methods.