Hosted by Chandra Wobschall and Paul Houtkooper

Hey JDE Connection listeners — it’s Chandra and Paul, and this week we’re digging into the kind of conversation that only a JD Edwards business analyst could love (and maybe hate a little too): baselines, impact analysis, and what happens when third-party vendors flag missing fixes in your system.

It all started with a routine vendor implementation that took a sharp turn into “wait, what is a baseline ESU?” territory.

Compliance Training, Jury Duty, and Construction Chaos

Before we got technical, we opened the show with a little life update. Paul’s been surviving the annual compliance training marathon (and not earning a badge… yet), narrowly avoiding jury duty, and clearly violating multiple sections of his annual training by simply existing.

Meanwhile, Chandra is navigating the heat, home construction, and daily dog guilt trips. But hey — renderings have arrived, and the patio project is officially underway. (It’s not a teepee, in case you were wondering.)

So… What Is a Baseline?

Let’s break it down. A baseline ESU is like a software reset point — a way for Oracle to simplify ESU dependencies. Rather than stacking every change you’ve ever made, a baseline lets you install one consolidated version and start fresh. It breaks the “A needs B needs C needs D” dependency chain and reduces the risk of pulling in far more than you need.

In this case, Chandra’s vendor noted two fixes that weren’t in her system. After tracking them down in baseline ESU JN20168, her CNC team pulled the update and ran an impact analysis.

The JD Edwards Impact Analysis Panic Button

Here’s where things got spicy.

Pages and pages of objects showed up in the report. Chandra, like many of us, looked at the sheer volume and had one thought: <Insert Midwesternism Here>

We agreed this topic deserves its own episode (stay tuned), but in short:

Impact analysis tells you what’s included in an ESU and how much of it will actually apply to your environment.

In Chandra’s case, 54 of 62 objects were going to be applied. Oof.

Of those, at least one was a custom object, which means retrofit time.

Object Usage Tracking to the Rescue

Here’s the saving grace: Chandra’s team has had Object Usage Tracking enabled for two years.

This means they can now cross-reference the ESU impact against what’s actually used in their environment. Customizations that aren’t actively used? That’s an opportunity to clean house. As Paul put it, “Just because you can retrofit something doesn’t mean you should.”

It’s not just about impact — it’s about relevance.

What We Learned

• Baseline ESUs are your friend — they help simplify installs and reduce overhead.
• Impact analysis is valuable, but it’s just the start.
• Object usage tracking helps you narrow the focus to what truly matters.
• Custom retrofits aren’t automatic — validate whether you’re even using them before investing time.
• Compliance training might be painful, but not as painful as finding out your system is 62 objects out of sync.

Midwesternism of the Day

Chandra’s go-to phrase of the week – Whether you’re facing a 20-page impact report or a State Fair food list that could wreck your macros in 15 minutes, this classic expression of surprise and frustration fits.

Also: we’re planning a live episode from the Minnesota State Fair. If you’re a Midwestern listener and want to join us for a deep-fried podcast adventure, reach out!

Have a question, a favorite expression, or thoughts on surviving ESU installs without losing your mind? Drop us an email at thejdeconnection@questoraclecommunity.org.

Until next time,

Let’s keep learning, sharing, and most importantly laughing together.

Toodles!

Missed an episode? Check out the full episode list! Also, be sure to subscribe on your favorite podcast provider, or select a provider below!

Learn More

Quest Oracle Community is where you learn. Ask questions, find answers, swap stories and connect to other JD Edwards customers and product experts in the JD Edwards Community, where you can also check out what’s happening in the Business Analyst SIG.