| 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.1 Part Number E22651-03 |
|
|
PDF · Mobi · ePub |
The Oracle Mediator Resequencer feature is used by various integration flows to ensure that messages are processed in a particular sequence.
This appendix contains the following sections:
For more information about the resequencer, see the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, "Support for Resequencing in Oracle Mediator."
This table lists the queues and flows that are enabled for sequencing.
Note:
Revision Order support - Oracle OSM manages scenarios where multiple revisions for the same order are sent out of sequence. If you are using a different Order Management system it must have similar support.
Table I-1 Queues and Flows Enabled for Sequencing
| Oracle AIA Queue | Flow | JMS Priority Set By | Sequencing Criteria | Comments |
|---|---|---|---|---|
|
AIA_SALESORDERJMSQUEUE |
Order submission flow from Siebel CRM to Oracle AIA. |
Siebel |
Group By: Billing Account on Order Header (/ListOfSWIOrderIO/SWIOrder/BillingAccountId) Order of Processing: FIFO (First in First Out). Composite Name: ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer. |
The resequencer in this flow ensures that in scenarios where concurrent orders for the same customer are submitted, the Oracle AIA Siebel provider does not fail while creating cross-reference entries. |
|
AIA_UPDSO_OUT_JMSQ |
Update order flow from Order Management/OSM to Oracle AIA for Siebel CRM system. |
Not Set |
Group By: Account ID mentioned in the ObjectCrossReference section of the update message(/UpdateSalesOrderEBM/EBMHeader/Sender/ObjectCrossReference/SenderObjectIdentification/AlternateObjectKey/ID[@schemeID = 'CUSTOMERPARTY_ACCOUNTID' and @schemeAgencyID = 'COMMON']) Order of Processing: FIFO (First in First Out). Composite Name: UpdateSalesOrderOSMCFSCommsJMSConsumer. |
Note: The consumer in the Create Trouble Ticket for Order Fallout business flow is only a sample. The resequencer in this flow ensures that multiple updates for the same order are processed in the right sequence. |
|
AIA_CRTCUST_OUT_JMSQ |
Order flow from Order Management/OSM to Oracle AIA for customer data creation in billing. |
Order Management/OSM |
Group By: Account ID on the message (this is either the Billing account or the Service account on the order line that must be created in billing) and the target system identifier. concat($in.SyncCustomerPartyListEBM/ns0:SyncCustomerPartyListEBM/ns0:DataArea/ns0:SyncCustomerPartyList/ns0:CustomerPartyAccount/corecom:Identification/corecom:ApplicationObjectKey/corecom:ID[@schemeID='AccountId'], $in.SyncCustomerPartyListEBM/ns0:SyncCustomerPartyListEBM/corecom:EBMHeader/corecom:Target/corecom:ID) Order of Processing: FIFO (First in First Out). Composite Name: CommunicationsCustomerPartyEBSV2Resequencer. |
The resequencer in this flow ensures that the solution can successfully handle processing of concurrent orders for the same customer. |
|
-- |
Sync customer flow from Siebel CRM system to Oracle Customer Hub. |
Not Set |
Group By: AccountID. Order of Processing: FIFO (First in First Out). Composite Name: SyncAcctSiebelAggrEventConsumer SyncContSiebelAggrEventConsumer. |
Also available in the Agent Assisted Billing Care pre-built integration. The resequencer in this flow ensures that multiple updates for the same customer are processed in the right sequence. |
|
AIA_CRTFO_IN_JMSQ |
Order flow from Oracle AIA to OSM |
ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer |
None. (Onus is on OSM.) |
na |
|
AIA_CRTBO_OUT_JMSQ |
Order flow from OSM to AIA for billing. |
OSM) |
None as delivered. Customers can use ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer to implement custom sequencing. |
na |
|
AIA_UPDBO_IN_JMSQ |
Order flow from AIA (from billing) to OSM |
ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer |
None. (Onus is on OSM.) |
na |
|
AIA_UPDCUST_IN_JMSQ |
Response of the customer creation in billing from AIA to OSM |
ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer |
None. (Onus is on OSM.) |
na |
|
AIA_CRTFO_OUT_JMSQ |
Create Fulfillment Order flow from OSM to Oracle AIA for the provisioning system |
OSM |
None as delivered. Customer can use ProcessProvisioningOrderOSMCFSCommsJMSConsumer to implement custom sequencing. |
na |
|
AIA_FOCFS_IN_JMSQ |
Update Fulfillment Order flow from Oracle AIA (from the provisioning system) to OSM) |
ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer |
None. (Onus is on OSM.) |
na |
|
AIA_FOPROV_OUT_JMSQ |
Update Fulfillment Order flow from the provisioning system to Oracle AIA (for OSM) |
Provisioning System |
None as delivered. Customer can use ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer to implement custom sequencing. |
na |
|
AIA_FOPROV_IN_JMSQ |
Create Fulfillment Order from Oracle AIA (from OSM) to the provisioning system. |
ProcessProvisioningOrderOSMPROVCommsJMSProducer |
None. (Onus is on OSM.) |
na |
An error may occur in the order process after the order was consumed by ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer but failed in any of the subsequent processes. As a result, the messages are rolled back to the resequencer. If this occurs, the fallout specialist must take corrective action on this resequencer to move the flow. If the message fails due to a system error (for example, if the target system is unavailable), then fallout specialists must retry the message from resequencer. If the message fails because of a business error, then the fallout specialist must unblock the resequencer.
If an error occurs in the Oracle BRM Customer provider, the message may be blocked in the CommunicationsCustomerPartyEBSV2Resequencer service and the error message may not propagate back to CommsProcessFulfillmentOrderBillingAccountListEBF. In these situations, fallout specialists must take corrective action on the resequencer to move the flow. If the message fails due to a system error (for example, if the target system is unavailable), then fallout specialists must retry the message from resequencer. If the message fails because of a business error, then the fallout specialist must unblock the resequencer.
An error may occur in the Siebel provider after it is consumed by UpdateSalesOrderOSMCFSCommsJMSConsumer and sent for processing. In this situation the messages are rolled back to the resequencer for this consumer and any subsequent order updates for that particular order are not processed. If this occurs, the fallout specialist must take corrective action on this resequencer to move the flow like the ones described above. If the message fails due to a system error (for example, if the target system is unavailable), then fallout specialists must retry the message from resequencer. If the message fails because of a business error, then the fallout specialist must unblock the resequencer.
For more information about retrying messages from resequencer and unblocking the resequencer, see Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite, "Resequencing Messages", Monitoring Resequenced Messages.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
