In this episode of the JDE Connection, hosts Chandra and Paul dive into the topic of managing and understanding JD Edwards baseline ESUs (Electronic Software Updates), focusing particularly on how they affect system updates and customizations. Chandra shares her real-life frustrations working with a third-party software integration, which uncovered missing bugs tied to a baseline ESU. Paul provides a thorough explanation of what baselines are, why they matter, and how they reset update dependencies, making them more manageable for customers. The conversation also covers strategies for interpreting lengthy impact analysis reports, the importance of object usage tracking, and the challenges of retrofitting custom objects.   01:10 Compliance Training Badge Incentives and Jury Duty  04:34 No Jury Duty, Heat, and Construction Projects  06:20 Project Frustrations  08:15 So....What is a Baseline?  13:50 Impact Analysis Panic Button  16:50 Object Usage Tracking to the Rescue  20:12 Midwesternism of the Day  Resources: Baseline FAQ’s: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=104746788911911&parent=EXTERNAL_SEARCH&sourceId=FAQ&id=626402.1&_afrWindowMode=0&_adf.ctrl-state=3tbauqq3x_4 Performing Impact Analysis: https://docs.oracle.com/en/applications/jd-edwards/change-management/9.2.x/eotsu/performing-an-impact-analysis-1.html  Understanding Object Usage Tracking: https://docs.oracle.com/en/applications/jd-edwards/change-management/9.2.x/eotsu/understanding-object-usage-tracking.html  If you have concerns or feedback on this episode or ideas for future episodes, please contact us at [email protected]  

Ver todos los episodios