Hosted by Chandra Wobschall and Paul Houtkooper

Hey JDE Connection listeners – Chandra here! This week it’s just me. Paul is off in Europe presenting and visiting customers (or lobbying for developers to be recognized as the unsung heroes of humanity). We’ll fact-check that when he’s back stateside, but in the meantime, I’m flying solo and leaning into something very BA-friendly: P95110 – Search Event Rule Objects.

If you’ve ever wanted to see event rules without opening up OMW, checking objects out, or risking accidental changes, this episode—and this post—is for you.

Why We’re Talking About P95110 Now

We walked through Form Design Aid (FDA) in Episodes 81, 83, and 85—how to get into FDA, follow event rules, and better understand what applications and functions are really doing behind the scenes. We all get that question, “Can someone tell me what table this application updates?”

Traditionally, that meant:

• Asking a developer or CNC
• Waiting a couple of days while they juggle higher-priority work
• Hoping for a clean explanation you can actually use

P95110 gives us another option—one that doesn’t require a project, OMW, or opening FDA at all. It’s like a safe viewing window into event rules, designed for those of us who want insight without the “what if I break something?” anxiety.

What P95110 – Search Event Rule Objects Actually Does

From a full client, when you fast-path to P95110 – Search Event Rule Objects, you can:

• Choose what kind of objects you want to look at:
  • Application objects
  • Report objects
  • Named Event Rule (NER) / business function objects
• From there you can
  • Browse the event rules, or
  • Print them out

For BAs and system analysts, that’s huge. It means you can explore logic and behavior without the risk of accidentally modifying anything.

Why This Is So Helpful for BAs?

Here’s where P95110 really becomes a power tool in our toolbox:

You can use it to:

• Understand what an application is doing
• Validate before logging a dev request
• Troubleshoot strange behavior
• Respond faster to Oracle Support
• Write sharper requirements

In short: it helps us be more independent, more informed, and more effective partners to our technical teams.

One Important Limitation

There is one key caveat to keep in mind: If Support (or you) needs the event rules for a C business function from the source file itself, you still have to go through the full client and source code, just like we discussed in our earlier FDA-focused episodes. P95110 is fantastic for application, report, and NER objects—but it doesn’t replace every single path into source.

A Little Salad

And in true Midwestern fashion, our closing story involved a very pretty holiday side dish that looked sweet, turned out… tangy, and reminded us that you never quite know what surprise ingredient might be hiding in a molded, fruit-filled “salad.” Let’s just say expectations and reality did not match on that first bite.

For questions, feedback, or ideas for future episodes, reach out at thejdeconnection@questoraclecommunity.org.

Until next time, let’s keep learning, sharing, and 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.