This chapter discusses the interoperable pair of pre-built integrations: Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release (Design to Release: Agile - EBS) 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:
The Design to Release: Agile - EBS integration supports the exchange of product information between Agile PLM and Oracle EBS. In the Order to Cash: Siebel CRM - EBS integration, product information is exchanged between Siebel Customer Relationship Management (Siebel CRM) and Oracle E-Business Suite (Oracle EBS). It is a one way feed from Oracle EBS to Siebel CRM.
For more information, see the Oracle Application Integration Architecture Design to Release: Agile - EBS Implementation Guide and the Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash.
The Design to Release: Agile - EBS integration enables and integrates the product development process between Design to Release: Agile - EBS and Oracle EBS. This integration supports different scenarios.
Change Order Release: during the product design phase, new products or parts are introduced or existing parts may go through design changes. When the authoring of a part's attributes and design information is complete and is ready for publishing to the manufacturing system, it is released by Change Orders. The Change Order Release Process consists of the New Part and Product Release (PREL) and the Product Design Modification flows of Design to Release: Agile - EBS. The release of a change order in the Design to Release: Agile - EBS integration system acts as a trigger for the synchronization of product design information with the ERP system.
For all items pushed to the ERP system, the system verifies whether the items exist, and whether they have the same revision number as the old item from the Agile system. If the item did not exist in ERP and is being released for the first time from PLM, it is created in ERP. If the item exists in ERP and the two systems were coordinated concerning item revision, the existing item is updated with new attribute data from Agile.
These are the product sync related flows:
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 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 to Siebel.
The details of the latest active version of the BOM and associated non-orderable components are synchronized from Oracle EBS to Siebel CRM as result of this request.
The following are the best practices for product (Item) and BOM synchronization among the various participating applications when the Design to Release: Agile - EBS integration and the Order to Cash: Siebel CRM - EBS support interoperability:
The Design to Release: Agile - EBS integration manages the product life cycle.
While the Design to Release: Agile - EBS integration is the system of record for item description, design, specs, and other information, the ERP system has more attributes and placeholders for information than the Design to Release: Agile - EBS system. The change order release must be updated in the ERP system.
The update of Item Attribute information from Oracle EBS to Design to Release: Agile - EBS is done as a batch process.
Item updates from Oracle EBS to Siebel CRM must be done using the Sync Item process.
If needed, Siebel CRM should request the BOM from Oracle EBS.
Routing rules changes are required to enable the interoperability of the Design to Release: Agile - EBS integration with the Order to Cash: Siebel CRM - EBS integration. The affected service-oriented architecture (SOA) composite service is the ItemEBSV2. The changes are delivered through patch 12314525. This patch should be applied to the Oracle AIA and Fusion Middleware (FMW) environment to re-deploy the ItemEBSV2 composite service with the new routing rules.
Perform these steps after both integrations have been installed and deployed:
Log in to the Oracle AIA Console.
Navigate to Setup, Systems.
Verify that the value in the System Type column for the E-Business Suite system is set to EBIZ (all upper-case). If it is not set to EBIZ, change the value to EBIZ and save.
Navigate to the AIA Configuration tab, and click Reload.