Nomana-IT

Noma sx-1
Compliance & licence platform

One platform for everything an auditor or licence manager 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.

Request a Demo Read the Docs
JD Edwards EnterpriseOne — flagshipOracle Database — audit scriptsSAP · NetSuite · custom ERPMSSQL · HANA · PostgreSQLLDAP · Active DirectoryOn-premise

Flagship combination

JD Edwards EnterpriseOne · Oracle Database

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.

Security tables

Users, roles, role relationships, environments, security workbench — read live.

Object Usage Tracking

Per-component user counts and last-use dates straight from the OUT history.

Oracle audit scripts

Detect the Oracle options, packs and features actually used on each instance.

No source-side change

No BIP job to schedule, no JDE audit to turn on — just a read-only datasource.

Why it exists

The problem Nomasx-1 solves

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.

Without a unified view

Dormant accounts keep their rights

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.

Without usage evidence

Licence cost grows on autopilot

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.

Without continuous SoD

SoX findings show up too late

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 in, decisions out

Sources connected

ERP security workbench
JDE · SAP · NetSuite · custom
Database catalogue
Oracle · MSSQL · HANA · PG
Directory
LDAP · Active Directory
Object Usage Tracking
per-component activity
Nomasx-1
The compliance & licence platform
Inventory
users · roles · rights
Track usage
OUT · activity log
Analyse SoD
matrix · conflicts
Optimise cost
licences · packs

Outputs

Compliance dashboards
SoD posture · expirations
Licence reports
usage · subscribed · gap
Excel exports
per department · per app
Sign-off trail
exceptions · approvals

Source-agnostic

JDE today, SAP tomorrow, a divested entity on NetSuite — a new connector plugs in without touching the rest of the product.

Continuous

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.

Audit-ready

Every grid exports to Excel, every exception leaves a sign-off trail, every change to the SoD matrix is logged.

On-premise

Single-tenant deployment. Security data, licence figures and SoD findings stay inside your perimeter — no SaaS upload.

What it covers

The four pillars

01 · Security & identity

Who has access, and is it still needed?

  • 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.
02 · Object Usage Tracking

What is actually used — by whom, how often?

  • Records every object call on the connected applications and aggregates by licence component.
  • Distinguishes dormant access (granted but never used) from 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.
03 · Licence compliance

What is paid, what is needed, what is the gap?

  • 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.
  • JDE per-app cohorts — enabled users, transactional users, dormant accounts, orphan transactions.
  • Usage Report and Financial Report — required vs subscribed and the monetary gap.
04 · Segregation of Duties

Where are the conflicts — and who cleared them?

  • Editable SoD matrix — predefined ERP risks plus your own additions.
  • Process / activity / risk model — conflicts 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 actions that actually happened.

Screens

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.

Nomasx-1 Oracle licences grid with required-component indicators

A Segregation-of-Duties summary by user, with conflicts ranked by risk and the proven ones marked.

Nomasx-1 Segregation of Duties conflicts summary by user

Inside the product

The application map

Sections

Overview
The dashboard — open conflicts, expiring assignments, licence gap, last refresh status.
Security
Users, roles, role assignments, role matrix, duplicate users, users without roles, LDAP / AD reconciliation.
Applications
Per app: menus, rights, Object Usage Tracking, Conflicts (summary, by user, by role, by object), Activity Log.
Database
Oracle properties (edition, packs, options, partitions), Audit Trail, Audit Lookup (row-level before / after).
Licences
CSI contracts, JD Edwards licence picture, Oracle requirements, Subscribed Licenses, Usage & Financial Reports.
Settings
Source-system definitions, LDAP department mapping, SoD configuration, pricing catalogue, security and AD flags.

Who uses it

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, dormant accounts and expired assignments flagged.
JDE security admin
Cross-environment user-and-role catalogue, easier than the JDE workbench, with bulk edits in Nomajde when needed.
Licence manager
Required-vs-subscribed reconciliation, OUT 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.

Four roles ship with the product — Viewer, Editor, Auditor and Administrator. A typical deployment keeps Auditor separate from Administrator: the person who configures the analysis should not be the one who signs off its findings.

Secure & Optimise Your JD Edwards Environment

Get in touch to see how Nomasx-1 brings security, licence compliance and Segregation of Duties into one continuous picture.

Request a Demo Read the Docs