User Management
The User Management screen is the JD Edwards user master, condensed into one editable grid. One line per JDE account. From a single page the security administrator can add a new user, change their JDE attributes (language, country, date format, …), reset the password, attach roles and declare environments.
It is the entry point for every user-related security operation — what the JDE P0092 Work With User Profiles, P98OWSEC Work With User Security and parts of P95921 do, on one screen.
At a glance
Goal of the view
For each JDE user:
- The user master, editable on the grid. Add a new user, change the language, swap the date format — all inline. The screen owns the same data as the JDE Work With User Profiles form.
- Full provisioning, end to end. A new user requires a SQL write on the user master and an AIS REST call to create the JDE security record and set the password. Nomajde chains the two on a single save — no manual Work With User Security step.
- Password reset in one click. The Reset Password button on the dialog calls the JDE AIS endpoint directly; the new password is active on the user's next sign-on.
Columns
| Column | Source | What it tells you |
|---|---|---|
| User | ULUSER — JDE user ID. | The sign-on user. |
| Alpha name | ABALPH — Address Book alpha name. | Friendly name pulled from the Address Book record. |
| Language | ULLNGP — preferred language code. | Drives the language of the JDE forms. |
| Date format | ULFRMT — date format pattern. | Controls how dates are typed and rendered (DMY, MDY, …). |
| Country | ULCTR — country code. | Default country for new transactions entered by the user. |
The hidden JDE attributes carried on the row (output queue, job queue, message logging, decimal separator, currency, time zone, time format, OMW logging, right-to-left, intensive-user flag, action / inactive marker, audit columns) are kept on the row so the edit dialog opens with the full picture.
Edit dialog
Click Add in the toolbar to register a new JDE user, or double-click a row to edit an existing one. The dialog has three tabs. The Roles and Environments tabs are hidden on Add — they appear once the user record exists.
Tab 1 — Default
The user identification and the JDE display preferences. Every field corresponds to a column on the JDE user master.
| Field | What to enter |
|---|---|
| User | JDE sign-on user. Mandatory. Cannot be changed after creation. |
| Alpha name | Friendly name pulled from the Address Book — appears on every report and form. |
| Language | Preferred language code (F, E, S, …). Drives the language of the JDE forms. |
| Country | Country code — default country for new transactions. |
| Date format | Day / month / year ordering and separator (DMY /, MDY /, YMD -, …). |
| Decimal separator | Decimal character (, or .). |
| Currency | Default currency for new transactions. |
| Time zone | User's time zone — drives the timestamp display in JDE. |
| Time format | 12 h or 24 h. |
| Right-to-left, OMW logging, Intensive user | JDE display behaviour switches. Leave at the JDE default unless the deployment guidelines call for a specific value. |
The hidden JDE fields (output queue, job queue, message logging defaults) carry standard values populated by Nomajde — typically QPRINT, *NOLIST, severity 00.
Tab 2 — Roles
Nested table listing the roles attached to the user — the same data the Role Relationships screen edits, scoped to this user. Each row carries the role, the effective date and the expiration date.
Add a row to attach a role; double-click to extend the date window; delete to revoke. Hidden on Add.
Tab 3 — Environments
Nested table listing the environments the user can sign on to (PD910, PY910, DV910, CRP910, …), with the display sequence. The default environments are populated automatically when the user is created — adjust here if a specific entry has to be added or removed. Hidden on Add.
What runs on save
Adding a JDE user is not just a SQL insert. Nomajde chains the SQL writes and the AIS REST calls so the operator never has to switch screen.
| Step | Channel | What it does |
|---|---|---|
| 1 | SQL | Writes the user identification row in the JDE user master. |
| 2 | SQL | Writes the display preferences row (language, date format, currency, time zone, …). |
| 3 | AIS REST | Authenticates the Nomajde service account against AIS to obtain a token for the next two calls. |
| 4 | AIS REST | Checks whether the user already has a JDE security record, then creates one if missing — this is what makes the user known to the JDE sign-on layer. |
| 5 | AIS REST | Sets the initial password. The new account is ready on the next sign-on. |
If any step fails, the chain stops and the operator is notified — there is no half-provisioned user to clean up.
Reset Password
The Reset Password button on the dialog calls the JDE AIS change password endpoint directly. The administrator enters the new password once, clicks the button, and the change is active on the user's next sign-on. The same flow can be used to unlock an account whose password has expired.
Tips & best practices
- Onboard via Add, not via SQL. A direct SQL insert into the user master skips the AIS security record provisioning — the user appears in the table but cannot sign on. The five-step save chain is what makes the new user usable.
- Excel upload for SI-delivered user lists — the upload runs the same five-step chain for every row, so 50 new users are provisioned in a single import.
- Reset Password is the right tool when an operator reports a forgotten password. It is also what the help desk uses for the unlock request — a fresh password resets the failed-attempt counter on the JDE side.
- Keep the Roles and Environments tabs in sync. A user without an environment cannot sign on; a user without a role has no rights. The default environments populate automatically, but the role attachment is a manual step on the Roles tab.