Search Results okr_ip_relations_pk




Overview
Explore in AI Chat

Overview

The OKR_IP_RELATIONS_B table belongs to the Oracle EBS module OKR – Contracts for Rights, which is classified as obsolete in the EBS 12.1.1 and 12.2.2 documentation set. It is the base table of the OKR Intellectual Property (IP) Relations entity, and its purpose is to capture a directional relationship between two distinct pieces of intellectual property. Each row therefore records an association from one IP record to another within the context of a rights contract. This structure is the foundation for representing hierarchies, derivations, dependencies, or cross-references between IP assets such as titles, trademarks, or licensed works.

From a modeling perspective, the metadata classifies this object heuristically as a link in Data Vault terms. This classification is a suggestion rather than a documented fact: the table has no descriptive attribute columns beyond its identifiers, and its key structure is entirely composed of references to other entities. A link interpretation is consistent with the fact that the table exists to associate two business entities (the "from" IP and the "to" IP) and a governing contract header, rather than to store changing descriptive detail about a single entity.

The table is documented as not implemented in the reference database, meaning the object may not exist or may be empty in a standard installation. This is expected for an obsolete module and should be verified before any query is issued against it.

Key Information Stored

The documented implementation metadata identifies a small set of columns, all of which function as identifiers rather than descriptive attributes:

  • IPR_ID – The surrogate primary key, generated through the OKR_IP_RELATIONS_PK constraint. It uniquely identifies each relationship row and is the column most other objects would use to reference a specific IP relation.
  • FROM_IP_ID – The originating intellectual property in the relationship. It carries a foreign key to OKR_IP_COMMON_B, making it a business-key candidate in combination with the other identifiers.
  • TO_IP_ID – The target intellectual property. It also references OKR_IP_COMMON_B, and together with FROM_IP_ID defines the direction and meaning of the association.
  • KHR_ID – The contract header reference, pointing to OKC_K_HEADERS_B. It situates the IP relationship within a specific rights contract.

The combination of FROM_IP_ID, TO_IP_ID, and KHR_ID is the practical business key: it answers which IP relates to which other IP, under which contract. No additional descriptive columns are documented, which reinforces the link classification. Any attributes such as relationship type or effective dates would be held in related objects or not represented at all in this obsolete structure.

Common Use Cases and Queries

Because the module is obsolete, the principal use cases are historical reporting, data migration assessment, and impact analysis. A typical query resolves the relation against the common IP table to obtain recognizable IP names:

  • Direct IP mapping: select IPR_ID, FROM_IP_ID, TO_IP_ID, KHR_ID from OKR_IP_RELATIONS_B to list all captured relationships, optionally filtered by KHR_ID to isolate one contract.
  • Joining to IP detail: join FROM_IP_ID and TO_IP_ID separately to OKR_IP_COMMON_B (two aliases) to present both ends of each relation in human-readable form.
  • Contract-centric reporting: join KHR_ID to OKC_K_HEADERS_B to group relations by contract number or contract type.
  • Integrity checks: left-join the FK targets and filter for nulls to detect orphaned relations, a common pre-migration validation step.
  • Graph-style analysis: self-join or recursively traverse from/to pairs to reconstruct IP dependency trees.

Related Objects

  • OKR_IP_COMMON_B – The master IP table. It is referenced twice: OKR_IP_RELATIONS_B.FROM_IP_ID and OKR_IP_RELATIONS_B.TO_IP_ID both point to it. This is the most leveraged join partner.
  • OKC_K_HEADERS_B – The contracts header table, joined via OKR_IP_RELATIONS_B.KHR_ID. It provides the contract context for each IP relationship.
  • OKR_IP_RELATIONS_TL – The translation table typically paired with the "_B" base table in EBS, holding language-specific relationship text where applicable.
  • OKR_IP_COMMON_TL – The translated companion to the common IP table, useful when reporting IP names across languages.
  • OKR_IP_RELATIONS_PK – The primary key constraint on IPR_ID, which any dependent child table or API would reference.
  • OKC_K_HEADERS_TL and related OKC contract child tables – supplementary objects joining through KHR_ID for full contract reporting.

Together these objects form the documented relationship graph around OKR_IP_RELATIONS_B; given the obsolete status, availability should always be confirmed in the target instance.