How to quickly implement Oracle Cloud Solution

Short URL: https://goo.gl/tGvqso

In his article 'Strategies to implement Oracle Cloud ERP better, faster and cheaper', Mr.Eric Kimberling of Third-stage Consulting, makes the following recommendations

1. Develop a solid strategy before the implementation begins

2. Create a reasonable implementation plan

3. Define your level 2 and Level 3 business processes

4. Develop a business case and benefits realization plan

5. Mobilize your project resources.

As you can see all these are generic steps for any ERP implementation and not specific to Oracle Cloud implementation.Mr.Kimberling mentions as such.

Based on my experience in implementing Oracle Cloud Solutions, I want to point out the following points specific to Oracle Cloud Implementations.

One, direct, point to point integration to Oracle cloud is not possible. Which means that once the data is pushed into cloud, you cannot add custom validations in your integration program. There are no 'interface tables' as there are in EBS where you can add pl/sql code logic. Also to ensure data security, you have to add encryption / decryption programs in your input data.

Two, PL/SQL is mostly redundant. Ensure to plan for minimal customizations and be ready for changes to your business processes in line with the application requirements. Here Organizational Change Management assumes a lot of importance.

Three, template driven data conversion is another new feature. This means that the SI can share the templates at the beginning of the program and data conversion can be checked and refined during all the stages of implementation. You do not need a specific 'data conversion'  phase in your project. You also do not need additional technical developer for data conversion.This has implications for project management, scheduling and gate acceptance.

Four, the concepts of data sets allows you to optimize your sub-master data like payment terms, product groups etc, You can have some of the sub-masters under a common data set and others under Org Specific data sets. This avoids unnecessary data duplication. This can be planned early in the project cycle.

Five, reports preparation is both simple and complex. Simple because you have the flexibility of creating many reports on your own. Complex because, you have minimal flexibility in run-time parameterization of reports. This means that you can plan the report requirements early in the project cycle.

I do understand that these points are more technical in nature. My experience is that most of these are management and planning issues and not a technical issues.