Siebel Order Management Guide Addendum for Communications > Workflows for Employee Asset-Based Ordering > Workflows to Process an Order >

SWIOrderUpsert Workflow

This workflow performs the following tasks:

• Makes a backup copy of an order.
• Updates the order details.
• Cascades down update.
• Triggers an auto asset.

Oracle Application Integration Architecture uses this workflow to update the order details through the SWIOrderUpsert inbound Web service. It is called when an order update arrives from Oracle Application Integration Architecture. This workflow is exposed as an inbound Web service and is used by the Siebel application to update or insert an order. This workflow decides on the basis of the system preference whether it calls the Order To Cash Process Integration Pack Order Upsert workflow or follows the communications workflow.

The UTCCanonical flag is N by default. To turn this default behavior on, you must change the default value for the UTCCanonical process property in the SWIOrderUpsert workflow to Y. This setting requires that updates from the Siebel application must be in UTC Canonical format. Because the process property is an Input process property, you can set the value of the UTCCanonical flag to Y or N from the Siebel application.

Figure 108 illustrates the SWIOrderUpsert workflow.

Figure 108. SWIOrderUpsert Workflow

Workflow Description. This workflow performs the following actions:

1. Is O2C Enabled? This step checks for the Enable AIA OrderToCash system preference and calls the O2C Order Upsert Workflow if the Is O2C Enabled property is set to True.
2. O2C Order Upsert. This step calls the SWI Order Upsert_O2C subprocess.
3. Get Header Field Value. This step gets the Order Id value. This step takes SiebelMessage, Fieldnames, HierarchyNode, and MaxField as input.
4. Is Copy Order. This step checks the status of the Backup Order Flag.
5. Copy Order. If the Backup Order Flag is set to True, then this subprocess calls the SWICopyOrder workflow to make a backup of the order details. For details, see SWICopyOrder Workflow.
6. EAI Update. This step uses an input flag named UTCCanonical. This flag is N by default. If this flag is Y, then data from the Siebel application must be in UTC (Coordinated Universal Time) and canonical format. The data in UTC and canonical format is converted to Siebel object manager format as determined by the value of the UTCCanonical flag.
7. RunOnWorkflowProcMgr? This step checks whether the RunOnWorkflowProcMgr process property is set to Y. If this process property is set to Y, then this step runs the SWIOrderUpsertSubProcess workflow on a different server component.
8. OrderUpsert_SubProcess. This step calls the SWIOrderUpsertSubProcess workflow.
9. Convert to XML Document. This step converts the Siebel message to a string that can be submitted to the Server Request business service to be run on a different server component.
10. Execute Sub Process. This step runs the workflow on a different server component.

    The default value of the literal Mode, which is an input to this step, is Sync. To make the call asynchronous, change the Mode value to DirectDB.

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