Migrations: Why face them?

Oracle JD Edwards EnterpriseOne can respond quickly enough to changes in the marketplace and in business processes. Thus, updating the ERP over time, promotes competitive advantages for the speed and quality of how the system will react to these changes.

Among other specific objectives, an upgrade project will bring the following benefits to your company:

  • Risk Reduction: An updated version of ERP supports the latest system updates, involving internet security and corporate data.
  • Rewards Redemption: With the upgraded version of ERP, companies can take advantage of hundreds of enhancements and deploy new modules for use.
  • Leveraging Oracle Research: ERP upgrade enables the customer to leverage the millions of dollars invested by Oracle in research and development.
  • Teamwork Maintenance: With an updated software, users and administrators work with a modern application, generating positive work experiences.
  • Remote Reach: Migration enables the use of native JDE applications on mobile platforms.
  • New Legal Requirements: An updated ERP covers a wider range of legal requirements.
  • Realization of ROI: Migration positions the organization to achieve better results related to better reporting, more productive users and lower ownership costs.

Upgrade Oracle JD Edwards EnterpriseOne

Since the launch of JD Edwards by Oracle, MPL has been delving deeper into the improvements available in each version, through the various upgrade projects with the installed base and deployment to new customers.

Basically, 2 types of upgrade projects can be conducted:

  1. Tools Version Upgrade
    In some cases, in order for the client to benefit from improvements made available to the general system, there is no need to upgrade the version of the application, but only the version of tools.
  2. Application Version Upgrade
    Every 5 years, at least, it is a good idea to start an upgrade project in your company.
    When we talk about application version upgrade, we can adopt 2 different policies for the project.
    The first one is a conventional upgrade, where all the customizations are analyzed and a retrofitted in the new version environment. After that, the new version is then released for key-users to test it.
    The second policy deals with an “exception” upgrade, where shortly after installing the new version, the environment is made available for key-users for test it. According test´s results, the customizations are fed back into the new version, when necessary.

Tools that can help in an Upgrade Process

In the market, there are several tools that can aid in an Upgrade Process, be it a Tools or Application Upgrade.

These tools can identify objects that have actually undergone code change, guide the tests of certain functionality within an application, create a script of tests that can be replicated indefinitely or you can even use them to allow your company to perform small upgrades, giving small “jumps” constantly, instead of a big “jump” every 5 years.

4 Important Questions

Regardless of the upgrade project to be implemented in your company, there are some important points to address:

  1. Upgrade the Tools version regularly
  2. Plan the project before starting it to determine the retrofit and testing strategy
  3. Use in your upgrade project the best resources in your organization.
  4. Simulate GO LIVE preparation activities several times before the final upgrade.