|Bookshelf Home | Contents | Index | PDF|
This topic describes some characteristics of order modification functionality in the context of Oracle Application Integration Architecture integration. These characteristics include order revisions and "as submitted" order records.
You can revise an original order, which creates a new version of the same order. The Revise feature allows you to revise the original order by creating a new order record with the same order number. The versions are distinguished by a revision number.
When you submit order revisions in Siebel CRM through Oracle Application Integration Architecture integration, you have several options that are specific to the integration. This topic describes features that are specific to Oracle Application Integration Architecture integration of Siebel CRM.
Siebel CRM and the external fulfillment system track revisions to order line items with the Row Id and Revised Line Item Id fields in Siebel CRM, and the Base Order Item Id field in the fulfillment system.
When a new order is created, and when a new line is added to an existing order, the value of the Row Id, Revised Line Item Id, and Base Order Item Id fields in the order line are the same. When a revision is created for the order, the following changes occur in existing order lines:
Table 16 lists the order versions, order actions, and IDs.
It is especially important for the fulfillment system to access previous values in case of a cancellation. For example, suppose an order is modified by a change to its Service Id (phone number). The revised order has been submitted, but is not yet fulfilled. Before fulfillment occurs, a cancellation is requested. This generates a revised order with no line items. The fulfillment system must know the original Row Id value of the former line item to identify what item to cancel. This information is provided using the Row Id, Revised Line Item Id, and Base Order Item Id.
An order submitted from Siebel CRM can only be changed by creating an order revision or a follow-on order while the order is in flight. However the fulfillment system can change the order. Changes made by the fulfillment system might include, for example, adding reserved resources to the original order, or updating the status of the order, or replacing the existing products as they were captured with equivalent products.
When an order is modified during its fulfillment by replacing products or changing product attributes, if configured, Siebel CRM makes a copy of the order in "As Submitted" form for user reference. Changes to the status of the order, or changes to record reserved resources, do not trigger the creation of an "As Submitted" copy.
The "As Submitted" copy of the order is identified by a Status field value of As Submitted. The "As Submitted" copy of the order has a new Order ID, and its line items have new Order Line Item IDs. This is because the fulfillment system still has to reference the original Order ID and Order Line Item IDs.
Siebel CRM creates an "As Submitted" copy of the order only when the order is first changed. Siebel CRM applies any additional changes to the products in the order, or the attributes of those products, to the original order and does not create additional copies of the order.
|Siebel Order Management Guide Addendum for Communications||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|