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
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

17 OLM - Update Sales Order Business Flow: Implementation

This chapter provides an overview of the Update Sales Order business flow and discusses the implementation of Siebel Customer Relationship Management (Siebel CRM) interfaces, industry Oracle Application Integration Architecture (Oracle AIA) components, and integration services.

This chapter includes the following sections:

17.1 Update Sales Order Business Flow Overview

This business flow is enabled using the Oracle Communications Order to Cash Siebel Customer Relationship Management (Siebel CRM) and Oracle Order and Service Management (Oracle OSM) pre-built integration options.

The following integration flow involves updating order statuses from Oracle OSM back to Siebel CRM.:

17.2 Updating Statuses from Oracle OSM to Siebel CRM Integration Flow

This integration flow uses the following interfaces:

Figure 17-1 illustrates how to use Oracle OSM to send a sales order data and status update to Siebel:

Updating Statuses from Oracle OSM to Siebel CRM sequence diagram

Figure 17-1 Updating Statuses from Oracle OSM to Siebel CRM Sequence Diagram

This image is described in surrounding text.

When this process is initiated, the following events occur:

  1. Oracle OSM creates a message UpdateSalesOrderEBM and enqueues the message to the Oracle AIA queue called AIA_UPDSO_OUT_JMSQ using SAF. The UpdateSalesOrderOSMCFSCommsJMSConsumer consumes this message and routes the message to UpdateSalesOrderSiebelCommsProvABCSImpl.

    Caution:

    The UpdateSalesOrderOSMCFSCommsJMSConsumer also has a sequencer. In other words, if any update to Siebel causes a system or business error, any further updates to the account does not happen until the error is fixed. All updates for that account are locked in the sequencer table. If the error is a business error then the message must be removed from the sequencer table and if the error is a system error then the message must be resubmitted.

  2. This process converts the enterprise business message (EBM) into a Siebel ABM and invokes the Siebel web service to update the order.

    Oracle AIA always copies fulfillment status to the DeliveryStatus ABM attribute. Internally, Siebel CRM reflects the end state status values (Canceled and Complete) on the Status field. The DeliveryStatus is mapped in the Siebel UI to the Fulfillment Status.

    In other words, the Status field in the Siebel UI represents the overarching status throughout order capture and order fulfillment. Fulfillment Status is a sub-status to Status = Open. Fulfillment Status indicates the status of the order in OSM COM while the order is in being fulfilled.

    For more information about using sequencing logic to make updates to Siebel, see Section 8.2, "Supporting Order Priorities" and Appendix I, "Using the Oracle Mediator Resequencer Feature."

17.2.1 Defining Transaction Boundaries and Recovery Details

For this flow there are two transaction boundaries. Table 17-1 describes the transactions involved, the database operations, and what actions to take in case of an error.

If any update to Siebel causes a system or business error, any further updates to the account does not happen until the error is fixed. All updates for that account are locked in the sequencer table. If the error is a business error then the message must be removed from the sequencer table and if the error is a system error then the message must be resubmitted.

For more information about system errors and business errors, see Section 27.5.2, "Using Error Type to Control Response to Order Fallout."

The following services are involved:

  • UpdateSalesOrderOSMCFSCommsJMSConsumer

  • UpdateSalesOrderOSMCFSCommsJMSConsumer_RS

  • UpdateSalesOrderSiebelCommsProvABCSImpl

Table 17-1 Transaction Boundaries and Recovery Details

Transaction DB Operations In Case of Error Recovery

UpdateSalesOrderOSMCFSCommsJMSConsumer consumes the message and puts it in the sequencer table defined at the Routing Service UpdateSalesOrderOSMCFSCommsJMSConsumer_RS.

Message goes into the sequencer table.

Rollback JMS message to AIA_UPDSO_OUT_JMSQ_ErrorQ

Resubmit the order from AIA_UPDSO_OUT_JMSQ_ErrorQ.

UpdateSalesOrderOSMCFSCommsJMSConsumer_RS routes the message to UpdateSalesOrderSiebelCommsProvABCSImpl, which invokes the Siebel web service to update the order.

AIA cross-reference entries.

Rollback the message to the sequencer table.

Resubmit the order from the sequencer table.


For more information about rollback procedures, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring Oracle AIA Processes for Error Handling and Trace Logging", Configuring Fault Policies to Not Issue Rollback Messages.

17.3 Siebel CRM Interfaces

This integration flow uses the following Siebel interfaces:

These are inbound Siebel web services used to update the order information back to Siebel CRM.

For more information about web services, see the Siebel Order Management Guide Addendum for Communications, "Web Services Reference."

17.4 Industry Oracle AIA Components

These integration flows use these industry components:

The industry enterprise business object (EBO) and enterprise business message XML schema (EBM XSD) files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Communications/EBO/

The industry enterprise business service (EBS) WSDL files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Industry/Communications/EBO/

For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository (OER).

For more information about using the OER and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle SOA Repository."

EBOs can be extended, for instance, to add new data elements. These extensions are protected and remain intact after a patch or an upgrade, so long as the extensibility guidelines are followed.

For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with AIA Design Patterns," AIA Assets Extensibility Patterns, Extending Existing Schemas in AIA.

17.5 Integration Services

The following services are delivered with these integration flows:

Some of these services have been enabled to use Session Pool Manager.

For more information about Session Pool Manager, see Oracle Application Integration Architecture Pre-Built Integrations 11.1: Utilities Guide, "Session Pool Manager."

17.5.1 UpdateSalesOrderOSMCFSCommsJMSConsumer

The UpdateSalesOrderOSMCFSCommsJMSConsumer is a Mediator process with a JMS Adapter Service. This process dequeues the UpdateSalesOrderEBM message from the AIA_UPDSO_OUT_JMSQ.

This service has one operation: Consume_Message.

17.5.2 UpdateSalesOrderSiebelCommsProvABCSImpl

The UpdateSalesOrderSiebelCommsProvABCSImpl is a BPEL process with one operation: UpdateSalesOrder. It accepts the UpdateSalesOrderEBM as the input from the UpdateSalesOrderOSMCFSCommsJMSConsumer, and uses the order information in the input message to update the orders in Siebel CRM.

The main functions of this service are:

  • Updating the order line status: updates the order line status back to Siebel CRM.

  • Enriching the order: enriches the information back to Siebel CRM from a central fulfillment system to facilitate customer care, service, and asset-based ordering. It is also used to update or enrich the order line items with fulfillment attributes back to Siebel CRM. Among these attributes are service IDs and allocated resources such as port number and IP address.

  • Updating the order header: enriches the order header to Siebel CRM.

This process is an asynchronous, one-way service.

This service is SPM enabled.

For more information about Session Pool Manager, see Oracle Application Integration Architecture Pre-Built Integrations 11.1: Utilities Guide, "Session Pool Manager."