| Oracle® Application Integration Architecture Oracle Order Management for Oracle Transportation Management, Oracle EBS, and Siebel CRM Implementation Guide Release 3.1.1 Part Number E20504-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Oracle Order Management for Oracle Transportation Management, Oracle EBS, and Siebel CRM Implementation Guide Release 3.1.1 Part Number E20504-07 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of the process integration for customers and discusses business process flows, assumptions and constraints, Siebel Customer Relationship Management (Siebel CRM), Oracle E-Business Suite (Oracle EBS), and Oracle Transportation Management (OTM) interfaces, core Oracle Application Integration Architecture (Oracle AIA) components, and integration services.
This chapter includes the following sections:
The process integration for creating and synchronization of customer accounts between Siebel CRM, Oracle EBS, and OTM involves these integrations:
Synchronize create account from Siebel CRM to OTM and Oracle EBS.
Synchronize update account from Siebel CRM to OTM and Oracle EBS.
Customers are important for any transportation order. In Siebel CRM, the customers are created as accounts. These accounts must be in OTM for execution of the order and the same accounts must be in Oracle EBS for billing purpose.
In this integration, Siebel sends accounts to OTM and Oracle EBS. Whenever a new account is created in Siebel, a real-time synchronization flow is initiated to synchronize it to a customer account in Oracle EBS. A new location and the corresponding corporation are created in OTM simultaneously for that Siebel account.
The addresses of the Siebel CRM account are synchronized to Oracle EBS to create locations, party sites, and account sites are synchronized as separate locations in OTM. The Bill To and Ship To address relationships from Siebel CRM are synchronized to Party Site Use and Account Site Use in Oracle EBS and to Location Roles in OTM.
If an update to a customer record or any of the details, for example, addresses, contacts occurs in Siebel CRM, the updated account record is synchronized to both OTM and Oracle EBS.
Figure 2-1 Customer Process Integration Flow
Figure 2-2 Incremental Changes in the Account Sequence Diagram
Siebel application can send one of these messages:
Account Message - This message contains the details about an account and its associated addresses and contacts. This message is sent to SyncAccountSiebelReqABCSImpl requester process. The requester process converts the message to SyncCustomerPartyListEBM and sends it to CustomerPartyEBS. From enterprise business service (EBS), the message then flows through the OTM provider and Oracle EBS provider to create the entries in the respective systems.
Address Message - This message comes to application integration architecture (AIA) layer when an address is modified in Siebel CRM. Siebel CRM sends an address message that contains the changed address data and all the associated accounts and locations for that address. Master Data Management (MDM) code then deciphers that message, picks up the associated accounts, and for each account it creates an account message and sends it to the MDM account requester. The requester then processes the message in the same manner as described in account message.
Contact Message - This message comes to the Oracle AIA layer when a contact is modified in Siebel CRM. Siebel CRM sends a contact message that contains the changed contact data and all the associated accounts and locations for that contact. The MDM code then deciphers that message, picks up the associated accounts, and for each account it creates an account message and sends it to the MDM account requester. The requester then processes the message in the same manner as described in account message.
These are the solution assumptions and constraints:
Only B2B (business to business) scenarios are supported. B2C (business to customer) scenarios are not supported.
Siebel contacts are synchronized as account contacts to Oracle EBS, and not as person parties in Oracle EBS; however, contacts related to synced locations are synced to OTM.
Deletion of accounts, contacts, or address associated to a customer is not supported in the synchronization.
If any error occurs and the customer message does not reach the target application, then AIA error handling framework notifies you. You should then manually re-submit that transmission that failed for re-processing.
This integration does not perform any business validation and thus does not raise errors for business data issues.
The customer integration only supports the synchronization of accounts (and its addresses and contacts).
Contacts can be shared across to multiple accounts in Siebel. In OTM, the same contact cannot be associated to multiple locations. Thus, if a contact is associated to two different locations in Siebel, then the same contact is created twice in OTM for each location.
Prospect contacts are not synchronized from Siebel.
Account hierarchy synchronization is not in the scope of this release.
The process integration pack for Oracle Customer Hub master data management is used for transformation from Siebel to enterprise business object (EBO) and Oracle EBS provider (EBO to Oracle EBS) transformation.
OTM domain value is derived from business unit mapping in cross-references. If you want to use a specific logic for deriving the domain, you must use the extensible transformation template.
The OTM specific columns in cross-references are populated based on the identifiers derived in the OTM connector. If you want to pass a different value in the OTM identifier, you can use the transformation's extensibility to update the cross-reference as well.
The direction of data flow is only from Siebel to OTM and Oracle EBS. The reverse data flow is not supported in this integration. If any customer data is modified or created in OTM or Oracle EBS, those changes are not reflected in Siebel CRM. Any subsequent synchronization of the same data from Siebel to OTM or Oracle EBS may overwrite the changes made in OTM or Oracle EBS.
The schemas available for this outbound integration from Siebel are:
Account schema
Change Address schema
Change Contact schema
For more information about Siebel customer WSDL and schema definition, see Oracle Customer Master Data Management Integration documentation.
For more information about Oracle EBS web services definition language (WSDL) and schema definition, see Oracle Customer Master Data Management Integration documentation.
For more information about Oracle EBS web services and documentation prior to Release 12.1.3, see the library on Oracle Technology Network: http://www.oracle.com/technetwork/documentation/applications-167706.html?. For Oracle E-Business Suite documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm.
The OTM provides an interface through a web service to connect to its application. This connectivity is established as a partner link in the provider service. The logistics web service on being called immediately returns an acknowledgment with a transmission number. When the processing is complete, it then sends a transmission report back indicating the success or the failure.
For more information about the Logistics Service, see Oracle Transportation Management Integration Guide.
The integration flow uses these components:
CustomerPartyEBO
CustomerPartyEBM
The core enterprise business object (EBO) and enterprise business message (EBM) XSD files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/ parent folder.
The core enterprise business services (EBS) web services definition language (WSDL) files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/ parent folder.
For detailed documentation of individual EBOs and EBMs, click AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository.
For more information about using the Oracle Enterprise Repository 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 AIA 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.
For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Extensibility for AIA Artifacts.
The services delivered with the customer process integration are:
SyncCustomerPartyListLogisticsProvABCSImpl
JMS Topic
SyncCustomerPartyJMSProducerV1
SyncCustomerPartyEbizJMSConsumerV1
SyncCustomerPartyLogisticsJMSConsumer
The SyncCustomerPartyListLogisticsProvABCSlmpl service is a Business Process Execution Language (BPEL) process that receives SyncCustomerPartyListEBM as input from CustomerPartyListLogisticsJMSConsumerV1, transforms that message to Logistics application business message (ABM), and calls the Oracle Transportation Management (OTM) web service to process that message in OTM. Cross-reference values are populated upon successful message processing.
A JMS topic receives a message from the customer party EBS and routes it to both OTM connector and Oracle E-Business Suite connector. The topic is created in the AIA database under the user JMSUSER. The topic name is AIA_CustomerPartyJMSTV1.
This service publishes the SyncCustomerPartyListEBM JMS message from EBS into the topic.
This is a mediator service with JMS Adapter and a routing rule. It accepts SyncCustomerPartyListEBM as input from CustomerPartyEBSV2. The received Customer Party List enterprise business message (EBM) payload message is published into the JMS Topic AIA_CustomerPartyJMSTV1.
SyncCustomerPartyEbizJMSConsumerV1service is a subscriber to the topic that dequeues the SyncCustomerPartyListEBM JMS message from the JMS Topic for Oracle E-Business Suite connector.
This is a mediator service with JMS Adapter. This adapter dequeues the SyncCustomerPartyListEBM message for the subscribed consumer from the JMS Topic AIA_CustomerPartyJMSTV1 and routes the message to the SyncCustomerPartyListEbizProvABCSImpl provider service.
SyncCustomerPartyLogisticsJMSConsumerV1 service is the other subscriber of the topic that dequeues the SyncCustomerPartyListEBM JMS message from the topic for logistics connector.
This is a mediator service with JMS Adapter. This adapter dequeues the SyncCustomerPartyListEBM message for the subscribed consumer from the JMS Topic AIA_CustomerPartyJMSTV1 and routes to the SyncCustomerPartyListLogisticsProvABCSImpl.
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
