Skip to main content

Duplicate users

The Duplicate users screen lists every account that shares its person identifier with at least one other account on the same application. One line per account in the duplicate group.

A "person identifier" is the field the source system uses to point at the underlying employee or contact — typically the Address Number on JDE (AN8), the Personnel Number on SAP HR (PERNR), or any similar foreign key. Two accounts linked to the same person mean the same individual carries two technical logins on the same application — almost always a residual of an account being created twice rather than re-activated.

At a glance​

Nomasx-1 · Security · Duplicate usersAPPUSERPERSONSTATUSCREATEDLAST LOGINLINKED ?12JDOE200714Active2019-03-142026-05-12→ J.DOE12J.DOE200714Inactive2014-02-102019-03-13→ JDOE12M.SMITH203128Active2022-09-112026-05-14—12M.SMITH2203128Active2024-11-04——2 duplicate groups · 4 accounts to review

Goal of the view​

For each pair (or group) of accounts pointing to the same person:

  • Why does the duplicate exist? Usually one of three cases — a renamed login (the source system couldn't rename so a second account was created), a contractor returning to the company, or a HR misconfiguration linking two logins to the same employee record.
  • Which account is the right one? The active one with the most recent login is normally the one to keep. The other should be deactivated and, if useful, linked to the active account via the Linked indicator.
  • Are the duplicates already declared? The Linked indicator marks accounts already declared as duplicates of another — those are documented exceptions and require no immediate action.

The screen drives both the cleanup of redundant accounts and the documentation of legitimate duplicate pairs.

Columns​

ColumnSourceWhat it tells you
Application IDUSR_APPS_ID — application identifier from the source system.Which application the duplicate group lives on.
User IDUSR_ID — user identifier.One account in the duplicate group.
Address NumberUSRD_AN8 — person identifier from the source system (JDE Address Number, SAP PERNR, equivalent on other ERPs).The shared person identifier — the grouping key for the duplicate row.
StatusUSR_STATUS — 01 means Active.Active or inactive in the source system.
Creation DateUSR_DT_CREATION — date.When the account was created — helps to identify the older account.
Login DateUSR_DT_LOGIN — date.Last authentication — confirms which account is the one actually used.
Is LinkedUSRP_IS_LINKED — boolean (Y / blank).Whether the account is already declared as linked to another login.
Linked User IDUSRP_ID_LINKED — text.If the row is linked, the other login it points to.

Hidden columns kept for downstream screens: USRP_PRIVILEGED, USRP_TECHNICAL, USRP_GENERIC.

JDE-specific

The default grouping key is JDE Address Number (AN8). On other source systems, the field is renamed but the rule is the same — Nomasx-1 still uses the foreign key the source uses to point to the person record.

Tips & best practices​

  • Read the duplicate group as a story. Old account Created earlier, last login years ago, Inactive vs new account Created recently, last login this week, Active → the old one is a leftover, deactivate or archive it.
  • An inactive duplicate already linked (Is Linked = Y) is a closed case — leave it alone and focus on rows with no linked indicator.
  • Two active duplicates is the alert worth investigating first — someone holds two effective logins on the same application, which doubles the surface to audit and may already be hiding an SoD breach.
  • Use the Settings → Users properties screen to declare a known-good duplicate pair once and remove it from this list permanently.