Once a customer has made the move to 9.2, they should be able to run code-current change event projects more frequently and more easily. Each code-current change event project will require less time and effort, will deliver value more quickly, and will put less strain on the business. It is this ability to stay code-current that will allow an organisation to make the most of the latest software developments and help them compete effectively in today’s digital economy.
One of the major challenges facing any organisation planning a code-current change event project or an upgrade is the technical retrofitting of custom or modified objects. The bigger your modified footprint, the more complex the retrofitting project is likely to be. However, each code-current change event project is also an opportunity to reduce the number of modifications and to move closer to a standardized implementation.
The longer a business leaves it between code-current change events, the bigger the technical debt it incurs. Unsupported software always represents a risk. When that software is as fundamental to the success of your business as JD Edwards EnterpriseOne, the risks become greater.
At DWS, we are always interested to understand exactly how and where Oracle’s changes impact the code. Understanding any code change is vitally important, as changes to the code can be an issue for your systems and the business.
UN5 to UN6 Change Statistics
We have downloaded UN6 and have performed some analysis on the Oracle code-changes, comparing them to a UN5 level (actually Jan 2021, so slightly more advanced than UN5 base, but still the best part of a full year of differences).
APPL: 360 diffs, 21 new objects
BSFN: 433 diffs, 64 new
BSVW: 124 diffs, 29 new
DSTR: 144 diffs, 103 new
GT: 0 diffs, 3 new
TBLE: 18 diffs, 16 new
UBE: 314 diffs, 17 new
Total: 1393 changes, 253 new objects
Over that 1-year UN5-UN6 change period, if we consider just APPL and UBE, then 5.9% have received some level of net-change.
Obviously, as you go back further in time (pre UN5) and the gap widens, then those net-change difference levels increase. As a point of interest, comparing UN6 to base E920 (some ~6 years of net-change) we see nearly 6000 changes and over 4000 new objects. Again, from an APPL and UBE perspective, almost 20% of objects have experienced a change from base E920 to UN6.
When we look at UN5 to UN6 specifically, it is interesting to note that the bulk of the new objects appearing in 2021 were in UN6 and not spread across ESUs over the course of the year, indicating Oracle possibly holding back new functionality until the update.
DWS has over 20 years’ experience working in the JD Edwards space. In that time, we have helped countless organisations meet their technical retrofit challenges. Our Dimension Analyze service provides a forensic analysis of the objects impacted by a code-current change event project. Our approach allows us to identify decommissioning opportunities and enables us to deliver fixed-price and fixed-timeline technical retrofit projects.
Having made the move to JDE E1 9.2, how can you ensure your business is well-placed to make the most of the latest features and functionality? Staying code-current means embracing the concept of continuous adoption and eliminating custom objects as and whenever you can; helping you take on and execute more, smaller, faster, smarter projects.