Skip to main content

System Code

The System Code screen maps every JDE System Code (SY) to its functional module and to the licence component Nomasx-1 uses for usage / compliance reporting. One line per SY. This is the table behind the Component column of every OUT view.

Maintaining this mapping correctly is what makes the licence compliance analysis truthful.

At a glance​

Nomasx-1 · Settings · JDE · System CodeSYDESCRIPTIONMODULECOMPONENT E1COMPONENT04Accounts PayableFinancialsCFINFinancials42Sales Order ManagementDistributionCSODistribution08Human Capital MgmtHuman ResourcesCHRHuman Resources

Goal of the view​

  • Map JDE System Codes to functional modules. The basis for the Module breakdown across the application.
  • Tie each SY to a licence component. This is the only place where Nomasx-1 knows that a P0411 (SY = 04) consumes the Financials licence.
  • Carry the E1 component label. When Oracle ships its own component naming in JDE EnterpriseOne, the mapping keeps both perspectives readable.

Columns​

ColumnSourceWhat it tells you
SYSYC_ID — JDE System Code.The two-character code (e.g. 04, 42, 08).
DescriptionSYC_DESCRIPTION — text.Friendly module description.
ModuleSYC_MODULE — high-level grouping.Functional area used in non-licence views.
Component E1SYC_COMPONENT_E1 — JDE E1 component code.The code Oracle exposes inside JDE EnterpriseOne for the component.
Component IDSYC_CPT_ID — links to Pricing → Components.Nomasx-1 licence component identifier.
ComponentCPT_COMPONENT — denormalised label.Human-readable licence component label.

Edit dialog​

The grid is read-only on the row. Double-click a row to open the editor and adjust the description, module or licence component.

Edit JDE System CodeSY04DescriptionAccounts PayableModuleFinancialsE1 ComponentCFINComponentFinancials ▾
FieldWhat to enter
SYRead-only. The two-character JDE System Code.
DescriptionFriendly module description shown across the application.
ModuleHigh-level functional area (Financials, Distribution, …).
E1 ComponentComponent code as Oracle exposes it in JDE EnterpriseOne.
ComponentDrop-down of the Nomasx-1 components from Pricing → Components.

Tips & best practices​

  • Bring this mapping in line with your contractual catalog, not the bundled Oracle defaults. A licence renegotiation often introduces new component names — update them here.
  • Every new SY introduced by a JDE upgrade must be classified here; otherwise it appears unmapped in the OUT views.
  • Audit changes through the hidden SYC_AUDIT_USER / SYC_AUDIT_DATE columns — useful when explaining why a component count moved.