Results for “okr_party_roles”

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

Overview

OKR_PARTY_ROLES is a configuration table within the Oracle E-Business Suite Contracts for Rights (OKR) module, a component historically associated with rights management and intellectual property licensing. The table defines which party roles are valid for a given property type, forming a validation and reference layer that constrains the relationship between intellectual property (IP) types and the roles that counterparties may assume on those properties. In Oracle EBS 12.1.1 and 12.2.2, the OKR product family is classified as obsolete, meaning it is not shipped or supported in new implementations but may persist in upgraded environments where historical rights management data exists. The ETRM metadata explicitly states that this table is "Not implemented in this database," indicating it may be absent from typical installations.

From a data modeling perspective, the heuristic Data Vault classification for OKR_PARTY_ROLES is satellite-leaning. This suggests the table behaves as a descriptive, attribute-bearing structure attached to a parent hub or link rather than serving as an independent hub of business keys. In Data Vault terms, it would most naturally be modeled as a satellite of the property type hub, capturing the valid role assignments as contextual attributes.

Key Information Stored

The table's documented structure is intentionally narrow, consistent with a reference or validation table. Key columns include:

• ID — The surrogate primary key, defined by the OKR_PPE_PK constraint. This is a system-generated identifier that uniquely distinguishes each row and is not a business key.
• IP_TYPE — The intellectual property or property type code. This column participates in a foreign key relationship with OKR_PROP_TYPES_B and serves as a business-key component that links role definitions to specific property categories.

The combination of IP_TYPE and role information (referenced through OKR_IP_PARTY_RELS_B.IP_TYPE and ROLE_CODE) effectively constitutes the business-key candidate for this table, even though the documented primary key is the surrogate ID. The table does not carry the full role definition; instead, it references role codes maintained in OKR_IP_PARTY_RELS_B. This separation reflects a normalized design where role master data and role-to-property-type assignments are stored independently.

Common Use Cases and Queries

Although obsolete, this table is relevant during data migration, archival analysis, and audit of legacy rights management environments. A common query pattern validates which roles are permitted for a given IP type:

• Joining OKR_PARTY_ROLES to OKR_PROP_TYPES_B on IP_TYPE to list valid roles per property type.
• Joining OKR_PARTY_ROLES to OKR_IP_PARTY_RELS_B on both IP_TYPE and ROLE_CODE to retrieve role descriptions alongside their assignments.
• Reporting on orphaned role assignments where an IP type no longer exists in OKR_PROP_TYPES_B.

A representative SQL pattern is:

SELECT pr.ID, pr.IP_TYPE, rel.ROLE_CODE FROM OKR_PARTY_ROLES pr, OKR_IP_PARTY_RELS_B rel WHERE pr.IP_TYPE = rel.IP_TYPE;

Such queries support impact analysis prior to decommissioning legacy OKR objects.

Related Objects

The following objects have documented relationships with OKR_PARTY_ROLES:

• OKR_PROP_TYPES_B — Referenced by OKR_PARTY_ROLES.IP_TYPE; the parent definition of property types.
• OKR_IP_PARTY_RELS_B — References OKR_PARTY_ROLES via IP_TYPE, and shares the ROLE_CODE business attribute, supplying role master data.

Because OKR is obsolete and the table is not implemented in current databases, related reporting views and APIs are generally unavailable. Integration is therefore limited to legacy data extracts and migration scripts that map OKR party role assignments into successor rights or licensing systems.