Nomajde
The problem Nomajde solves
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 between 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.
Form ping-pong
Five forms to onboard one user
Create the user in P0092, set the password in the security workbench, attach the roles in P95921, pick the environments in P0093, copy the security from a reference user — each form on its own, with its own data check.
Bulk edits hurt
No way to edit 200 UDC values at once
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 together a SQL script and hopes nothing breaks.
Reporting is its own world
BIP runs leave no trail
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-at-a-time 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
A web application that sits next to JD Edwards and reads its data live — through SQL on the JDE security and master tables, and through the JDE AIS REST API for the operations that need a JDE workflow behind them (password reset, user provisioning, processing-option overrides). Every screen writes back to JDE — no staging copy, no replay.
Behind the screens
SQL — security & master tables
F0092 · F00926 · F95921 · F0093 · F00950 · F0004 · F0005
AIS REST API
token · provisioning · password reset
BIP scheduler
schedule · archive · resend
JDE Object Librarian
menus · objects · versions
→
→
Nomajde
The JD Edwards companion
Master Data
UDC · Address Book
Security
users · roles · workbench
Transactions
AP · AR · GL
Reporting
BIP · archive
Day-to-day work
Grid edits
inline edit · bulk update
Excel upload
SI bundles · roll-outs
Drill-down grids
filter by every column
Audit trail
who changed what, when
Direct to JDE
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.
Bulk-friendly
Excel upload on every writable screen — UDCs, security workbench, role relationships, environments. Onboard a roll-out in minutes.
Audit-traced
Every change carries the Nomajde user, the timestamp and the screen it came from — JDE sees it, and so does the Audit Trail.
On-premise
Single-tenant deployment, next to the JDE servers. No SaaS upload. The credentials and the master data never leave the perimeter.
The four pillars
01 · Master Data
UDC, Address Book, GL — bulk-editable
- UDC types and UDC codes — one grid per topic, with Excel upload for roll-out loads.
- Address Book, customers, suppliers, items, GL accounts — same shape, same grid editing.
- The required-field checks JDE runs at row save are enforced here too — no half-written record reaches JDE.
02 · Security Maintenance
User Management · Role Management · Workbench
- Add and edit JDE users — SQL writes the user master and the display preferences, AIS REST provisions the security record and the password.
- Reset password — one click; the call goes to the JDE AIS endpoint and the new password is active immediately.
- Import Security and Merge Roles — copy or merge the full security setup (application, action, row, column, processing-option, tab, exit, image, UDO, menu-filtering) from a source user / role to a target, in a guided workflow.
- Security Workbench — every JDE security type on one grid, with type-aware dialog and Excel upload for SI-delivered bundles.
03 · Transactions & Reporting
AP, AR, GL — and the BIP archive
- AP, AR, GL grids — filter on any column (company, supplier, document, amount, date), drill into the details.
- Schedule BIP reports from a single form — pick the program, the version, the data selection, the run time.
- The generated output (PDF or XML) is archived next to the run. Download, e-mail, resend in one click.
- Every BIP run is logged — who scheduled it, when it ran, what was produced.
04 · Monitoring
JDE in production, live
- Live counters of AP / AR / GL transactions, drill-through to the underlying screen.
- The JDE job-control queue as a grid — status, owner, runtime, output.
- Performance indicators: database latency, AIS response time, transaction throughput.
A sample of what you see
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 grid, with the editable user record, the attached roles and environments, and the workflow that combines a SQL write with an AIS API call.
The application map
The sidebar splits the day-to-day work into five sections.
| Section | What it covers |
|---|---|
| Dashboard | Daily activity summary — open transactions, running jobs, recent users, latest alerts. |
| Master Data | UDC types and UDC codes, Address Book, customers, suppliers, items, GL accounts. Every grid supports filter, sort, inline edit and Excel upload. |
| Security Maintenance | User Management, Role Management, Role Relationships, Environments, Security Workbench. The full JDE security catalogue, condensed into five screens with grid editing and a guided Import / Merge workflow. |
| Transactions | AP, AR, GL grids with filters and drill-through to the underlying detail. |
| Reporting | Schedule BIP jobs from one form, archive of past runs, distribution by e-mail. |
| Monitoring | Live transaction counters, the JDE job-control queue as a grid, performance indicators (DB latency, AIS response time, throughput). |
| Settings | Environment definitions, AIS endpoint, e-mail server, archive retention. |
Who uses it
| Role | What they typically open Nomajde for |
|---|---|
| JDE security administrator | The five Security Maintenance screens — add a user, attach a role, run Import Security on a clone, walk through the security workbench grid. |
| AP / AR operator | The transaction grid — open invoices across companies and environments on one page, with bulk filters and drill-through. |
| Master-data steward | Address Book, customer and supplier maintenance with required-field checks; UDC types and codes for the catalogue work. |
| Reporting analyst | One form to schedule BIP, the archive of past runs, e-mail distribution. |
| Ops engineer | The Monitoring section — live counters, job queue, performance indicators. |
Roles inside Nomajde
The application ships four roles.
| Role | What it grants |
|---|---|
| Viewer | Read every screen, run reports, no edits. |
| Operator | Everything a Viewer does, plus AP / AR / master-data edits and scheduling reports. |
| Security | Everything an Operator does, plus the Security Maintenance section (User, Role, Role Relationships, Environments, Security Workbench). |
| Administrator | Everything above, plus environment configuration, AIS endpoint, archive retention. |
A typical deployment keeps Operator separate from Security — the person processing transactions is not the same one managing access rights.