JD Edwards work, on one searchable grid. Nomajde collapses what JDE spreads across many forms — user master, role description, security workbench, environments, UDC tables, transactions, BIP scheduling — into a smaller set of grids with inline editing. Every write goes straight to JDE through SQL inserts on the security tables and AIS REST calls. No nightly extract, no staged copy.
Why it exists
JD Edwards is a depth product. Most day-to-day tasks — add a user, attach a role, update a UDC value, schedule a BIP report — require navigating five or six forms, sometimes across the fat client and the web client. Operators get the job done; they spend twice the time they should.
Create the user in P0092, set the password in the security workbench, attach the roles in P95921, pick the environments in P0093, copy security from a reference user — each form on its own, with its own data check.
JDE forms are one-row-at-a-time editors. When the SI delivers a new module with 200 UDC values, the operator types them in by hand — or hacks a SQL script and hopes nothing breaks.
Scheduling a BIP report goes through the JDE scheduler, the output lives wherever the printer queue dropped it, and the audit of “who ran what, when” is left to the operator’s memory.
Nomajde replaces the form ping-pong with one screen per topic, the one-row editor with grid editing and Excel upload, and the unwritten audit trail with a logged history of every run and every change.
What Nomajde is
Behind the screens
Day-to-day work
Every write hits the JDE tables and AIS API the same way the fat client would — the change is visible on the next JDE refresh.
Excel upload on every writable screen — UDCs, security workbench, role relationships, environments. Onboard a roll-out in minutes.
Every change carries the Nomajde user, the timestamp and the screen it came from — JDE sees it, and so does the Audit Trail.
Single-tenant deployment, next to the JDE servers. No SaaS upload. Credentials and master data never leave the perimeter.
What it covers
Screens
The Security Workbench grid — every JDE security entry on one row, with the action flags side by side and the dialog adapting to the security type.
The User Management form — the editable user record, with the dual SQL + AIS workflow that runs on save.
Inside the product
Four roles ship with the product — Viewer, Operator, Security and Administrator. A typical deployment keeps Operator separate from Security: the person processing transactions is not the one managing access rights.
Install Nomajde, point it at your JDE database, and give your operators one searchable grid for master data, security, transactions and reporting.
