Oracle CRM On Demand Exposed -
Customization & Integration

Perhaps the most glaring disadvantage of the Oracle CRM On Demand is its limitation on customization. From the beginning the product could only handle a maximum of three custom objects, although many analysts expected this restriction to be removed some time ago. This seems to indicate that the Oracle is struggling to change the On Demand infrastructure to accommodate greater degrees of customization. Since the CRM On demand product was built as a multi-tenant architecture, Oracle must now reverse engineer it to handle greater customization needs and make the client code base independent for it to operate in isolated-tenancy architecture.

Since Oracle tends to pursue enterprise-sized clients with a high potential to use its full ERP suite, this limit on customization can be a major limitation to the future flexibility required from organizations with more complex sales processes. We do not expect major changes to Oracle’s approach to customization – they want On Demand CRM to drive sales of ERP and if you adhere to the ‘Oracle Way’ of approaching both systems, there is no need to change.

Free: Complete Report – Oracle CRM On Demand Exposed

To that end, Oracle On Demand has extensive and robust integration potential – provided your integration is with Oracle’s on-premise ERP software. This is a predictable approach from Mr. Ellison on down through the Oracle organization – make it easy to connect the hosted CRM to the on premise software assets and Oracle is positioned for long-term annuity revenues.

Free: Complete Report – Oracle CRM On Demand Exposed