Tom Gabriele, Product Manager
ESU (Electronic Software Updates), ASU (Application Software Updates), and SP (Software Updates)
Have you ever wondered how IT keeps your JD Edwards system up and running on the latest software and application features and functions? Ever wonder how all those "fixes" that people refer to from Oracle get implemented within your system? Oracle provides its' clients with a simple, electronic technique to update the JD Edwards system for these fixes or enhancements. The fixes and enhancements are called ESUs (Electronic Software Updates) or ASUs (Application Software Updates), they will deliver your organization with the most recent JD Edwards' foundations and applications. This way you can continue to make the most of your investment and have confidence that your system is operating as designed.
Oracle's JD Edwards EnterpriseOne Software Update process is developed to distribute the following four types of updates, each affecting numerous areas within the organization:
• Electronic Software Updates (or ESU) is used to fix problems reported on a specific JD Edwards EnterpriseOne application or report. These are typically individual fixes to the particular application or report and are downloaded individually. All ESUs are accessed and downloaded from the Oracle Update Center.
• Application Software Updates (or ASUs) are sets of enhancements for specific functional areas within the EnterpriseOne applications. Like ESUs, these fixes support individual functionality; however, unlike ESUs, ASUs are distributed via a CD and requested by going to the Oracle edelivery.oracle.com site.
• Service Packs (or SPs) are groups of all currently available fixes, and in some cases, enhancements. Just like ASUs, service packs are distributed via CD and requested on the edelivery.oracle.com site.
• Last but not least, what are Tools Releases? These are groups of all fixes to the JD Edwards EnterpriseOne foundation (System) code. Think of that layer as being similar to the Windows or Apple operating systems. Tools releases contain things like the User Defined Object capabilities that you've been hearing so much about lately.
All of these deployments need to be installed on your JD Edwards servers, transferred to the appropriate environment, and merged with any modifications as expected before they are promoted to production. Taking any update is not a "simple" step, but should be approached and managed as would any other project. Organizations ought to follow at a minimum a basic project flow consisting of the following steps to ensure a well-timed and successful update.
• Prepare for the update and understand the areas, functions, integrations, and systems impacted.
• Acquire the update from the appropriate source.
• Install the update on the JD Edwards deployment server.
• Deploy the updates to the Pristine and Development environments for testing and validation.
• Retrofit custom modifications/integrations and complete all business processes that are impacted by the update.
• Re-validate the applied update in a "quarantine" or pre-production environment.
• Rollout the update to production users.
As you would expect for those organizations that feel that they do not have the means, skillsets or time, in order to achieve these updates, they can participate in a secure business like GSI who specializes in the management and control of these procedures within an Organization. By doing so, you can take full advantage of your investment in your JD Edwards system by continually being "code current" and in the know on the newest technology, software and functionality.
Have a question about JD Edwards, please contact us at inquiries@GetGSI.com!