Any JDE application release upgrade is a base implementation followed by table conversions, spec merge, code retrofits, acceptance testing, production upgrade and go live.
A lot of the tasks involved in JDE implementation are also part of any JDE Upgrade but before starting the actual upgrade several tasks are undertaken to ensure a successful upgrade and go-live.
Following our byDesign methodology here is how we approach JDE upgrades and try to finish the process in way less than 100 days.

  • Archive!!
    One of the common mistakes a lot of consultants make is ignore the importance of data archiving/purging and reclaiming storage. With proper archiving and purging one can drastically reduce the time it takes to run table conversions which is one of the key components of any JDE release upgrade.
    Even if you are not planning for an application upgrade it’s always a good practice to use an archive tool to keep your table sizes in check.
    During our pre upgrade analysis for a client we determined that their production data size was around 400GB. Further analysis showed that out of 400 GB 216GB was being used by 9 business data tables alone (over 50%) not to mention temp index and tables scans taking place on some of them… think what that does to the table conversion process. contact us to know more.
  • Platform, Database, Server and OS selection.
    Even though you are running JDE there may be a need to move to a different database or OS platform due to cost or other third party integration needs. Here is where we factor in the change, how it ties into the upgrade process and how we can migrate the data over to the new platform and then perform the upgrade.
  • Sizing Recommendation.
    Very important to get the new servers specs correct. With a new release comes newer functionalities and more complex function execution may require more resources than your current release, growth factor, need for more instances and changes to the overall architecture of the new release makes this step a critical step in the upgrade planning and implementation process.
  • Object Modification Audit and proper object flagging.
  • Current third party and planned third party software integration audit and analysis.
  • Environment and Infrastructure Design.
    Based on the from release, things may become drastically different from both technical and functional perspective. Use of fat clients to run apps can be a thing of the past, terminal servers and citrix will get replaced with JAS which means one will need to factor in new servers, new web solutions and a completely new approach to how things get designed and implemented and eventually used.
  • Technical Implementation
    The first phase of the two part process is the technical portion of the upgrade where one environment is upgraded to the new release with customization brought over making the environment ready for testing.
  • Function Implementation.
    Second part of the process involves the functional tasks executed by functional analysts and application developers to get the new release, applications and the functionality setup according to business needs.
  • Security maintenance and configuration
    During the upgrade existing security information from the old release will be brought over but based on the from release security can be drastically different. If the from release is anything lower than 8.9 groups will be replaced by Roles and new security configuration will be required and new relationships will need be created.
  • Stress, functional and application testing with OATS (Oracle Application Testing Suite) or similar.
    A key element during post upgrade is application stress testing to make sure everything is performing as expected and taking proactive action before an issue becomes a problem.
  • Training
    Another important step during post upgrade is to train end users on new processes, leverage the most out of new functionalities, UI changes, thereby making it easy for end users to adapt to the new release.
  • Release of environments to end users for extensive testing and re-converting the data with more recent copy of production business data.
  • Production Upgrade and Go-Live
    After extensive technical and functional testing the long journey ends with production upgrade (normally done over a weekend) and Go-Live!
  • Ongoing technical and functional help. We will be there whenever you need us after Go-Live. Contact us and talk to our experts.