Skip to main content

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​

Settings - JD EdwardsAPPLICATION ID(null if blank)2 rows · 12 msTableChart+ Add row✎ Bulk edit⌕ Search…▷ RunMax rows default▦ Views⏷ Filters⌘ Group▥ Columns⇩ Export ▾APPLICATION ID (ID)APPLICATION IDJDE SYJDE DTAJDE CTLJDE SVMJDE COJDE OLF009501JDE-PRODSY920PRODDTAPRODCTLSVM920PD920OL920SY9202JDE-TESTSY920TESTDTATESTCTLSVM920PY920OL920SY920Rows per page50 ⌄Showing 1–2 of 2« ‹ 1 › »Schemaswhere the JDE tables are readF00950schema of the security workbenchApplication IDblank = every applicationAdd rowsettings for one applicationClick a rowopens the edit dialogColumnsDB links, flags, retention

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.

Edit · JD Edwards Settings⤢APPLICATION ID1 JDE-PROD⌄JDE DTAPRODDTAJDE_DTA_DBLINKJDE CTLPRODCTLJDE_CTL_DBLINKJDE SYSY920JDE_SY_DBLINKJDE SVMSVM920JDE_SVM_DBLINKJDE COPD920JDE_CO_DBLINKJDE OLOL920JDE_OL_DBLINKF00950SY920JDE_F00950_DBLINKJDE_UDO_SECSY920JDE_UDO_SEC_DBLINKJDE_UDO_OLOL920JDE_UDO_OL_DBLINKTHICK LOB READ (Y/N)disabledSTANDARD MENU (Y/N)enabledE1 PAGES (Y/N)enabledE1 COMPOSITE (Y/N)enabledPURGE OUT (Y/N)enabledOUT RETENTION DAYS90▣ Save✕ Cancel⧉ DuplicateDeleteApplication IDread-only once savedSchemasdata, control, system, server map…UDO librariesneeded for the user defined objectsMenus to readstandard, E1 pages, composite…_DBLINKdatabase link per schemaThick LOB readJDE reached through a DB linkPurge OUT · retentiondays of usage keptSavetaken at the next collection
FieldWhat to enter
Application IDThe application. Read-only once saved.
JDE DTASchema of the business data tables (F0101, F4211…).
JDE CTLSchema of the control tables (F0005…).
JDE SYSchema of the system tables (security F00950, users F0092…).
JDE SVMSchema of the server map tables.
JDE COSchema of the central objects — the specifications read by the cross reference.
JDE OLSchema of the Object Librarian (F9860, F9861) — the objects catalogue and the menus.
F00950Schema of the security workbench table, when it is not the system one.
JDE_UDO_SECSchema of the user defined objects' security table (F00950W): its rows are added to the security collected. Blank: skipped.
JDE_UDO_OLSchema 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.
…_DBLINKNext 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 DaysDays of usage history the purge keeps in JDE.
JDE-specific

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.