Skip to main content

OUT — Users / Roles

The OUT — Users / Roles screen pivots the OUT data by user. One line per (Application, Component, User) triplet. Each row brings the user's status (active / inactive), the technical and generic flags, the linked-user reference and the creation / last-login dates — everything needed to interpret the usage in the context of who the user is.

A row with high usage on a sensitive component carries a different weight depending on whether the user is a real person, a technical batch account or a generic shared login.

At a glance​

Nomasx-1 · Applications · OUT · Users / RolesAPPUSERSTATUSCREATEDLAST LOGINTECHNICALGENERICLINKED USER12JDOEActive2019-03-142026-05-14NN—12SVC_BATCHActive2017-04-022026-05-14YN—12SHARED01Active2015-09-012026-05-13NY—12J.DOEInactive2014-02-102019-03-13NNJDOESorted by LOUT_USER · 14 technical, 3 generic, 1 linked to a primary account

Goal of the view​

For each user that has invoked at least one object of a licence component:

  • Sort the noise from the signal. Technical and generic users are tagged so they can be excluded from the audit if needed.
  • Read activity in identity context. Created + Last login + Status give the full account-hygiene context next to the usage.
  • Spot consolidated identities. Linked User signals an account already declared as a duplicate of another login. Counting it twice in licence reporting would over-count the user.
JDE-specific

Tagging of technical / generic / linked users is held in SECURITY_USERS_PROP. The flag values are maintained on the Settings → Users properties screen. Other source systems can use the same tagging mechanism via a corresponding query.

Columns​

ColumnSourceWhat it tells you
Application IDLOUT_APPS_ID — application identifier. Filterable.The connected application.
ComponentCPT_ID — licence component. Filterable, hidden by default.Used by the drill-down from OUT — Components.
User IDLOUT_USER — user identifier. Lookup against the user catalog.Who used the component.
StatusUSR_STATUS — 01 means Active.Account state in the source system.
Creation DateUSR_DT_CREATION — date (string-formatted).When the account was created.
Login DateUSR_DT_LOGIN — date (string-formatted).Last authentication.
TechnicalUSRP_TECHNICAL — Y / N.Account flagged as technical / batch — usually excluded from headcount-based licence calculations.
GenericUSRP_GENERIC — Y / N.Account flagged as a shared / generic login — used by multiple people, not headcount.
Linked UserUSRP_ID_LINKED — text.If the account is declared as a duplicate, the primary login it points to.

Tips & best practices​

  • Filter on Technical = N and Generic = N to get the real human usage — the figure to discuss with the business when sizing the licence.
  • Inactive users with recent usage should not exist — if the row shows up, the activity happened before deactivation but the screen still surfaces the last touch. Confirm the deactivation date is post the last-usage date.
  • A row with a Linked User means the licence allocation should follow the primary account, not the linked one. Filter it out before counting.
  • Combine with OUT — Objects to see which specific programs of the component each user invoked.