Migrations: Why Face Them?
Oracle JD Edwards EnterpriseOne pode responder suficientemente rápido às mudanças que ocorrem no mercado e nos processos de negócio. Assim, atualizar o ERP, ao longo do tempo, promove vantagens competitivas pela velocidade e qualidade de como o sistema reagirá a estas mudanças.
Among other specific objectives, a migration project will bring the following benefits to your company:
- Risk Reduction: Uma versão atualizada do ERP suporta as últimas atualizações de sistema, envolvendo security de internet e dados corporativos.
- Rewards Redemption: Com a versão atualizada do ERP, as empresas conseguem aproveitar as centenas de melhorias e disponibilizar novos módulos para utilização.
- Use of Research Conducted by Oracle: A atualização do ERP permite ao cliente que ele aproveite os milhões de dólares investidos, pela Oracle, em pesquisas e desenvolvimento.
- 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: One ERP atualizado cobre uma maior variedade de requerimentos legais.
- ROI achievement: Migration positions the organization for better results related to better reporting, more productive users and lower cost of ownership.
Migrações Oracle JD Edwards EnterpriseOne
Desde o lançamento do JD Edwards pela Oracle, the MPL vem se aprofundando nas melhorias disponibilizadas em cada versão, através dos diversos projetos de migração junto à base instalada e implantação em novos clients.
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.