Skip to main content

Users Audit

The Users Audit screen is the drill-down view of a single user account. One line per (Application, User, Module) triplet — meaning a user used on five different modules of the source system produces five rows on this screen, one per module.

It is what you open after clicking on a row in Users, Users without roles or Duplicate users: rather than a one-line summary, it shows the full identity card plus the per-module usage trail.

At a glance​

Nomasx-1 · Security · Users Audit · APMGRIDENTITYApp 12 · APMGR · Accounts Payable ManagerActiveCountry FR · Company 00010 · BU 30 · Cat 8 SALESCreated 2019-03-14LAST USAGE BY MODULEAccounts Payable2026-05-13General Ledger2026-04-02Address Book2025-11-18Procurement2023-09-04

Goal of the view​

For a single user on a single application:

  • Who is this person? Identity (name), the organisation context (country, company, business unit, category code) and the account status — everything an auditor needs to recognise the user without leaving the screen.
  • What does this user use? A line per module of the source system, with the date of the last operation in that module. This is the trail that answers "is the wallet of roles this user holds actually justified?".
  • What can be revoked? A role that grants access to a module not used in the last twelve months is a candidate for revocation.

The screen is the second click in every per-user investigation — one row, all context.

Columns​

ColumnSourceWhat it tells you
Application IDUSR_APPS_ID — application identifier from the source system.The application the user belongs to.
User IDUSR_ID — user identifier (technical login).Carried from the calling screen.
User NameUSR_NAME — display name.Human-readable name.
StatusUSR_STATUS — normalised: 01 for Active, N otherwise.Account state in the source system.
CountryUSRD_ULCTR — text.Country attached to the user in the source system.
CompanyUSRD_MCCO — text.Default company assigned to the user.
Business UnitUSRD_MCMCU — text.Default business unit assigned to the user.
BU Code Cat 8USRD_MCRP08 — text.Category code 8 of the business unit — typical breakdown axis for analytical reporting.
Creation DateUSR_DT_CREATION — date.When the account was created.
ComponentCPT_COMPONENT — text.Functional module of the source system (Accounts Payable, General Ledger, etc.). One row per module the user has used at least once.
Last UsageLAST_USAGE — date.Last activity recorded by the source system on the module.
JDE-specific

On JD Edwards EnterpriseOne, Component and Last Usage are computed from Object Usage Tracking (LICENSE_JDE_OUT) joined to the JDE objects table and to the System Code → License Component mapping (SETTINGS_JDE_SY → SETTINGS_LIC_COMPONENTS). The organisation columns (Country, Company, Business Unit, BU Category 8) are JDE defaults stored in the user data. Other source systems can populate the same columns with their own equivalents — for example HR cost-center mapping for SAP, location and department on NetSuite.

Tips & best practices​

  • Read the last-usage column from the bottom up. Modules with no activity in the last twelve months are the strongest signal for role revocation — the user is paying the audit cost of a role they no longer exercise.
  • Use Country and Business Unit to cross-check with HR. A user whose source-system country no longer matches the HR record is either a relocation never reflected in the system or a stale account.
  • For technical / batch users, expect a single module with a recent date and nothing else. Tag them via the Settings → Users properties screen so they stop being flagged by the dormant-account review.
  • Click Print to export the audit card as a PDF — handy for evidence packs delivered to external auditors.