OperoStudio · JDE Data Tooling

The JDE schema, finally readable.

A desktop tool for the people who need to work with JDE data — analysts, integration developers, reporting builders. Browse the schema in plain language. Build data models visually. Extract clean data to CSV, JSON, or SQL.

One-time license Windows · macOS · Linux Runs locally
OperoStudio · Untitled.osm
Tables
F4211 Sales Order Detail
F0101 Address Book
F0911 Account Ledger
F4101 Item Master
F4111 Item Ledger
F0901 Account Master
F4211SO
DOCOdoc
AN8cust
LITMitem
UORGqty
F0101ADDR
AN8id
ALPHname
AT1type
Why we built it

The JDE schema isn't supposed to feel like a riddle.

JDE EnterpriseOne ships with over a thousand database tables — most of them named in five-character codes nobody can remember. F4211 for sales orders. F0911 for the general ledger. F4101 for the item master. To get data out, you either become an expert in the schema or you wait for someone who is.

OperoStudio reads the JDE Data Item Specifications and turns the schema into something humans can actually navigate. Real names alongside the F-codes. Foreign keys visible as joins. Models built by clicking, not by guessing. Extracts that come out clean the first time.

Two modules

Buy one. Buy both. Add later.

OperoStudio comes as two modules. They work standalone — or together, when you need to go from understanding the schema to producing real data.

Data Modeller

DM01_MODELLER

Visual schema browser and data model designer. Understand what's in JDE, how it joins, and what to query.

  • Full JDE schema pre-loaded with plain-language descriptions
  • Visual model canvas with drag-and-drop joins
  • Foreign-key detection and auto-suggested joins
  • Models saved as portable .osm files, version-controllable

Extracts

EX01_EXTRACTS

Turn a Data Modeller model into a working data extract. CSV, JSON, SQL, or feed it into your data warehouse.

  • One-click extract to CSV, JSON, Excel, or Parquet
  • Scheduled extracts for repeated runs
  • SQL output for warehouse ingestion (ELT)
  • Filter, transform, and join at extract time
Studio Bundle: Both modules together at a reduced price, with a single setup and unified license. Most customers start here.
How it works

From install to first extract in an hour.

OperoStudio runs on your laptop. It connects directly to the JDE database with the credentials your DBA gives you. Nothing leaves your environment.

1

Install & connect

Install the desktop app on Windows, macOS, or Linux. Add your JDE database connection — read-only credentials are enough.

2

Browse the schema

Use the table browser to find what you need. Search by topic, by F-code, by field name. Descriptions and relationships are pre-loaded.

3

Build the model

Drag tables onto the canvas. OperoStudio suggests joins. Add filters and transformations. Validate before extract.

4

Extract

One click to CSV, JSON, or your data warehouse. Schedule it for recurring runs. Save the model for reuse next time.

Use cases

Where OperoStudio pays off fastest.

Four scenarios where teams spend weeks figuring out JDE data — and where OperoStudio cuts that down to hours.

Reporting builders

Reports without the schema dive.

Your reporting team needs data for a new dashboard but doesn't know which F-table holds it. With OperoStudio they search "open invoices by customer", find the right tables, build the model, extract the data — in an afternoon, not a week.

Data warehouse

The JDE-to-warehouse pipeline.

Your data engineers need to ingest JDE into the warehouse. OperoStudio gives them a working map of the relevant tables, sample extracts to validate, and reusable models that become the source-of-truth for the ELT pipeline.

Integration projects

Know what to read before you start.

A new system needs JDE data — which tables, which fields, which joins? OperoStudio answers the discovery questions in days, not weeks. The integration spec writes itself once the model is clear.

Audit & compliance

"Show me where this happens in JDE."

When auditors ask where specific transactions live, OperoStudio gives a direct answer with a model that proves the data trail. Extract the records on demand. Document the lineage. Move on.

Questions

Frequently asked.

Don't see your question? Ask us directly.

Which JDE versions are supported?

OperoStudio supports JD Edwards EnterpriseOne 9.1 and 9.2 across all Tools Releases. The schema metadata is shipped with the product and is updated as Oracle releases new ESUs. Databases supported: Oracle, SQL Server, IBM Db2, PostgreSQL.

How does pricing work?

OperoStudio is sold as a one-time perpetual license, not a subscription. You buy the Data Modeller, Extracts, or the Studio Bundle — and you own it. Annual maintenance covers updates, schema-metadata refreshes, and support. Get in touch for a quote.

Does it run on Mac and Linux?

Yes. OperoStudio is a desktop application for Windows 10/11, macOS 12+, and Linux (Ubuntu, RHEL, SUSE — recent versions). Same feature set across all platforms.

What does the app need to access JDE?

A read-only database user with select privileges on the JDE schema. That's it. OperoStudio doesn't connect to the JDE web client or change anything in JDE — it queries the database directly.

For DB2 on IBMi, the connection uses the IBM JDBC driver. For Oracle/SQL Server/PostgreSQL, standard JDBC drivers are bundled.

Where does the data go? Is anything sent to your servers?

Nothing. OperoStudio runs entirely on your laptop. Data queried from JDE stays on your machine (or your local network if you're extracting to a network share). We never see your business data.

The only thing that talks to our servers is the license activation. After that, the app works offline.

Can models be shared between team members?

Yes. Models are saved as portable .osm files — version-controllable, shareable via Git, OneDrive, or any file system. A teammate with their own license can open the model, run it against their JDE connection, and get the same results.

What's covered by the annual maintenance?

Three things: new releases of the app, schema-metadata updates as Oracle ships new ESUs (so your table descriptions stay current), and support — email and ticket-based, business-hours, ~24h response time. Maintenance is optional after year one but recommended.

Can we try it before buying?

Yes — we provide a 30-day trial license with the full feature set, no payment details required. After the trial expires, the app continues to work in read-only mode on saved models — you don't lose your work even if you decide not to buy. Get in touch for a trial.

Stop guessing what's in your JDE.

The fastest way to see if OperoStudio is right for your team is a guided demo on a representative use case — we'll model a real extract on a sample JDE schema and show what you'd save in time and frustration.