Search Results okr_template_rgts_b

Overview

OKR_TEMPLATE_RGTS_B is a table within the Oracle E-Business Suite module OKR — Contracts for Rights. The OKR product line historically supported rights management and royalty processing for media, publishing, and intellectual property industries, and this table belongs to that family of objects. The ETRM metadata explicitly flags the module as obsolete and states that OKR_TEMPLATE_RGTS_B is not implemented in this database. Consequently, in Oracle EBS 12.1.1 and 12.2.2 environments, this object should be treated as a historical or documentation-only artifact; it will not appear as a populated runtime table in a standard installation unless a legacy OKR schema has been preserved.

Functionally, according to its naming convention and foreign key relationships, the table represents an association between rights templates and right types or IP common records. The heuristic Data Vault classification mined from the FK structure is link, which suggests this object models a many-to-many relationship between two business entities rather than holding descriptive attributes. In Data Vault modeling terms, it would be modeled as a link table resolving the relationships between an IP common hub and a right types hub.

Key Information Stored

The metadata identifies a small set of documented columns, consistent with a link-style table:

• ID — The surrogate primary key column, constrained by OKR_TEMPLATE_RGTS_B_PK. This is the unique identifier for each association row.
• IP_ID — Foreign key referencing OKR_IP_COMMON_B. This identifies the intellectual property common record involved in the template-right relationship.
• RGTP_ID — Foreign key referencing OKR_RIGHT_TYPES_B. This identifies the specific right type associated with the template record.

The ETRM documentation does not enumerate additional attribute columns for this table. Given its link classification, supplementary columns would typically be limited to standard EBS "WHO" columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and potential context or descriptive fields. However, these are not confirmed in the provided metadata and should be verified against an actual installed schema if the object exists.

The surrogate primary key ID is distinct from any business-key candidate. No unique index on the combination of IP_ID and RGTP_ID is documented in the metadata, though such a composite unique constraint would be typical for a link table to prevent duplicate associations.

Common Use Cases and Queries

Because the table is not implemented in a standard database, its practical use is largely confined to migration, archival, or forensic analysis scenarios. Typical query patterns include:

• Joining to OKR_IP_COMMON_B to resolve IP descriptors for a given template: SELECT t.ID, i.NAME FROM OKR_TEMPLATE_RGTS_B t JOIN OKR_IP_COMMON_B i ON t.IP_ID = i.ID;
• Joining to OKR_RIGHT_TYPES_B to retrieve right type descriptions: SELECT t.ID, r.NAME FROM OKR_TEMPLATE_RGTS_B t JOIN OKR_RIGHT_TYPES_B r ON t.RGTP_ID = r.ID;
• Reporting on all right types assigned to a given IP across templates.

These queries are illustrative only and depend on the target schema retaining the table.

Related Objects

The metadata documents two foreign key relationships, defining the immediate object neighborhood:

• OKR_IP_COMMON_B — referenced via OKR_TEMPLATE_RGTS_B.IP_ID; the parent IP common record.
• OKR_RIGHT_TYPES_B — referenced via OKR_TEMPLATE_RGTS_B.RGTP_ID; the parent right type definition.

Sibling objects likely related through the OKR template family — such as OKR_TEMPLATE_B or template header tables — are not documented in the supplied metadata and should be confirmed by examining the full OKR schema if it exists. In Oracle EBS 12.1.1 and 12.2.2, no public APIs or views specific to this table are catalogued in the excerpt, reinforcing its status as an obsolete and non-implemented historical object.