Search Results okr_prop_types_b_pk




Overview

The OKR_PROP_TYPES_B table is the base table for valid property types within the Oracle EBS Contracts for Rights (OKR) module. It serves as a foundational reference or lookup table that defines the set of property types recognized by the application, providing the authoritative list against which other contracts-for-rights entities are validated. Property types in this context correspond to categories of intellectual property rights, such as copyrights, trademarks, patents, and similar intangible assets managed through OKR contracts.

The OKR module is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2, and the metadata explicitly notes that this table is not implemented in the current database. This indicates that the object may exist as a legacy or deprecated schema element retained for backward compatibility, or may have been superseded by alternative structures in later releases. The table nevertheless remains significant as a historical reference point for understanding the OKR data model and for environments where the module was previously active.

Based on the foreign key structure, the metadata offers a heuristic Data Vault classification of hub-leaning. This suggests that OKR_PROP_TYPES_B functions as a hub table, holding a distinct business concept (property type) identified by a stable business key, with satellite and link relationships distributed across dependent tables.

Key Information Stored

The documented columns for this table are limited to the primary key definition. The primary key constraint OKR_PROP_TYPES_B_PK is defined on the single column IP_TYPE. This column stores the identifier for each valid property type and serves as the business-key candidate that anchors all relationships to this table.

Because the available metadata does not enumerate additional descriptive columns, the following characteristics can be stated with confidence:

  • IP_TYPE — The primary key and the business-key identifier for a valid property type. All referencing tables join to this column.

In the typical OKR design pattern, a base table such as this is paired with a _TL translation table that stores language-specific descriptive names. The absence of descriptive columns in the documented metadata suggests that translated attributes reside elsewhere, consistent with the multilingual architecture of Oracle EBS.

Common Use Cases and Queries

The principal use case for this table is validation and classification of intellectual property records within the OKR module. Applications and reports reference it to resolve the meaning of an IP_TYPE value carried by common, classification, and party role records.

A representative query retrieving all valid property types is:

  • SELECT ip_type FROM okr_prop_types_b;

A validation query confirming that a given property type exists before inserting a dependent record:

  • SELECT 1 FROM okr_prop_types_b WHERE ip_type = :ip_type;

A join pattern linking common intellectual property records to their property type:

  • SELECT c.ip_type, c.* FROM okr_ip_common_b c, okr_prop_types_b p WHERE c.ip_type = p.ip_type;

Because the module is obsolete, these queries are primarily relevant to migration audits, historical data reconciliation, and legacy reporting projects.

Related Objects

Six dependent tables reference OKR_PROP_TYPES_B.IP_TYPE through foreign keys, all of which depend on the validity of the parent record:

  • OKR_IP_COMMON_B — references OKR_PROP_TYPES_B via IP_TYPE, storing the common intellectual property records.
  • OKR_CLSF_TYPES — references via IP_TYPE, holding classification type definitions.
  • OKR_PARTY_ROLES — references via IP_TYPE, associating parties with property roles.
  • OKR_PROP_QSTNS_B — references via IP_TYPE, storing property-related questionnaire definitions.
  • OKR_PROP_RESP_SET_B — references via IP_TYPE, holding responsibility set configurations.
  • OKR_VALID_PROP_RGTS — references via IP_TYPE, defining which property rights are valid for each type.

These relationships confirm the hub-leaning role of the table and underscore its central position in the OKR entity model.