| Oracle® Application Integration Architecture Pre-Built Integrations 11.2: Functional Interoperability Configuration Guide Release 11.2 Part Number E27102-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Pre-Built Integrations 11.2: Functional Interoperability Configuration Guide Release 11.2 Part Number E27102-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses the interoperable group of pre-built integrations: Oracle Product Master Data Management Integration Base Pack (Product MDM: Base), Oracle Product Master Data Management Integration Option for Siebel CRM (Product MDM: SBL CRM), Oracle Product Master Data Management Integration Option for Oracle Communications Billing and Revenue Management (Product MDM: Comms BRM) and Siebel CRM Integration Pack for Oracle Order Management: Order to Cash (Order to Cash: Siebel CRM - EBS). This chapter includes the routing rules that must be changed to enable interoperability.
This chapter includes the following sections:
In both the Product MDM integration and the Order to Cash integration, product information is synchronized between Siebel Customer Relationship Management (CRM) and Oracle E-Business Suite (EBS). The Product MDM integration also supports the Oracle Product Hub application in addition to Siebel CRM and Oracle EBS.
For more information, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide and the Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash.
The Oracle Product Hub (OPH) is a single consolidated system for defining products (items), Bill of Materials (BOMs, or item structures), and more product related features. The flows provided by the Product MDM integration are:
Synchronize Product Classes from the OPH to Siebel CRM.
Synchronize Domain Values from the OPH to Siebel CRM.
Synchronize Items and BOM from the OPH to Siebel CRM.
Synchronize Items and BOM from the OPH to Oracle E-Business Suite.
The flows provided by the Order to Cash integration are:
Sync Orderable Product from Oracle EBS to Siebel.
When an item (product) is created or updated in Oracle EBS, it is synchronized to Siebel CRM.
Request Bill of Material (BOM) Sync from Siebel to Oracle EBS.
A product administrator in Siebel CRM requests the details of item relationships for the selected BOM from Oracle EBS. As a result of this request, the details of the latest active version of the BOM and the associated non-orderable components are synchronized from Oracle EBS to Siebel CRM.
In the Product MDM integration, product information is synchronized from OPH to Siebel CRM and Oracle EBS. In the Order to Cash integration, product information is synchronized uni-directionally between Oracle EBS and Siebel CRM.
For more information, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide and the Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash.
When both the Product MDM integration and the Order to Cash integration are deployed, the following best practices flows are recommended for the product and bill of materials (BOM) synchronization among the various participating applications.
Products are created and updated in OPH only, so the AIA configuration property 'Product.Source.PIP' is always MDM.
Synchronize products from the Product MDM integration to Siebel CRM and Oracle EBS.
Sync BOMs from the Product MDM integration to Siebel CRM and Oracle EBS.
Request BOM synchronization from Siebel to Oracle EBS.
Synchronize Product Classes from the Product MDM integration to Siebel.
Synchronize Domain Values from the Product MDM integration to Siebel.
Even though the BOM is synchronized from the Product MDM integration, this BOM does not contain the Oracle EBS identifiers required to invoke Oracle Product Configurator from Siebel CRM. The product administrator in Siebel CRM must request the details of the product structure for the selected BOM from Oracle EBS. This synchronization provides the Oracle EBS identifiers in Siebel, so that the Oracle Product Configurator can be successfully invoked.
This section describes the routing rule and AIA configuration property changes that must be made to enable interoperability. There may be deployment sequence considerations.
This section includes the following topics:
For more information about install sequence considerations, see Chapter 1, "Deployment Dependencies". For more information about using and extending routing rules, see the Oracle Enterprise Service Bus Developer's Guide, "Creating Routing Services and Routing Rules".
Configure the ItemEBSV2 routing rule as described in Section 4.4.1.1, "For ItemEBSV2".
A new filter condition for the routing rule to the SyncProductSiebelProvABCSImpl must be added in the ItemEBSV2 service.
Table 4-1 shows the filter condition:
Table 4-1 Routing Rules for ItemEBSV2
| Operation | Filter Condition | Service Invoked | Description of Routing Rules |
|---|---|---|---|
|
SyncItemList |
(aia:getServiceProperty('{http://xmlns.oracle.com/EnterpriseServices/Core/Item/V2}ItemEBSV2',
'Routing.ActiveRuleset',false())='DEFAULT'
and count(normalize-space($in.SyncItemListEBM/ebo:SyncItemListEBM/ebo:DataArea))
> 0 and (normalize-space($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom:
EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode/text
())='PRODUCTION' or not (normalize-space($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom:
EBMHeader/corecom:MessageProcessingInstruction/corecom:
EnvironmentCode/text()))) and (xref:lookupXRef('oramds:/apps/AIAMetaData/xref/
INVENTORY_LOCATION_
ID.xref','COMMON',$in.SyncItemListEBM/ebo:SyncItemListEBM/ebo:DataArea[1]/ebo:SyncItemList/corecomEBO:
InventoryLocation/corecom:Identification/corecom:BusinessComponentID,'SEBL_01',false()))
and ((normalize-space($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom:EBMHeader/corecom:
Target/corecom:ApplicationTypeCode/text())='SIEBEL' or not(normalize-space($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom:
EBMHeader/corecom:Target/corecom:ID/text()))) or aia:getSystemType(normalize-space
($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom:EBMHeader/corecom:Target/corecom:ID/text
()))='SIEBEL') and (aia:getSystemType(normalize-space
($in.SyncItemListEBM/ebo:SyncItemListEBM/corecom
:EBMHeader/corecom:Sender/corecom:ID/text()))
!='SIEBEL'))
|
SyncProductSiebelProvABCSImpl_1_0::SyncItem |
The routing rule in the MDM integration by default only routes product sync messages created by PIM to Siebel. The additional conditions in the filter documented here, ensure that "*-items" created in Ebiz, are synced to Siebel since those types of items are mastered in E-Business Suite in the Order to Cash integration scenario. |
Set the following properties in the AIAConfigurationProperties.xml file:
Set the AIAConfiguration property PUBLISH_ALL_PRODUCT for the service QueryItemCompositionListEbizProvABCSImpl to Y.
Setting this property allows synchronization of all the Oracle EBS identifiers in Siebel.
Set the AIAConfiguration property Product.Source.PIP for both the InterfaceSyncProductStructureEBF and the SyncProductSiebelProvABCSImpl services to MDM.
Set the AIAConfig property COMPLEX_PRODUCT_RELEASE_FLAG, SIMPLE_PRODUCT_RELEASE_FLAG for the service SyncItemCompositionListSiebelProvABCSImpl to Y.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
