Results for “okr_ip_litworks_b”

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

Overview

OKR_IP_LITWORKS_B is the base table in Oracle E-Business Suite for storing Literary Works Intellectual Properties within the OKR (Contracts for Rights) module. OKR itself is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2, meaning the module is retained for backward compatibility and historical data reference but is no longer actively enhanced or supported for new implementations. The literal description attached to the object refers to it as the "Base table for storing Litrary Works Intellectual Properties," and its presence in the ETRM catalog confirms it as a legacy data object rather than a current functional component.

Functionally, this table holds the specialization attributes that distinguish a literary work from other intellectual property types managed through the OKR rights management framework. Those attributes are not repeated in the common table; instead, OKR_IP_LITWORKS_B extends the shared IP definition held in OKR_IP_COMMON_B through a shared primary key, IP_ID. This is a classic subtype/detail pattern: a single IP record is written to the parent table and, when the IP corresponds to a literary work, a corresponding row is written here with the type-specific columns.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. In practice, OKR_IP_LITWORKS_B behaves as a satellite of the IP hub (represented by IP_ID in OKR_IP_COMMON_B), carrying descriptive, type-specific attributes rather than defining new business entities or relationships. Treating it as a satellite is a reasonable heuristic for downstream modeling, though it is not an implemented Data Vault object in the Oracle database itself.

Key Information Stored

The metadata documents only a small, precise set of columns and constraints. The most important structural facts are:

• IP_ID — The primary key column, and the sole documented column. It is the surrogate identifier that both uniquely identifies a row and simultaneously acts as a foreign key to OKR_IP_COMMON_B.
• OKR_IP_LITWORKS_PK — The primary key constraint defined over IP_ID.
• OKR_IP_LITWORKS_B.IP_ID → OKR_IP_COMMON_B.IP_ID — The documented foreign key relationship linking this subtype row to its parent intellectual property definition.

Because IP_ID serves as both the primary key of this table and a foreign key into the parent, there is no separate business-key column documented for OKR_IP_LITWORKS_B. Business identification of a literary work is therefore inherited from OKR_IP_COMMON_B; any unique business key (for example an IP number or title) lives in the parent table, not here. The metadata does not enumerate any additional descriptive columns such as title, author, ISBN, publication date, or rights territory, even though a fully populated legacy implementation would likely have contained them. Any such columns are unverifiable from the provided metadata and should not be assumed. The ETRM implementation note states the table is "Not implemented in this database," meaning it may exist structurally in some environments while remaining unpopulated.

Common Use Cases and Queries

Because OKR is obsolete, practical use cases center on historical reporting, data migration, or archival extraction rather than live transaction processing. Typical scenarios include retrieving all literary works for a rights contract, reconciling IP hierarchies, and migrating legacy rights data into a successor system.

A representative query joining the subtype to its parent, using the documented key, is:

• SELECT c.ip_id, l.ip_id FROM okr_ip_litworks_b l, okr_ip_common_b c WHERE l.ip_id = c.ip_id;
• An outer-join pattern to isolate literary works among all IP records: SELECT c.ip_id FROM okr_ip_common_b c, okr_ip_litworks_b l WHERE c.ip_id = l.ip_id (+);

Common reporting uses include counting literary works versus other IP types, validating that every literary work has a matching parent row (orphan detection), and extracting the full set of IP identifiers for a migration mapping. Because the table carries no independently documented descriptive attributes, most reports must join to OKR_IP_COMMON_B to obtain meaningful business information.

Related Objects

The relationship data identifies the following significant object relationships. Where the metadata documents a foreign key, it is stated explicitly; other related objects mentioned below are described only as contextual.

• OKR_IP_COMMON_B — The parent table holding the common intellectual property definition. Joined on IP_ID, which is this table's primary key and its foreign key into the parent.
• OKR_IP_LITWORKS_PK — The primary key constraint on IP_ID that enforces uniqueness of each literary work record.
• OKR_IP_LITWORKS_TL — The translated-attributes counterpart commonly present for base tables, holding language-specific descriptive columns.
• OKR_IP_COMMON_TL — The translated table for the parent IP definition, joined through OKR_IP_COMMON_B for multilingual reporting.
• Other OKR_IP_* subtype tables — Sibling specialization tables sharing the same IP_ID pattern, permitting union queries across IP categories.
• OKR rights and contract APIs — Legacy programmatic interfaces that reference the IP identifier chain for rights transactions.

Given the obsolete status of OKR, these relationships should be treated as read-only for historical and migration purposes.