Skip to main content

JD Edwards

The JD Edwards screen summarises the licence-relevant figures for every JDE application connected to Nomasx-1. One line per JDE application (filter APPS_TYPE = 'JDE').

This is the dashboard Oracle's JDE licence team asks for: how many distinct human users are active, how many actually transacted in the last 90 days, and how many accounts are missing from one side or the other.

At a glance​

Nomasx-1 · Licenses · JD EdwardsAPPLICATIONACTIVE USERSTRANSACTIONAL (90 D)TRANSACTIONAL · NO USER12 — JDE Production218182413 — JDE Test62380READING THE NUMBERSActive = security users · Transactional = touched a JDE table in 90 d · Transactional · No user = transactions without a security account behind them.

Goal of the view​

For each JDE application:

  • Headline active count. Active users is the number of distinct accounts with USR_STATUS = '01' and at least one role assignment — the JDE side of the headcount.
  • Real usage. Transactional counts how many of those active users actually wrote something in the last 90 days. This is the figure to bring to an Oracle licence renegotiation.
  • Detect orphan transactions. Transactional · No user counts source-system transactions whose JDE user has been deleted from the security table — a strong indicator of clean-up gaps.

The hidden No-transaction users column is the inverse — active users with zero transaction over the window — visible in deeper drilldowns but not on the headline.

Columns​

ColumnSourceWhat it tells you
Application IDAPPS_ID — application identifier.The JDE application.
Active usersJDE_ACTIVE_USERS — distinct active users with at least one role.Effective licence headcount.
Transactional usersJDE_TRANSACTION_USERS — active users that transacted in the last 90 days."Used the system" cohort.
No-transaction usersJDE_NOTRANSACTION_USERS — active users with no transaction. Hidden.Inactive accounts — candidates for revocation.
Transactional · No userJDE_TRANSACTION_NOUSERS — transactions in the window without a matching security user.Cleanup gap.

Tips & best practices​

  • Transactional × component rate is the most useful negotiation lever — if the Transactional count is well below the Active count, the licence is over-sized.
  • Address Transactional · No user first — every transaction without a security user means either the user was deleted while keeping rights, or a non-JDE program writes through a service account that should be tagged.
  • The view is JDE-specific. For other source systems, equivalent screens can be built around their own usage tables (see Object Usage Tracking for the underlying mechanism).
  • Combine with Subscribed Licenses to compare the Transactional number against the contractual entitlement.