Hosted by Chandra Wobschall and Paul Houtkooper

Welcome back, JDE Connection listeners! This week, we discuss some troubleshooting basics and how understanding JDE structures can help you quickly diagnose and resolve issues.

The Method Behind the Madness

Troubleshooting in JD Edwards can feel overwhelming, but there’s actually a well-thought-out pattern behind the naming conventions and object structures. The more familiar you are with these conventions, the easier it becomes to navigate the system, whether you’re tracking down a rogue data issue or deciphering what a batch process actually does.

Breaking Down the Basics

We kicked things off by revisiting JD Edwards’ table naming conventions. Here are some key takeaways:

• Tables (Fxxxx): The letter “F” designates a file (or table), followed by system code and then object type. For example:
  • F0101 – where “01” indicates Address Book and “01” designates a header (parent) table
  • F4311 – where “43” indicates Procurement and “11” designates a detail (child) table
  • F42199 – where “42” indicates Sales Management and “99” designates a transaction history table

Knowing these simple rules makes it easier to locate the right tables when troubleshooting data inconsistencies. It also can aid in identifying the corresponding interactive applications responsible for managing the data in those tables.

• Interactive Applications (Pxxxx): When looking at a JDE application, the “P” prefix indicates it’s an interactive program. The following numbers generally align with the corresponding table. Example:
  • P0101 corresponds to the F0101 table
  • P1721 corresponds to the F1721 table

Conversely, if you’re in an interactive application and want to know what primary tables it controls, you can reverse the exercise. So, Purchase Order Entry, P4310, manages the PO Header (F4301) and PO Detail (F4311).

The Big Mystery: Which UBEs Update Data?

One of the biggest frustrations can be figuring out which reports (UBEs) actually update data. We discussed how there isn’t a clear-cut naming convention for this, but there are a few ways to investigate:

• Cross-reference tools: You can look up tables used by an application in the cross-reference utility.
• Audit fields: Use table audit fields (user, machine, date/time) to track updates.
• Developer insights: When in doubt, ask a developer to check the code!
• Processing options: Check for a “Proof or Final Mode” option.

Chandra’s Favorite Troubleshooting Tools

We close out this troubleshooting episode with a list of Chandra’s other favorite resources she uses daily. We’ll cover these in more detail with real world examples in future episodes,

1. Start with Work With Submitted Jobs (WSJ) – This will tell you what reports were run and with what parameters.
2. Leverage Business Object Reservations (P00095) – If an object is locked, check here to see who’s holding it.
3. Check User Security (P0092 & P00950) – If someone can’t access a program, security settings might be blocking them.
4. Use AAIs & DMAAIs – Understanding your Automatic Accounting Instructions can be a game-changer.
5. Verify UDCs – Confirming the right User Defined Code settings can save time. Note – Don’t delete the “BLANK”!

Midwesternism of the Week

To wrap up, we continued our winter outdoor activities theme with a nod to a very popular event in the north. There’s something nostalgic and pure about playing this sport the way Mother Nature intended—outside, on a frozen lake, battling the elements. Whether you’re a fan or not, this event is an awesome display of skill, endurance, and community spirit.

Keep the Conversation Going

Have questions or want to share your own troubleshooting tips? 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.