Search Results okr_right_types_b_pk

Overview

OKR_RIGHT_TYPES_B is the base definition table for valid right types within the Oracle E-Business Suite module OKR — Contracts for Rights. In the Oracle EBS 12.1.1 and 12.2.2 releases, this module is documented as obsolete, meaning that the object is retained for backward compatibility and historical data integrity rather than active functional use. The table acts as a reference or lookup repository: each row defines a type of right that may be granted, licensed, or otherwise transacted under a rights contract.

From a Data Vault modeling perspective, the FK structure surrounding this table suggests a hub-leaning classification. Its central position as the target of multiple foreign keys, combined with its role as a stable definition of right types, aligns with the characteristics of a hub entity — a business concept with a durable identity and a surrogate key. This classification is a heuristic suggestion derived from the documented FK relationships and should be treated as a modeling aid rather than a normative statement.

Key Information Stored

The documented metadata identifies the primary key of OKR_RIGHT_TYPES_B as OKR_RIGHT_TYPES_B_PK, implemented on the ID column. This ID is the surrogate primary key and serves as the unique identifier for each right type record. Because the metadata excerpt does not enumerate additional columns, the following points distinguish what is documented from what is conventionally implied by an EBS base table of this nature:

• ID — The surrogate primary key, defined by the OKR_RIGHT_TYPES_B_PK constraint. It uniquely identifies each valid right type and is the column referenced by all downstream foreign keys.
• Business-key candidates — A base table of this type typically carries a user-facing name or code that serves as the business key. However, no unique index other than the primary key is documented in the provided metadata, so no specific business-key column can be confirmed from the source material.
• Descriptive attribute columns — Although the excerpt does not list specific column names, the table's stated purpose (a base table for valid right types) implies the presence of one or more descriptive or classification columns used during entry of rights data. These are not documented in the metadata above.

Only the ID column can be asserted with confidence from the provided documentation.

Common Use Cases and Queries

In practice, OKR_RIGHT_TYPES_B functions as a validation and lookup source for foreign keys on transactional and template rights records. Typical reporting and diagnostic patterns include listing all defined right types, resolving the right-type descriptions for rights held on an intellectual property record, and confirming that referential integrity is intact across the dependent tables.

A representative query joining the base table to its primary dependent is:

• SELECT t.ID, r.RGTP_ID FROM OKR_RIGHT_TYPES_B t, OKR_IP_RGTS_B r WHERE t.ID = r.RGTP_ID;

Because the module is obsolete, the most common operational use cases are historical reporting, data migration validation, and referential-integrity auditing rather than new transaction entry. Analysts frequently query this table to confirm that codes held in OKR_IP_RGTS_B, OKR_TEMPLATE_RGTS_B, and OKR_VALID_PROP_RGTS remain resolvable after upgrades or consolidations in 12.1.1 and 12.2.2 environments.

Related Objects

The following objects are documented as referencing OKR_RIGHT_TYPES_B through the RGTP_ID column. All three are foreign-key dependents and should be considered the most significant related tables:

• OKR_IP_RGTS_B — References OKR_RIGHT_TYPES_B via OKR_IP_RGTS_B.RGTP_ID. This is the transactional rights record associated with an intellectual property.
• OKR_TEMPLATE_RGTS_B — References OKR_RIGHT_TYPES_B via OKR_TEMPLATE_RGTS_B.RGTP_ID. This holds rights defined on templates.
• OKR_VALID_PROP_RGTS — References OKR_RIGHT_TYPES_B via OKR_VALID_PROP_RGTS.RGTP_ID. This table restricts which right types are valid for a given property.

These three dependents constitute the documented relationship set. When querying or migrating data, they should be joined on RGTP_ID = ID to preserve the documented referential integrity.