Skip to main content

OUT — Details

The OUT — Details screen is the raw Object Usage Tracking record. One line per (Application, Component, User, Object, Version) quintuplet — every distinct call captured by the source system, with the timestamp of the most recent invocation.

This is the data set behind every aggregation Nomasx-1 produces — OUT — Components, OUT — Users / Roles, OUT — Objects, Last Usage in the user audit.

At a glance​

Nomasx-1 · Applications · OUT · DetailsAPPUSEROBJECTDESCRIPTIONVERSIONLAST USAGE12JDOEP0411Standard Voucher EntryZJDE00012026-05-1412JDOEP03B11Customer Ledger InquiryZJDE00012026-05-1312MSMITHP03013Customer MasterZJDE00012026-05-1212SVC_BATCHR31410MRP GenerationXJDE00012026-05-14

Goal of the view​

For each (user, object, version) tuple ever invoked on a connected application:

  • The raw evidence. Every other OUT view is an aggregation of this dataset — when something looks off in the summary, this is the screen to drill into.
  • Per-user per-object timeline. Filter on a user and read the full inventory of what they have ever invoked, sorted by date.
  • Component traceability. The hidden Component column carries the licence bucket — used internally by drill-down navigation from OUT — Components.
JDE-specific

This view is built on top of LICENSE_JDE_OUT — the JDE Object Usage Tracking table. The component dimension is derived from the System Code mapping. Other source systems can produce an equivalent dataset by exposing their own usage / audit log.

Columns​

ColumnSourceWhat it tells you
Application IDLOUT_APPS_ID — application identifier. Filterable.The connected application.
User IDLOUT_USER — user identifier. Filterable, scoped to the application.Who invoked the object.
ObjectLOUT_OBJECT — technical object. Filterable.What was invoked.
DescriptionJDEO_DESCRIPTION — friendly object label.Human-readable label of the object.
VersionLOUT_VERSION — processing version.Which configuration variant was used.
Last usageLAST_USAGE — date of the most recent invocation.When the call happened.

Hidden columns kept on the row: CPT_ID (used by the drill-down from OUT — Components).

Tips & best practices​

  • Filter on a User ID + sort by Last usage descending — the user's usage trail, ordered. Anything older than the access-review window is fair game for revocation.
  • Filter on an Object to see every user that invoked a given program, plus the dates. A long-tail of dormant users on a sensitive object is the cleanest revocation argument.
  • Compare with the Rights matrix — a user invoking an object without an obvious declared right means either an inherited rule (cross-check with *ALL sign-on) or a security bypass.
  • A row with a recent Last usage on a sensitive object is one of the strongest evidence pieces for an audit — file the line under the relevant SoD finding.