JDEtips Data Inspector

Make sense of your JD Edwards database

JDEtips Data Inspector turns JD Edwards' cryptic tables, columns, and codes into plain English — so you can find the right table, understand every field, and read the data without an ERP decoder ring.

Why JDEtips?

JD Edwards stores everything across thousands of tables with names like F4211 and columns like SDDCTO. What they mean lives in a separate data dictionary, dates are encoded integers, and values are cross-referenced codes. Answering “which table holds sales orders?” or “what does this column mean?” normally takes deep ERP knowledge and a lot of digging.

This app was built to make that instant. JDEtips Data Inspector reads JD Edwards' own data dictionary and object librarian to let you search the table structure and find the related information behind the data — descriptions, help text, code meanings, and links between them — all read-only, on your own server.

What you can do

🔍

Find tables by meaning

Search by description — “sales order”, “address”, “work order” — and get the matching tables with live row counts, so you see which actually hold data.

Go to Find →

📋

Browse & describe

List a schema's tables and describe any one: every column with its plain-English name, hover for the full glossary, and flags for UDC-backed fields.

Go to Browse →

▶

Query the data

Run read-only SQL with sortable, filterable, paginated results. Dates and codes are decoded for you; save and reuse your queries; export to CSV.

Go to Query →

🏷️

Decode UDCs

Look up any User Defined Code table to turn short codes into their meanings (e.g. document type SO → Sales Order).

Go to UDC →

📅

Convert Julian dates

Translate JDE's CYYDDD integer dates to real dates and back — handy for filters and spot checks.

Go to Julian →

🔗

Explore relationships

See how tables link by shared keys, trace one value (a supplier, order, item) across every table it touches, and walk header → detail → ledger chains.

Go to Relate →

🦉

CNC console

Proactively monitor security, objects & UDOs, OMW, environments, batch, and red-alert health — a growing library of one-click checks, guided by Sage the owl.

Go to CNC →

❓

Learn the ropes

A short primer on JDE schemas, table naming, column aliases, Julian dates, and UDCs — plus how each tab works.

Go to Help →

Built-in intelligence

Plain-English fields — every column shows its data-dictionary description, with full F1 help on hover.
Decoded dates — JDE Julian integers become real dates automatically in previews and query results.
Decoded codes — UDC-backed values show their meaning inline, right next to the code.
Related info, one click away — jump from a column to its dictionary entry, or from a UDC reference straight to its code list.

Everything is strictly read-only. Nothing you do here can change JD Edwards data.

💡

You're browsing sample data — the JD Edwards demo (“Vision”) dataset in TESTDTA. The tables, columns, and codes match a real JD Edwards system so you can learn the structure, but the records are illustrative, not live business data.

Schema Filter ⓘ how schemas work

Pick a schema and click “List tables”.

Select a table to describe it. Then click a column for its data-dictionary entry, or “Preview 25 rows”.

Limit raw dates read-only SELECT / WITH · Ctrl+Enter runs

examples:

Keyword row counts searches table descriptions · click a result to describe it

Product code Code type User Defined Codes — the ERP’s lookup/validation lists

Value JDE stores dates as CYYDDD integers

Follow the links

JD Edwards spreads a business fact across many tables joined by shared keys. Explore what a table connects to, trace a single value everywhere it appears, and jump along header → detail → ledger chains.

🧭 Explore a table's relationships

See the tables it shares keys with (AN8, DOCO, MCU…), its header/detail family, and a map.

🎯 Where used — trace a value (360°)

Pick what you're tracing, then enter its value.

CNC Console

How to use JDEtips Data Inspector

A read-only window into your JD Edwards EnterpriseOne Oracle database. It translates JDE’s cryptic names and codes into plain English using the ERP’s own data dictionary. Nothing you do here can change data.

The tabs

Browse: Pick a schema, list its tables (filter with a SQL LIKE like F41%), then click a table to describe it — every column with its data-dictionary description and, where relevant, the UDC table it’s validated against. Click a column name to open its full dictionary entry; click “Preview 25 rows” to see real data with dates and codes decoded.
Query: Run any read-only SELECT/WITH. Results are sortable (click a header) and filterable. Julian date columns get a decoded _DATE companion; UDC columns show the code meaning on hover. ★ Save useful queries and re-run Recent ones. Export with Download CSV.
Find: Don’t know the table name? Search by description — “sales order”, “address”, “work order”. Results show live row counts (populated tables first). Click a result to describe it.
UDC: Decode a User Defined Code table. Enter a product code + code type (e.g. 00 / DT) to list its codes, or just a product code to list its code types.
Julian: Convert between a JDE Julian integer (CYYDDD) and a normal date, in either direction.

JDE concepts, briefly

Schemas — business data lives in TESTDTA; control tables (UDCs, menus) in TESTCTL; the data dictionary in DD920; object descriptions in OL920. The tool finds the right one for you.
Table names — tables are F + numbers (e.g. F0101 = Address Book Master). Use Find to map English → table.
Columns — each is a 2-letter table prefix + a data-item alias (e.g. F0101.ABAN8 → alias AN8 = “Address Number”).
Julian dates — stored as CYYDDD integers (e.g. 125001 = 2025-01-01). Auto-decoded in previews and query results.
UDCs — short codes validated against lookup lists (e.g. document type SO = Sales Order). The UDC tab decodes them.

Try it

Safety: the server only ever issues read-only queries.

Database connection

Choose which JD Edwards database this tool reads. Settings are saved on this server and take effect immediately — no restart. Only read-only access is used.

Database type

Oracle connection

Host Port Service name SID User Password Mode Client lib dir

SQL Server connection

Host Instance Port Database User Password Trust server certificate Encrypt connection

JD Edwards schemas (Release 9.2)

Prefilled with the standard Release 9.2 owners. Pick an environment or type your own. On SQL Server these are schemas inside the database above (e.g. TESTDTA.F0101).

Data schema (Business Data) Your transaction & master data — Address Book, Sales Orders, G/L, Inventory. 9.2: PRODDTA (Production), CRPDTA (CRP), TESTDTA (Test/Dev). Control schema (Control Tables) Shared configuration — User Defined Codes (F0004/F0005), menus, next numbers. 9.2: PRODCTL, CRPCTL, TESTCTL. Data Dictionary Field descriptions, F1 help/glossary text, and edit rules (F9200 / F9202 / F9210). Release 9.2: DD920. Object Librarian Object names & descriptions — table and report titles (F9860). Release 9.2: OL920.

These match a standard Release 9.2 install. When the tool is connected, the list is refreshed with the actual schemas found in your database.

Credentials are stored in config/connection.json on this server (like a .env file) — keep the server secured. Leave a password blank to keep the currently saved one.