JD Edwards
The JD Edwards screen (Settings - JD Edwards) holds, for each connected JD Edwards EnterpriseOne application, where the collection reads the JDE tables and what it reads. One line per application. Open it from Settings → Global → JD Edwards.
The same fields are on the JD Edwards tab of Applications; this screen shows every application side by side.
At a glance
The Application ID field above the grid narrows it to one application; blank, it shows them all.
Edit dialog
Click Add row to give an application its JD Edwards settings, or click a row to open them. The dialog, Edit · JD Edwards Settings, is one form in four columns, with Delete, Duplicate, Cancel and Save.
| Field | What to enter |
|---|---|
| Application ID | The application. Read-only once saved. |
| JDE DTA | Schema of the business data tables (F0101, F4211…). |
| JDE CTL | Schema of the control tables (F0005…). |
| JDE SY | Schema of the system tables (security F00950, users F0092…). |
| JDE SVM | Schema of the server map tables. |
| JDE CO | Schema of the central objects — the specifications read by the cross reference. |
| JDE OL | Schema of the Object Librarian (F9860, F9861) — the objects catalogue and the menus. |
| F00950 | Schema of the security workbench table, when it is not the system one. |
| JDE_UDO_SEC | Schema of the user defined objects' security table (F00950W): its rows are added to the security collected. Blank: skipped. |
| JDE_UDO_OL | Schema of the user defined objects' librarian (F9860W, F9861W), read for the composite pages, the E1 pages and the inventory of user defined objects. Blank: those steps do nothing and say so. |
| …_DBLINK | Next to each schema: the database link that reaches it. Blank when the JDE tables are in the database Nomasx-1 connects to. |
| Thick LOB read (Y/N) | Tick when the JDE tables are reached through a database link: the menus and the specifications (LOB columns) are then read by a short-lived thick-mode process. |
| Standard Menu (Y/N) | Read the standard JDE menus for the security build. |
| E1 Pages (Y/N) | Read the E1 pages: the applications and reports their code calls or names become access paths. |
| E1 Composite (Y/N) | Read the composite pages: what their tiles open, the forms in their panes, the task of a task tile — for a landing page, every task under its menu. |
| Purge OUT (Y/N) | Purge old Object Usage Tracking rows in JDE once Nomasx-1 has collected them. |
| OUT Retention Days | Days of usage history the purge keeps in JDE. |
The menus read decide the access paths behind Menus, Rights, the segregation of duties and the licence figures: switching E1 Pages or E1 Composite on or off changes them at the next security collection. The inventory of user defined objects (queries, grid formats, watchlists, form extensions, composite pages, orchestrations…) and the cross reference built from the central objects are read by Nomajde's screens, from what Nomasx-1 collects with these settings.
Tips & best practices
- Ask the JDE administrator for the schema names and the database links — they come from the JDE installation (path code, data sources).
- Fill JDE_UDO_OL on any Tools 9.2 installation: much of what a customer changes is a user defined object, and composite pages give access paths the standard menus do not.
- Tick Thick LOB read only with a database link; a local install reads the LOB columns directly.
- Keep the OUT retention longer than the collection interval, so no usage row is purged before Nomasx-1 has read it.