The JDE Connection: Episode 63 – Securing POs, Data Selection, Hyper Exits, and more
-
Posted by Quest Editor
- Last updated 5/30/25
- Share

Hosted by Chandra Wobschall and Paul Houtkooper
This episode is brought to you by AllOut Security.
Hey there, JDE Connection listeners! We’re back with another episode in our security series>. From processing options to exclusive application access, this episode is all about giving you the practical tips you need to stay in control of your JDE environment. And yes—we’re back to weekend recording mode, which means coffee in hand and punchy commentary guaranteed.
What We Covered
We picked up right where we left off in Episode 60 and explored several more Security Workbench types, including:
- Processing Option Security (Type 5) Want to prevent users from changing processing option values or selecting the wrong version of a report? Type 5 lets you lock it down.
- Data Selection Security (Type 7) This one’s specific to the web client. It helps ensure users can’t change data selection criteria when submitting UBEs—especially important for preventing accidental (or intentional) report changes.
- Hyper Exit Security (Type 6) This gives you control over row and form exits—like accessing data selection or processing options from Work with Batch Versions. This also includes controlling whether users even see the row or form exit menu options.
- Tab Security (Type 8) Restrict user access to specific tabs in interactive applications. Handy when you want to hide sensitive data—think salary info in HR or category codes in the Address Book.
- Exclusive Application Security (Type 9) Gives a user access to specific applications—even when they’re otherwise restricted from seeing the data (e.g., a payroll user needs access to salary info for one report). Think of it as a precision exception tool.
Quick Recap: Hierarchies and Type Codes
We also covered the security hierarchy JD Edwards follows:
- Starts at the user level for Version, then Batch, then *ALL
- Then checks the group level for Version, then Batch, then *ALL
- Then checks *PUBLIC for Version, then Batch, then *ALL
And Chandra walked us through which type codes go with which security functions:
- Type 1: Action Security
- Type 2: Column Security
- Type 3: Application Security
- Type 4: Row Security
- Type 5: Processing Options
- Type 6: Hyper Exit
- Type 7: Data Selection
- Type 8: Tab
- Type 9: Exclusive App Access
Lessons from the Field
We talked about real-world use cases, like preventing users from messing up data selection on shared versions, comparing processing options between environments, and how BrightView secures sensitive apps in time entry and fixed assets. Chandra pointed out that there are third-party tools that make it easier to compare version settings across environments (and upgrades).
Midwesternism of the Week
It wouldn’t be a JDE Connection episode without a little regional flavor. This week Paul gave us a crash course on this classic Midwest tavern game—a competitive, fast-paced way to decide who’s picking up the next round. (Spoiler: He’s got a lot more experience than Chandra.)
Wrapping It Up
Security in JD Edwards can feel like a beast—but with the right strategies and understanding of each type, you can build a system that’s not only protected but user-friendly.
Have your own security story, audit horror, or version mishap to share? Reach out at [email protected].
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.