Skip to main content

Menus

The Menus screen lists every application menu entry known to Nomasx-1. One line per leaf — i.e. the action a user can actually launch from the source-system menu. Each row carries the full hierarchy of parent menus, the technical object the leaf invokes, and the licence component the object falls under.

The screen is what you open to understand the navigation of a connected application from a security perspective: what is reachable from where, under which licence weight.

At a glance​

Nomasx-1 · Applications · MenusAPPROOTLEVEL 1LEVEL 2OBJECTFORMCOMPONENT12G0911Accounts PayableDaily ProcessingP0411W0411AFinancials12G0911Accounts PayableSetupP0401W0401AFinancials12G42Sales Order MgmtSales Order InquiriesP4210W4210EDistribution1 — 50 of 4 280 menu leaves · 7 licence components

Goal of the view​

For each menu leaf in a connected application, answer three questions:

  • What does the leaf launch? Object, form and version — the three values the source system needs to open the screen.
  • Where does it live? Root + up to 9 nested levels — the breadcrumb that explains how a user gets there.
  • What licence does it consume? The component groups the underlying object into a billable bucket — see Licenses → JD Edwards for the volume rules.

Columns​

ColumnSourceWhat it tells you
Application IDMENU_APPS_ID — application identifier from the source system. Filterable.Which application the menu belongs to.
RootMENU_ROOT — top-level menu identifier (e.g. G0911). Filterable.The role-level entry point.
ObjectMENU_OBJECT — technical object launched (program, application, batch). Filterable.What the leaf actually calls.
FormMENU_FORM — form code within the object.The specific form (interactive screen) within the program.
VersionMENU_VERSION — processing version.Configuration variant used at runtime.
ComponentCPT_ID — licence component the object falls under. Filterable.The billable bucket — drives licence reporting.
Menu IDMENU_ID — task identifier on the leaf. Filterable.Source-system task code (e.g. JDE menu task ID).
Level 1 … Level 3MENU_LEVEL1, MENU_LEVEL2, MENU_LEVEL3 — nested labels. Level 1 is filterable.First three depths of the breadcrumb.
Level 4 … Level 10MENU_LEVEL4 … MENU_LEVEL10.Deeper levels — hidden by default but stored on the row for downstream screens.

Hidden columns kept on the row: MENU_SEQ_UKID (stable sequence), MENU_REFRESH (last sync), MENU_UKID (technical id).

JDE-specific

On JD Edwards EnterpriseOne, the menu tree is read directly from the JDE Solution Explorer tables. Object, Form and Version are the canonical JDE triplet to launch an interactive application or a batch UBE. The licence component is derived from the JDE System Code mapping (SETTINGS_JDE_SY → SETTINGS_LIC_COMPONENTS).

Tips & best practices​

  • Filter by Level 1 to focus on a single business area (Accounts Payable, Sales Order Mgmt, etc.) before tackling its security review.
  • Filter by Component to bring up every menu entry that consumes a specific licence — useful before re-negotiating module volumes.
  • Filter by Object to find every place a given program is exposed in the menu tree. A program reachable from multiple roots may need different security rules per entry point.
  • Cross-reference with Rights / Roles to confirm which roles grant access to each menu leaf.