JD Edwards Migration
Migrations: Why Face Them?
Oracle JD Edwards EnterpriseOne can respond quickly enough to changes in the market and business processes. Thus, updating the ERP, over time, promotes competitive advantages due to the speed and quality of how the system will react to these changes.
Among other specific objectives, a migration project will bring the following benefits to your company:
- Risk Reduction: An updated version of the ERP supports the latest system updates, involving internet security and corporate data.
- Rewards Redemption: With the updated version of ERP, companies can take advantage of hundreds of improvements and make new modules available for use.
- Use of Research Conducted by Oracle: Upgrading the ERP allows the customer to take advantage of the millions of dollars invested by Oracle in research and development.
- Maintenance of the Work Team: With updated software, users and administrators work with a modern application, generating positive work experiences.
- Remote Range: The migration allows the use of native JD Edwards applications on mobile platforms.
- Replacement of Legal Requirements: An updated ERP covers a wider range of legal requirements.
- ROI achievement: Migration positions the organization for better results related to better reporting, more productive users and lower cost of ownership.
Oracle JD Edwards EnterpriseOne Migrations
Since the launch of JD Edwards by Oracle, MPL has been deepening the improvements made available in each version, through the various migration projects with the installed base and implementation in new customers.
Basically, 2 types of migration can be conducted:
- Tools version migration – In some cases, in order for the customer to benefit from improvements made available in the general scope of the system, there is no need to migrate the application version, but only the Tools version.
- Application version migration – It is good practice that every, at most, 5 years of use, a migration of the version of the application installed in your company is carried out.
When we talk about application version migration, we can adopt 2 different policies for the project.
The first deals with a conventional migration, where all customizations are analyzed and these customizations are retrofitted to the new version so that the new environment is released for testing by key users.
The second policy deals with a migration “by exception”, where soon after installing the new version, the environment is made available for testing by key users. From the tests performed, the customizations are fed back into the new version, when necessary.
Tools that can help with a migration process
In the market, there are several tools that can help in a Migration process, be it a Migration of Tools or of Application: identifying objects that have actually undergone code changes, guiding the tests of certain functionality within an application, creating a tests that can be replicated indefinitely or you can also use tools that allow your company to carry out small migrations, making small “jumps” constantly, in contrast to a large “leap” every 5 years.
4 Important Questions
Regardless of the migration project to be implemented in your company, there are some important points that must be observed:
- Migrate Tools Version Regularly
- Plan the migration before starting the project to determine the retrofit and testing strategy
- Use your organization's best resources in your migration project.
- Simulate GO LIVE staging activities multiple times before final migration.