Skip to main content

Nomajde — Overview

Nomajde is a JD Edwards companion application. It sits next to JDE EnterpriseOne and consolidates what JDE typically spreads across many separate screens into a smaller set of simplified ones, with grid editing for bulk updates. The day-to-day work — what would take five JDE screens and dozens of clicks — collapses into one Nomajde page:

  • consult and edit master data (address book, customers, suppliers, items, GL accounts),
  • maintain JDE security — users, roles, role relationships, environments, security workbench,
  • inspect transactions across companies and environments without navigating row by row,
  • schedule BIP reports, archive their outputs and resend them,
  • watch JDE in production — transactions, jobs, performance — live.

Every screen reads JDE data in real time. There is no nightly extract, no staged copy — what the screen shows is what JDE is showing right now.

At a glance​

🟧 NOMAJDE · Sidebar📊 Dashboard📁 Master DataAddress bookCustomers · SuppliersItems · GL accounts📁 Security MaintenanceUser ManagementRole ManagementRole RelationshipsEnvironmentsSecurity Workbench📁 TransactionsAP · AR · GL📁 Reporting📁 Monitoring👥 USER MANAGEMENTSearch a user, see every role,every environment, every securityentry that applies to them.Add / update / disable a userwithout leaving the page.Edits go straight to JDE — thechange is live on the fat-clienton the next refresh.Audit trail: who changed what,when, from which page.Same shape on Role Management,Environments and Security Workbench.📊 REPORTINGSchedule a JDE batch job froma form. Output is archived nextto the run — download, resend,e-mail in one click. Audit logof every run.📈 MONITORINGLive counters of AP / AR / GLtransactions. The job-controlqueue as a grid. Performanceindicators (DB latency, AISresponse time, transactionthroughput).

What it covers​

Master data​

The day-to-day master-data work, in one shape per business object.

  • Address book — search any address, see who / what / where on a single row. Edit a name, a phone, a postal address without opening three screens.
  • Customers and suppliers — the full master, per company. Edit the credit terms, the bank account, the payment instructions.
  • Items — item master, with item branch / plant on the same page.
  • GL accounts — chart of accounts per business unit and per company.

Every grid lets you filter by any column, sort, export to Excel, and click a row to open the edit form.

Security Maintenance​

The same JDE security work, condensed into five screens that each consolidate what JDE spreads across many forms. Every grid supports inline editing — change a value on a row, the update is written back without leaving the page.

ScreenWhat you do here
User ManagementSearch a user; see every role, environment and security entry that applies on a single page. Add, update or disable a user; assign or revoke a role inline in the grid. The change goes to JDE immediately.
Role ManagementThe catalogue of roles, with the applications attached to each. Add a role, attach an application, set processing-option security — without navigating between separate JDE forms.
Role RelationshipsRole inheritance and effective-date windows in one grid. Promote a junior role to inherit a senior one, with a start and an end date, in a single edit.
EnvironmentsThe list of environments (PD, PY, DV, CRP, …) and the role assignments per environment, side by side.
Security WorkbenchThe whole security catalogue — application security, action security, row security, column security, processing-option security — on one searchable grid with inline edits, instead of a separate JDE screen per security type.

Edits are written straight to JDE — no extract, no replay. The audit trail records every change with the user, the timestamp and the page it came from.

Transactions​

Grids over AP, AR and GL. Filter on any column — company, business unit, supplier, document number, amount range, date range — and click a row to drill into the details. Right for spotting an open invoice, an unposted batch, or a journal that did not balance.

Reporting​

Schedule and archive JDE BIP reports.

  • Pick the program and the version, fill the data selection, choose when it runs. The job goes to JDE through a single form — no chain of separate scheduling screens.
  • The generated output (PDF or XML) is archived next to the run. Download it later, e-mail it to a recipient list, resend it through the same connector.
  • Every run is logged — who scheduled it, when it ran, what was produced.

Monitoring​

A live view of JDE in production.

  • AP / AR / GL transaction counters with 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.

Right for an ops engineer keeping a watch on the day's load.

The application map​

SectionWhat you find here
DashboardDaily activity summary: open transactions, jobs running, recent users, latest alerts.
Master DataAddress book, customers, suppliers, items, GL accounts.
Security MaintenanceUser Management, Role Management, Role Relationships, Environments, Security Workbench.
TransactionsAP, AR, GL grids with filters and edit forms.
ReportingSchedule a BIP job, archive of past runs, distribution.
MonitoringLive transaction counters, job-control queue, performance indicators.
SettingsEnvironment definitions, e-mail server, archive retention.

Who uses it​

RoleWhat they typically open Nomajde for
AP / AR operatorThe transaction grid — every open invoice across companies and environments on one page, with bulk filters and inline edits.
Master-data stewardAddress book, customer and supplier maintenance, with required-field validation in the form and grid edits for mass updates.
JDE security administratorThe five Security Maintenance pages — five screens that consolidate what JDE spreads across many separate forms, all with inline editing.
Reporting analystThe Reporting section — one form to schedule, archive and distribute a BIP job, where JDE walks through several separate screens.
Ops engineerThe Monitoring section — live transaction counters, job queue, performance, on one dashboard.

Roles inside Nomajde​

The application itself ships four roles.

RoleWhat it grants
ViewerRead every screen, run reports, no edits.
OperatorEverything a Viewer does, plus AP / AR / master-data edits and scheduling reports.
SecurityThe Security Maintenance section — User, Role, Role Relationships, Environments, Security Workbench.
AdministratorEverything above, plus environment configuration and archive retention.

A typical deployment keeps Operator separate from Security — the person processing transactions is not the same one managing access rights.