Skip to main content

CSI

The CSI screen lists every Oracle Customer Support Identifier declared in Nomasx-1. One line per contract. Each row carries the identifier, a friendly description, the contract validity dates and its current status.

The CSI is the contractual anchor: the entitlement counts (subscribed licences, support), the usage analysis (Usage report) and the financial impact computation (Financial report) all attach to a CSI through the components catalog.

At a glance​

Nomasx-1 · Licenses · CSICSI IDDESCRIPTIONFROMTOSTATUS12345678JD Edwards EnterpriseOne — corporate2018-01-012026-12-31Active12345910Oracle Database EE — production2017-04-012026-09-30Active11982001Legacy Internet Application Server — retired2008-06-012024-12-31Closed3 active CSI · 1 closed · all-time inventory · drives Subscribed Licenses

Goal of the view​

For each CSI under management:

  • Inventory the support contracts. Every active CSI must be associated with at least one application — otherwise it is a contract for an application that has nothing left.
  • Track validity windows. From / To dates drive the renewal calendar.
  • Capture the status. Active / Closed matches what Oracle's contract management portal shows. Closed CSIs are kept for historical reporting but no longer count.

Columns​

ColumnSourceWhat it tells you
CSI IDCSI_ID — numeric contract identifier.The Oracle reference.
DescriptionCSI_DESCRIPTION — text.Friendly label.
From dateCSI_FROM_DATE — date.Start of the support coverage.
To dateCSI_TO_DATE — date.End of the current support window.
StatusCSI_STATUS — Active / Closed.Whether the contract is still in force.

Audit columns (CSI_AUDIT_USER, CSI_AUDIT_DATE) are hidden but tracked on the row.

Edit dialog​

Click Add to register a new CSI, or double-click a row to edit. The dialog has three tabs. The Applications and Components tabs are hidden on Add — they appear only once the CSI exists.

Edit CSI — 12345678Contract SupportApplicationsComponentsCSI ID12345678DescriptionJD Edwards EnterpriseOne — corporateFrom2018-01-01To2026-12-31StatusActive ▾

Tab 1 — Contract Support​

The contract identity. All fields are mandatory.

FieldWhat to enter
CSI IDNumeric Oracle contract identifier.
DescriptionFriendly label for the contract.
From dateStart of the support coverage.
To dateEnd of the current support window.
StatusActive while the contract is in force, Closed once it ends.

Tab 2 — Applications​

Nested table linking the CSI to the applications it covers. Add one row per application: an entry here is what makes the contract count for that application in Subscribed Licenses and the compliance reports. Hidden on Add.

Tab 3 — Components​

Nested table listing the licensed components per CSI, with their quantities and metric. Aggregates feed the Subscribed Licenses page. Hidden on Add.

Context menu​

Right-click a row to open the row menu.

ActionWhere it lands
Display ApplicationsList of applications attached to the CSI.
Display ComponentsList of components subscribed under the CSI with their quantities.

Tips & best practices​

  • Sort by To date ascending to surface the next renewals — the budget-planning view.
  • Confirm every active CSI maps to at least one application in Subscribed Licenses. An orphan CSI is a contract paid for an application that no longer uses it.
  • Closed CSIs remain visible for audit traceability — leave them in place rather than deleting the row.
  • The screen is writable — only the licence administrator should edit it. Each change is captured in the audit columns and surfaces in the Audit Trail if the underlying table is being audited.