JD Edwards Table Security over ODBC
Give external tools ODBC access to JDE while preserving JDE credentials and table-level security.
ODBC access without a database back door
Direct database reporting often creates an uncomfortable exception: shared DB credentials that do not follow the JDE user lifecycle and do not reflect JDE Table Security.
The ESI JDE ODBC Driver is designed so the user connects with JDE credentials and access is constrained by the same table security expectations administrators already manage.
- No shared SQL or Oracle login handed to report users.
- Table Security remains the access boundary.
- Backend choice can align with network policy.
A cleaner CNC conversation
Security teams do not have to approve a parallel access model. They can evaluate an ODBC interface that is explicitly JDE-aware and designed around the existing JDE security model.
See where this fits in the product.
This supporting page explains one search intent in detail. The main ESI JDE ODBC Driver page gives the full product overview, related use cases, licensing and enquiry path.
Back to ESI JDE ODBC Driver