One platform for everything a licence manager or an auditor asks for. A dedicated connector reads the JD Edwards security workbench, the user / role / environment tables, the Object Usage Tracking history and the underlying Oracle instance in one pass — no manual export, no BIP job to run beforehand.
Flagship combination
The Nomasx-1 JD Edwards connector is the original engine of the product and ships out of the box. It logs into the JDE security tables, pulls Object Usage Tracking history from Object Librarian and reads the Oracle DBA views — all from a single configured datasource. The JDE-on-Oracle customer goes from install to a first audit-ready picture in hours, not weeks.
Users, roles, role relationships, environments, security workbench — read live.
Per-component user counts and last-use dates straight from the OUT history.
Detect the Oracle options, packs and features actually used on each instance.
No BIP job to schedule, no JDE audit to turn on — just a read-only datasource.
Why it exists
The teams who answer compliance questions never look at the same screen. Security data sits in the ERP workbench, licence data in hand-maintained spreadsheets, SoD findings in a stale Excel matrix, database options in DBA views nobody outside IT can read.
A user who left a year ago still holds the AP-approval role. A SoD conflict opened in March is still open in October. Nobody catches it until the next audit.
The renewal arrives. No one can tell which JDE modules are actually used or which Oracle options run on the database. The safest answer is to renew everything — at full price.
The SoD matrix is an Excel file on someone’s laptop. The check is done once a year, two weeks before the auditor arrives. Every finding becomes an urgent remediation.
Nomasx-1 replaces the spreadsheets, the manual exports and the once-a-year scramble with a continuous picture maintained by the product itself.
What Nomasx-1 is
Sources connected
Outputs
JDE today, SAP tomorrow, a divested entity on NetSuite — a new connector plugs in without touching the rest of the product.
Scans run on a schedule. The dashboard the auditor opens at 9 am is the picture from the last scan, not last quarter’s spreadsheet.
Every grid exports to Excel, every exception leaves a sign-off trail, every change to the SoD matrix is logged.
One instance per customer — on your premises, in your cloud, or hosted by Nomana-IT on OCI or AWS. Security data, licence figures and SoD findings are never pooled in a shared SaaS.
What it covers
Screens
The licence compliance picture — one row per database × component, with a green / red indicator straight from the collection scripts. The dashboard a licence manager opens before every renewal.
A Segregation-of-Duties summary by user, with conflicts ranked by risk and the proven ones marked.
Inside the product
The application ships with four roles. They control what each user can see and change.
Read every screen, run reports, no edits.
Everything a Viewer does, plus update the SoD matrices, schedule scans, manage notification rules.
Everything a Viewer does, plus sign off exceptions. The only role that can close a flagged conflict.
Everything above, plus manage the source-system configuration (ERP datasources, Oracle accounts, LDAP / AD mapping).
A typical deployment keeps Auditor separate from Administrator: the person who configures the analysis should not be the one who signs off its findings.
FAQ
Nomasx-1 is a compliance and licence optimisation platform published by Nomana-IT and built with Liberty Next. It unifies Oracle and JD Edwards licence compliance, Object Usage Tracking, enterprise security and Segregation of Duties in one audit-ready, single-tenant application, built first for JD Edwards EnterpriseOne on Oracle.
Object Usage Tracking records every object call and aggregates it by licence component, separating dormant access from active use. The Usage and Financial Reports then compare required licences with subscribed licences and show the monetary gap before each renewal.
It provides an editable SoD matrix with predefined ERP risks plus your own, expressed as processes, activities and risks rather than raw role pairs. Conflicts are ranked per user, role and object, and proven conflicts — actions that actually happened — are separated from theoretical ones.
No. Object usage is captured passively, without enabling the ERP’s own audit and without operational impact.
JD Edwards EnterpriseOne is the flagship source, with audit scripts for Oracle Database. Connectors also cover SAP, NetSuite and custom ERPs on MSSQL, HANA or PostgreSQL, and accounts are cross-checked against LDAP or Active Directory.
Wherever you choose, always single-tenant: on your premises, in your own cloud, or hosted by Nomana-IT on Oracle Cloud Infrastructure (OCI) or AWS. Security data, licence figures and SoD findings stay in your dedicated instance — never in a shared SaaS.
Get in touch to see how Nomasx-1 brings licence compliance, security and Segregation of Duties into one continuous picture.