What is co-existence strategy? Is it just a myth?
Until EBS R12, Co-existence strategy was merely a product of some fancy imagination.It was indeed a myth.
The Myth has turned Real!
Oracle Fusion Applications has unveiled a new method of adoption called Co-existence with existing Oracle Product lines.In order to achieve value from Fusion Applications, customers don't have to upgrade or migrate their existing systems to Fusion Applications. Customers can protect their current investment on existing implementations while trying to add new functionality using Fusion Apps.
Where Does Co-Existence Stop?
The co-existence processes extends across all major product lines, including Oracle's Siebel CRM, People Soft, JD Edwards and Oracle E-Business Suite.For example: Fusion Account hub is a new product in Fusion Applications which is supposed to co-exist with Oracle EBS R12 and the integration is supposed to be Out of box between R12 GL and Fusion Accounting hub.
Some of the supported Co-existence modesl include Oracle Fusion Incentive Compensation with Oracle E-Business Suite CRM and HCM or Oracle Fusion Incentive Compensation with PeopleSoft HCM.
So What is the advantage of this Co-existence model?
* First of all, you dont need rip off your current deployments to take advantage of Fusion Applications.* For Example if Company ACME Limited has Oracle R12 CRM and plan to add some of the Incentive Compensation capabilities in Fusion.
Why? Because of some of the new capabilities like Territory and Quota Management!
* Can ACME do it seamlessly?
YES. Because ACME does not need to migrate their current CRM to Fusion inorder to take advantage of Fusion Incentive Compensation modules.
*ACME can implement Fusion Incentive Compensation and co-exist with their EBS CRM module and take advantage of the modular approach.
* So ACME gets a lot of flexibility to plan and implement projects in a small scale approach rather than go with a Big Bang approach on the implementation.