Search Results okr_ip_ctrct_rels_dv




Overview

OKR_IP_CTRCT_RELS_DV is a denormalized database view within the Oracle E-Business Suite Contracts for Rights module (OKR), an obsolete component associated with intellectual property and rights management. The view presents a flattened, read-oriented projection of contractual relationships between intellectual property records and OKC contract headers. Its suffix "_DV" typically denotes a "document view" or "denormalized view," indicating that it aggregates descriptive attributes and lookup meanings that would otherwise require multiple joins at query time.

The view is documented as not implemented in the current database, meaning it exists in the ETRM metadata repository as a reference object but is not deployed in the instance from which the documentation was extracted. Its role is to supply reporting and integration consumers with a single source for contract-to-IP relationship data, including status codes and their business-friendly meanings, contract version numbers, IP type descriptors, and territory names. The user's search term, sts_code_meaning, corresponds directly to one of the view's derived columns, which is populated via the OKR_UTIL_PUB.GET_K_STATUS_MEANING function over the base STS_CODE column.

Underlying Base Objects

The view is defined over five base tables joined in a linear chain:

  • OKR_IP_CTRCT_RELS (alias IPCR) — the primary relationship table linking IP records to contract headers.
  • OKC_K_HEADERS_B (alias CHRB) — the base contract header table carrying status, version, and buy/sell indicators.
  • OKC_K_HEADERS_TL (alias CHRT) — the translated contract header table supplying the short description.
  • OKR_IP_COMMON_B (alias IPCB) — the base intellectual property common table holding identifiers, types, and origin data.
  • OKR_IP_COMMON_TL (alias IPCT) — the translated IP table providing the IP name.

The join predicates equate IPCR.CHR_ID to CHRB.ID, CHRB.ID to CHRT.ID, IPCR.IP_ID to IPCB.IP_ID, and IPCB.IP_ID to IPCT.IP_ID. No base objects are separately documented in the ETRM metadata beyond the view text itself; the relationships above are inferred from the view SQL.

Key Columns

Common Use Cases and Queries

Typical usage includes rights reporting, contract status dashboards, and integration extracts that require human-readable status and territory values without re-implementing the OKR utility functions.

SELECT contract_number,
       short_description,
       version,
       sts_code,
       sts_code_meaning,
       ip_identifier,
       ip_type_meaning,
       country_name
FROM   okr_ip_ctrct_rels_dv
WHERE  sts_code_meaning = 'Active';

A second common pattern joins the view back to OKC contract headers for header-level filtering, leveraging the contract number and status meaning to produce consolidated rights portfolios. Because the view is documented as not implemented, teams must confirm its deployment status in each instance and, where absent, replicate the underlying SQL directly against the five base tables.