Search Results okr_ip_software_b_pk

Overview

OKR_IP_SOFTWARE_B is a base table within the Oracle E-Business Suite module OKR — Contracts for Rights, a component historically associated with the management of intellectual property rights, royalties, and licensing agreements. In the ETRM (E-Business Suite Technical Reference Manual) documentation provided for Oracle EBS 12.1.1 and 12.2.2, this table is flagged as Obsolete, and the implementation notes explicitly state that it is not implemented in this database. Its documented purpose is to serve as the base table for storing software intellectual property records, with the description also referencing literary works intellectual properties — a description that appears to be carried over from a related sibling table such as OKR_IP_LITERARY_B.

From a data modeling perspective, the table holds a single foreign key relationship: OKR_IP_SOFTWARE_B.IP_ID references OKR_IP_COMMON_B. The heuristic Data Vault classification supplied in the metadata is satellite-leaning, which suggests that in a Data Vault 2.0 model this table is best treated as a satellite attached to the hub represented by OKR_IP_COMMON_B, rather than as an independent hub or a link table. This classification aligns with the observed structure — a shared IP identifier foreign key plus descriptive attributes.

Key Information Stored

The documented metadata for OKR_IP_SOFTWARE_B is sparse, so only a limited set of columns can be asserted with authority:

• IP_ID — the single documented column, serving as the primary key column for the OKR_IP_SOFTWARE_B_PK constraint and simultaneously as a foreign key to OKR_IP_COMMON_B.IP_ID. Because IP_ID is shared with the common table, it functions as a surrogate primary key within this table while also acting as the business-key carrier inherited from OKR_IP_COMMON_B.

No additional descriptive columns (for example, software title, publisher, version, or licensing attributes) are enumerated in the ETRM excerpt. In a typical EBS OKR satellite pattern, columns of that nature would reside here to hold software-specific attributes distinct from the shared IP header stored in OKR_IP_COMMON_B. Because the table is documented as not implemented, DBAs should treat any column-level assumptions beyond IP_ID as informative rather than authoritative.

Common Use Cases and Queries

Since the table is obsolete and absent from implemented schemas, live production use cases are limited. The principal scenarios are historical review, migration analysis, and data lineage work:

• Locating software IP records — joining the satellite to its hub to retrieve the shared IP details:
  SELECT s.ip_id, c.* FROM okr_ip_software_b s JOIN okr_ip_common_b c ON s.ip_id = c.ip_id;
• Obsolete object auditing — querying dba_objects or dba_tab_columns to confirm whether the table exists in a given 12.1.1 or 12.2.2 instance.
• Upgrade and migration assessment — identifying references to OKR_IP_SOFTWARE_B in customizations before patching from 12.1.1 to 12.2.2.
• Data Vault mapping documentation — recording the table as a satellite source feeding the OKR_IP_COMMON_B hub in a warehouse model.

Related Objects

The most significant related object is the one directly referenced by the documented foreign key:

• OKR_IP_COMMON_B — the parent (hub) table holding the shared intellectual property header. Joined on OKR_IP_SOFTWARE_B.IP_ID = OKR_IP_COMMON_B.IP_ID. This is the sole FK relationship documented in the ETRM metadata.
• OKR_IP_SOFTWARE_B_PK — the primary key constraint defined on IP_ID.

Sibling satellite-style tables in the OKR IP family (for example, literary or other IP-type base tables) are likely to exist by analogy, but these are not confirmed in the supplied metadata and should be verified against the actual data dictionary before being relied upon.