Planning for Conversions and Dual Maintenance During an Upgrade

3rd March 2016

by

When preparing for an upgrade, it’s easy to focus on the big things – the project team, the timeline, the actual cutover – and leave the other, more detailed decisions to be made “on the fly”. However, that inevitably leads to a rushed decision, often made by a single person, and sometimes things can fall through the cracks. These items may not make or break the upgrade as a whole, but they definitely have an impact on the project.

One of these detailed decisions involves determining how you will handle Conversions and Dual Maintenance during the life of the project. Typically, during an upgrade, a single object migration will be performed, with several mock cutovers of data executed prior to go live.  In addition to the object development code freeze, it’s important to analyze what will be migrated initially, and what will be preserved during mock cutovers.

Every customer organization has configured their own JDE environment over time to meet their own needs. In addition to object customizations, there are object versions, custom menus, UDCs, users, passwords and several other items which are unique to your setup and should be preserved during an upgrade. All of these items combine to make your unique JD Edwards environments work for you, and, during an upgrade, it’s important to determine if and how to preserve these items.

Before you decide, you may want to do some analysis, to ensure you are migrating what you need and planning for dual maintenance during the upgrade.  Some items to consider ahead of time:

  • Customizations: Number and critical nature of each. Are the customizations still necessary? Are they easily recreated?
  • Scheduler: Review scheduled jobs, and determine if the schedules are running at the optimum times, with specific scheduler versions that are secured.
  • History: Do you require the Submitted Jobs History, or Scheduler History for some reason? Do users expect to see their Submitted Jobs from the prior release, after go-live?
  • Security: Review user accounts and roles. Is there cleanup to be done before migration?

Possible dual maintenance candidates:

  • User-Defined Codes (UDCs)
  • User Overrides – Grid formats, Favorites, Advanced Queries
  • Security records – User IDs, Roles, Passwords

As you plan for your upgrade, make sure to spend some time reviewing the affected objects and data to determine the best way to handle the migration tasks, and focusing on how tasks will be executed.  Things such as Grid Customizations may not seem important; after all, those can be recreated, right?  But, to users, these are important tools they will use to do their job on Day One after an upgrade. To avoid configuration loss and rework, take some time to create your Conversions and Dual Maintenance plan document.

To get started, sign up below to access our private content* and download our Conversion and Dual Maintenance Decision Template and make sure to review and discuss with your team all the items outlined in the document.

Login below to download:

Not registered? Request access here:

* EmeraldCube approval is required to gain access to private content. We generally reject requests from Hotmail, Yahoo and Gmail. If you do not have a work email address, please email info@emerald-cube.com to request permission. Please include your full name and company information.

Comments are closed.

Want to know more? Contact Us

FROM BLOG