Skip to main content

Reclassification

The Reclassification screen overrides the default System Code that Nomasx-1 would otherwise apply to a JDE object. One line per object. Useful when the default SY of a program does not match its actual licence relevance — typically when a program is technically in H9 but commercially in Financials.

Each row says: for this object, use this SY instead of the default one. The change propagates to every OUT view and licence report that resolves through System Code.

At a glance​

Nomasx-1 · Settings · JDE · ReclassificationOBJECTDESCRIPTIONRECLASSIFIED SYP0411Z1Voucher Z-File Interface04R0008PDate pattern report09

Goal of the view​

  • Override the SY when JDE's own classification does not reflect the contractual reality.
  • Keep the override list short. Every entry is an exception — too many overrides make the licence model hard to defend in audit.

Columns​

ColumnSourceWhat it tells you
ObjectJDES_OBJECT — technical object.The program being reclassified.
DescriptionJDES_DESCRIPTION — friendly label.What the program does.
Reclassified SYJDES_SY — System Code.The SY Nomasx-1 should use instead of the JDE default.

Edit dialog​

Click Add to override the SY of a new object, or double-click a row to edit.

Edit reclassificationObjectP0411Z1DescriptionVoucher Z-File InterfaceReclassified SY04 ▾
FieldWhat to enter
ObjectSource-system program code (e.g. P0411Z1). Required.
DescriptionFriendly label of what the program does.
Reclassified SYDrop-down of the SY catalog. The value Nomasx-1 will use instead of the JDE default.

Tips & best practices​

  • Document the rationale of each override — a one-line description that a future auditor can read.
  • Re-validate the list after an Oracle upgrade. JDE sometimes moves an object between system codes, retroactively making an override redundant.
  • Avoid systemic overrides — if more than a handful of objects from the same module need reclassification, consider revisiting the mapping in System Code instead.