Free tool

ERP Table and Field Explorer

Find the table behind a form or report, see its key, the fields that matter and how it joins to the rest of the schema, then get a JOIN query skeleton for SQL Server, Oracle or HANA. Built for report writers, ERP developers, consultants and IT managers.

Why a table explorer

ERP schemas are large and their names are terse: coitem_mst in SyteLine, tdsls401 in LN, OOLINE in M3, F4211 in JD Edwards, VBAP in SAP. The data dictionary that explains them often sits behind a login or a client install. This explorer keeps the most used tables of each ERP in one searchable place, with the conventions that trip people up: site and company columns, table name suffixes and right-justified keys.

Search by what you know. A field such as qty_ordered, a business word such as invoice, or a form name finds the table, and the detail panel shows the key and the joins so the query you write uses the index instead of scanning the table.

Questions

What does the ERP Table and Field Explorer do?

It is a searchable catalog of the tables report writers, developers and consultants use most in each ERP: items, BOM and routing, sales, purchasing, inventory, production, finance, customers and suppliers. For each table you get a description, the key, the important fields with their meaning and the documented join columns. Pick two to four tables and it writes a JOIN query skeleton in the right SQL dialect.

Where do the tables and fields come from?

From vendor documentation and well established public references, listed as sources on every ERP page. Anything we could not confirm is left out or marked verify in the table notes. Column sets change between releases, so treat the catalog as a map and confirm details in your own data dictionary.

Which SQL dialect does the query builder use?

The dialect of the database the ERP normally runs on: SQL Server for SyteLine, Epicor Kinetic and SYSPRO, Oracle for E-Business Suite, SuiteQL for NetSuite, and SQL Server or Oracle for JD Edwards and LN depending on your platform. On SAP pages you can switch the output to ABAP Open SQL or an ABAP CDS view skeleton, matched to the release: Open SQL compatible with 7.40 SP08 and 7.50 plus a DDIC-based CDS view for ECC, the FIELDS syntax and a CDS view entity for S/4HANA. For native SQL you can set the schema or owner, and on LN the company number suffix.

Is it safe to run the generated SQL?

The skeletons are read-only SELECT statements with a row limit and the site, client or company filter the ERP needs. Run them against a reporting copy or with read-only credentials, and never write to ERP tables with SQL: use the APIs, IDOs, BAPIs or interfaces the vendor supports.

Do I need an account?

No. Search, the query builder and every export work without a login. A free Netray account is optional and only saves your favorites and query so you can reopen them on another device.