In this episode, hosts Chandra and Paul welcome Pete Cotton, a Business Analyst at Irex Services, LLC, to discuss the process and methodology of decustomizing JD Edwards EnterpriseOne (E1) instances. The conversation kicks off with the importance of reducing customizations to streamline the ability to stay code current and minimize upgrade overhead. Pete elaborates on the methodologies Irex employs, which include cataloging all customizations, identifying those that can be retired, and exploring the various JD Edwards user-defined object (UDO) tools such as form personalizations, form extensions, and orchestrations to replace custom code. The episode highlights the significance of understanding customizations at a granular level and leveraging new capabilities within JD Edwards to achieve business goals without extensive retrofitting. 

02:25 A brief history of how we got here 

05:58 Customizing the base object vs cloning the object debate 

08:35 What is the goal of de-customization? 

09:35 Step 1: Inventory and catalog your customizations 

13:51 Step 2: Retire what you don’t need 

14:58 Step 3: Replace customizations with User-Defined Objects (UDO) 

17:48 Real world examples of customizations that can be replaced with UDO’s 

24:49 Summary of what UDO to use when 

25:39 Midwesternism of the day 

Resources: 

Custom Object Analyzer: https://docs.oracle.com/en/applications/jd-edwards/change-management/9.2.x/eotsu/customization-object-analyzer.html 

Custom Object Analyzer Tutorial: https://www.oracle.com/webfolder/technetwork/tutorials/jdedwards/Object%20Analyzer/COA.mp4 

Understanding Customization Object Analyzer (Doc ID 1499756.1) https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=115464695465036&parent=EXTERNAL_SEARCH&sourceId=BULLETIN&id=1499756.1&_afrWindowMode=0&_adf.ctrl-state=ax2thxh30_4 

If you have concerns or feedback on this episode or ideas for future episodes, please contact us at [email protected].