Components
The Components screen is the master catalog of every licence component Nomasx-1 reasons about. One line per component, with the Price list it belongs to, its category and a friendly name. Every other licence and OUT screen joins through this catalog.
It is the table to maintain whenever Oracle introduces a new component or renames an existing one.
At a glance
Goal of the view
- The single source of truth for component naming across Nomasx-1.
- Three classification dimensions. Price list (the Oracle catalog), Category (Applications, Database, Middleware…) and Component (the human-readable name).
Columns
| Column | Source | What it tells you |
|---|---|---|
| ID | CPT_ID — numeric component identifier. | Referenced by every other licence / Oracle / OUT screen. |
| Price list | CPT_LISTS — Oracle catalog. | The Oracle price book the component is sold under. |
| Category | CPT_CATEGORY — broad classification. | Applications, Database, Middleware, … |
| Component | CPT_COMPONENT — friendly name. | Label rendered across the application. |
Edit dialog
Double-click a row to edit a licence component.
| Field | What to enter |
|---|---|
| Price list | Oracle price book label the component is sold under. |
| Category | Broad classification (Applications, Database, Middleware, …). |
| Component | Human-readable component name as shown across the rest of the application. |
Tips & best practices
- Add a new component once and reference it widely. Avoid creating per-application duplicates — the model is global.
- Keep the Price list aligned with Oracle's price book so the catalog is recognisable to the LMS auditor.
- Audit changes through
CPT_AUDIT_USER/CPT_AUDIT_DATE— useful when a column suddenly displays a different label.