Nomasx-1
The Nomasx-1 JD Edwards connector is the original engine of the product and is included out of the box. It logs into the JDE security tables (users, roles, environments, security workbench, menus), pulls the Object Usage Tracking history from JDE Object Librarian and reads the Oracle DBA views on the underlying database — all from a single configured datasource. The JDE-on-Oracle customer goes from install to a first audit-ready picture in hours, not weeks.
The problem Nomasx-1 solves
The teams who need to answer compliance questions never look at the same screen. Security data sits in the ERP security workbench, licence data in spreadsheets the procurement team maintains by hand, SoD findings in an Excel matrix that has not been refreshed in months, and database options in DBA views nobody outside IT can read.
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
A single platform that pulls every relevant source — ERP, database, directory — and turns it into a small set of grids, dashboards and reports the compliance team uses every day.
The four pillars
- Master list of users with creation, last login, last activity and ERP attributes.
- Role assignments with effective and expiration dates — expired-but-still-active surfaces in red.
- LDAP / AD cross-check — every ERP account is matched against the directory.
- Duplicate users, dormant accounts, accounts without any role — flagged automatically.
- Records every object call on the connected applications and aggregates by licence component.
- Distinguishes the dormant access (granted but never used) from the active access.
- Per-component user counts and last-use dates — the evidence behind the licence figures.
- Captured passively — no need to turn the ERP's own audit on, no operational impact.
- Customer Support Identifiers and the licences attached to each — the contractual side.
- Per-database list of required Oracle options based on what the collection scripts found on the instance.
- JDE per-app cohorts — enabled users, transactional users, dormant accounts, orphan transactions.
- Usage Report and Financial Report — required vs subscribed and the monetary gap.
- Editable SoD matrix — predefined ERP risks plus your own additions.
- Process / activity / risk model — conflicts described in business language, not raw role pairs.
- Conflicts ranked per user, per role, per object — the order in which to remediate.
- Proven conflicts split out from theoretical ones — only the user actions that actually happened.
A sample of what you see
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 second example: a Segregation-of-Duties summary by user, with the conflicts ranked by risk and the proven ones marked.
The application map
The sidebar splits the day-to-day work into five sections plus the configuration area.
| Section | What it covers |
|---|---|
| Overview | The dashboard — open conflicts, expiring assignments, licence gap, last refresh status. |
| Security | Users, roles, role assignments, role matrix (combinations), duplicate users, users without roles, LDAP / AD reconciliation. |
| Applications | Per connected application: menus, rights (per user, per role, combined), Object Usage Tracking (components, objects, details), Conflicts (summary, by user, by role, by object), Activity Log. |
| Database | Oracle properties (edition, packs, options, partitions), Audit Trail (Oracle archive log changes), Audit Lookup (row-level before / after). |
| Licences | CSI contracts, JD Edwards licence picture, Oracle licence requirements, Subscribed Licenses, Usage Report, Financial Report. |
| Settings | Source-system definitions (applications, JDE schemas, Oracle catalogues), LDAP department mapping, SoD configuration (processes, activities, risks, objects, matrix), pricing catalogue, security and AD flags. |
Who uses it
| Role | What they typically open Nomasx-1 for |
|---|---|
| Internal auditor | The quarterly SoD review — open conflicts, exception sign-offs, trend over time. |
| Security officer | Day-to-day "who has access to X" — the user-and-role catalogue, with dormant accounts and expired assignments flagged. |
| JDE security administrator | Cross-environment user-and-role catalogue, easier than the JDE security workbench, with bulk edits in Nomajde when changes are needed. |
| Licence manager | Required-vs-subscribed reconciliation, Object Usage Tracking evidence, financial-gap report before each renewal. |
| CISO / Risk | The compliance dashboard — SoD posture, account hygiene KPIs, licence exposure. |
| DBA | The Oracle picture — options, features, partitions — without writing a single query. |
Roles inside Nomasx-1
The application ships four roles. They control what each user sees and what they can change.
| Role | What it grants |
|---|---|
| Viewer | Read every screen, run reports, no edits. |
| Editor | Everything a Viewer does, plus update the SoD matrices, schedule scans, manage notification rules. |
| Auditor | Everything a Viewer does, plus sign off exceptions. The only role that can close a flagged conflict. |
| Administrator | Everything above, plus manage the source-system configuration (ERP datasources, Oracle accounts, LDAP / AD mapping). |
A typical deployment keeps Auditor separate from Administrator — the same principle Nomasx-1 itself enforces: the person who configures the analysis should not be the one who signs off its findings.