Skip to main content

Pricing

The Pricing screen is the price book Nomasx-1 uses for the financial impact computation. One line per (Component, Metric). Each row carries the unit list price, the minimum quantity Oracle imposes on the metric, and the annual support fee.

It is the table the Financial Report multiplies by the compliance gap to produce the euros next to a non-compliant component.

At a glance​

Nomasx-1 · Settings · Pricing · PricingPRICE LISTCOMPONENTMETRICPRICEMINIMUMSUPPORTJDE FoundationFinancialsApplication User1 20010264Database TechOracle Database EENamed User Plus95025209Database TechOracle Database EEProcessor47 500110 450

Goal of the view​

  • Price book input. Per (Component × Metric), the unit list price and unit support fee.
  • Used by Financial Report. Multiply the compliance gap by these values to produce the euros that show up next to a non-compliant row.
  • Audit traceability. Changes to a row should be approved and audit-stamped.

Columns​

ColumnSourceWhat it tells you
IDPRC_ID — internal identifier.Numeric key of the row.
Price listCPT_LISTS — Oracle catalog.The catalog the row belongs to.
CategoryCPT_CATEGORY — Applications / Database / …Component category.
ComponentCPT_COMPONENT — component name.The component being priced.
MetricMET_DESCRIPTION — metric.The unit the price applies to.
PricePRC_PRICE — list price.Unit price, in the contract currency.
MinimumPRC_MINIMUM — minimum quantity.Oracle's minimum order for the metric (e.g. NUP minimum per processor).
SupportPRC_SUPPORT — annual support fee.Per-unit support cost — multiplied by 3 in the Financial Report.

Edit dialog​

Double-click a row to edit the price book entry.

Edit pricing rowComponentOracle Database EE ▾MetricNamed User Plus ▾Price950Minimum25Support209
FieldWhat to enter
ComponentDrop-down of Nomasx-1 components.
MetricDrop-down of metrics declared on Pricing → Metrics.
PriceUnit list price in the contract currency.
MinimumMinimum quantity Oracle imposes for this metric (e.g. 25 NUP per processor on Database EE).
SupportAnnual unit support fee. Multiplied by 3 in the Financial Report.

Tips & best practices​

  • Update the price book at renewal time — Oracle ships a new technical price list every year. Keeping the numbers current is what makes the financial impact view trustworthy.
  • Remember the Minimum — Oracle imposes a minimum (e.g. 25 NUP per processor on Database EE). A negative compliance below the minimum forces the purchase up to the minimum, not just the missing quantity.
  • Cross-reference with Subscribed Licenses to detect prices being applied to a metric the contract does not use.