Skip Headers
Oracle® Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management
Release 11.2

Part Number E26501-03
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

14 OLM - Understanding the Provision Order and Update Fulfillment Order Business Flows

This chapter provides an overview of order provisioning, describes how provisioning orders are created, and how orders and statuses are updated in the Oracle Order and Service Management Central Order Management (Oracle OSM COM) system.

This chapter includes the following sections:

The provision order and update fulfillment order business flows are enabled using the Oracle Communications Order to Cash: Oracle OSM pre-built integration option.

14.1 Order Provisioning Overview

Customer order fulfillment requests, (both Qualify and Deliver types), received in Oracle OSM COM from Siebel Customer Relationship Management (Siebel CRM) are decomposed into suborders called order components depending on the fulfillment topology and the fulfillment dependencies. Some of the order components are targeted for a provisioning (Service Order Management) stack. Oracle OSM COM uses Oracle Application Integration Architecture (Oracle AIA) services to pass provision order requests to Oracle OSM Service Order Management (Oracle OSM Provisioning) instance or any third-party OSM system.

For more information about customer order fulfillment request types, see Section 7.3, "Order Capture Overview."

When Oracle OSM is also used as the Service Order Management application, Oracle OSM manages the order lifecycle management (OLM) events of the service order. For Cancel and Revision requests, Oracle OSM generates and executes compensation plans to efficiently match the change. OLM also manages order data and status updates, and fallout incidents. Throughout the fulfillment process, Oracle OSM Provisioning sends status and data updates to Oracle OSM COM.

14.2 Creating Provisioning Orders

For interacting with Oracle OSM Provisioning, OSM COM pushes the ProcessProvisioningOrderEBM message, which includes most of the SalesOrderEBO attributes, into AIA_CRTFO_OUT_JMSQ using sore and forward (SAF) mechanism. When it errors, the response comes 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.

For more information about this sequence of events, see Chapter 15, "OLM - Provision Order and Update Fulfillment Order Business Flows: Implementation."

For more information about order fallout, see Chapter 21, "Understanding the Process Integration for Order Fallout Management."

14.3 Updating Fulfillment Orders

This feature provides the ability to update Oracle OSM COM with Oracle OSM Provisioning milestones, status, and data.

Order Status Management is an integral capability of Oracle OSM COM. Oracle OSM COM provides for a configurable order status management across different fulfillment systems, including Oracle OSM Provisioning.

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.

14.4 Solution Assumptions and Constraints

One or more OSM Provisioning Cartridges must be deployed. They preserve the Oracle AIA interfaces.

For more information about product-specific assumptions and constraints, see the Oracle Order and Service Management product documentation.