This chapter provides an overview of order provisioning, describes how provisioning orders are created, and how orders and statuses are updated in Oracle Communications Order and Service Management in the central order management role (OSM COM).
The Provision Order and Update Fulfillment Order business flows are enabled using the following Pre-Built Integration options of the Oracle Communications Order to Cash Integration Pack for Siebel customer relationships management (Siebel CRM), OSM, and Oracle Communications Billing and Revenue Management (BRM) (the integration):
Oracle Communications Order to Cash for Siebel CRM and OSM Pre-Built Integration option
Oracle Communications Order to Cash for Siebel CRM, OSM, and BRM Pre-Built Integration option
Siebel CRM sends customer order fulfillment requests of both Qualify and Deliver types to OSM COM, which decomposes them into suborders called order components. OSM uses the integration to send order components that are targeted for provisioning to either OSM in the service order management (OSM SOM) role or other order management systems.
See "Order Capture Overview" for more information about customer order fulfillment request types.
When OSM SOM manages the order lifecycle management (OLM) events of the service order. For Cancel and Revision requests, OSM generates and executes compensation plans to match the change. OSM also manages order data and status updates, and fallout incidents. Throughout the fulfillment process, OSM SOM sends status and data updates to OSM COM.
For interacting with OSM SOM, OSM COM pushes the ProcessProvisioningOrderEBM message, which includes most of the SalesOrderEBO attributes, into the AIA_CRTFO_OUT_JMSQ store-and-forward queue. Error responses come through the Oracle AIA common error schema, otherwise, there is no response for this message. Provisioning Service operation responses are made through ProcessFulfillmentOrderUpdate service operations in all cases except an interface error or request failure. In these cases, the responses are passed to an Oracle AIA Error Handling service, which passes order failure information from provisioning to customer order management for order fallout handling.
See "Implementing the Provision Order and Update Fulfillment Order Business Flows" for more information about this sequence of events.
See "Understanding the Process Integration for Order Fallout Management" for more information about order fallout.
This feature provides the ability to update OSM COM with OSM SOM milestones, status, and data.
Order Status Management is an integral capability of OSM COM. OSM COM provides for a configurable order status management across different fulfillment systems, including OSM SOM.
In addition, order milestones are configured to track order fulfillment progress. Fulfillment system responses and status updates are used to trigger evaluation of rules that progress the order item status and realize new milestones and in turn trigger aggregation rules that update the order-level status.
Also, several attributes are populated during design and assign that are critical to pass to other fulfillment systems and Siebel CRM.
One or more OSM Provisioning Cartridges must be deployed. They preserve the Oracle AIA interfaces.
See the OSM documentation for more information about product-specific assumptions and constraints.