Results for “okr_ip_rgts_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKR_IP_RGTS_B is a base table within the Oracle E-Business Suite product family OKR — Contracts for Rights, a module that has been designated Obsolete in the ETRM reference documentation. The table stores the association between an intellectual property record and a rights type, effectively defining which rights are attached to a given IP asset. In ETRM terms, an intellectual property record is the parent entity that owns or controls creative content, while the rights type describes the category of rights (for example, publishing, broadcast, or reproduction rights) that can be exercised over that content. OKR_IP_RGTS_B therefore acts as the definitional bridge between IP and the rights available against it.

The ETRM metadata notes that the table is not implemented in the documented database, reflecting the obsolete status of the OKR product line. The FK structure mined from the metadata classifies OKR_IP_RGTS_B as satellite-leaning, which is a modeling suggestion rather than a physical fact. In Data Vault terms, a satellite records descriptive attributes about a hub or link key. Here, the table carries attributes about the IP-to-Rights-Type relationship, with its identity dependent on the surrounding hubs, so it behaves like satellite-level detail rather than an independent hub.

Key Information Stored

The documented metadata exposes a small set of structurally significant columns:

• ID — the surrogate primary key, defined by constraint OKR_IP_RGTS_B_PK. It uniquely identifies each row in the table and is the internal join key used across the OKR schema.
• IP_ID — foreign key to OKR_IP_COMMON_B, identifying the intellectual property record to which the rights assignment belongs.
• RGTP_ID — foreign key to OKR_RIGHT_TYPES_B, identifying the rights type being attached to the IP record.

These three columns constitute the documented structural core. IP_ID and RGTP_ID together represent the natural business-key candidate for the IP-to-Rights-Type association, while ID is the surrogate key. The metadata does not enumerate additional descriptive or audit columns; any remaining attributes (dates, flags, descriptive text) are not documented and should be confirmed against the physical implementation where it exists.

Common Use Cases and Queries

The primary reporting use case is enumerating the rights attached to a particular IP asset, or conversely, determining which IP assets carry a particular rights type. A representative query joining the base table to its parent IP and rights-type tables:

• SELECT r.ID, r.IP_ID, r.RGTP_ID FROM OKR_IP_RGTS_B r WHERE r.IP_ID = :ip_id;
• SELECT i.IP_ID, t.RGTP_ID FROM OKR_IP_RGTS_B r JOIN OKR_IP_COMMON_B i ON r.IP_ID = i.IP_ID JOIN OKR_RIGHT_TYPES_B t ON r.RGTP_ID = t.RGTP_ID;

Because OKR is obsolete, these patterns are primarily relevant to historical data migration, legacy reporting reconciliation, or data-archival projects. Where the module is still installed, the table supports rights-validation checks during contract creation and rights-availability reporting for licensing teams.

Related Objects

The documented FK relationships define the immediate dependency graph:

• OKR_IP_COMMON_B — parent IP master table, joined via OKR_IP_RGTS_B.IP_ID.
• OKR_RIGHT_TYPES_B — rights-type reference table, joined via OKR_IP_RGTS_B.RGTP_ID.
• OKR_IP_RGTS_TXN_B — transaction-level child table referencing this table through OKR_IP_RGTS_TXN_B.IP_RIGHTS_ID, holding transactional occurrences of the defined rights.

These three tables, together with the OKR_IP_RGTS_B_PK constraint, form the documented relationship context. Any broader OKR object set (contract, royalty, or usage tables) is not evidenced in the supplied metadata and should be verified separately.