Search Results oke_k_related_entities




Overview
Explore in AI Chat

Overview

The OKE_K_RELATED_ENTITIES table is a core data object within the Oracle E-Business Suite Project Contracts (OKE) module. It functions as a relationship mapping table, formally documenting associations between a primary contract and other related business entities. Its primary role is to establish and maintain formal links, which are critical for managing contract hierarchies, tracking dependencies, and supporting change management processes. The table's design, which includes foreign key references to both contract headers and change requests, indicates its integral function in the contract lifecycle, ensuring that relationships are properly versioned and auditable, particularly when modifications are processed through formal change orders.

Key Information Stored

The table's structure is defined by a composite primary key and several foreign keys, emphasizing the uniqueness of each relationship record. The key columns are:

  • K_HEADER_ID: The unique identifier for the primary contract (Project Agreement) from the OKE_K_HEADERS table.
  • RELATED_ENTITY_ID: The identifier for the associated business entity, which also references the OKE_K_HEADERS table, indicating the related entity is typically another contract.
  • RELATED_ENTITY_VERSION: A version number for the related entity, allowing the system to track which specific iteration of that entity the relationship is tied to.
  • CHG_REQUEST_ID: A link to the OKE_CHG_REQUESTS table, signifying that the creation or modification of this relationship record may be tied to a formal contract change request process.

Common Use Cases and Queries

This table is essential for reporting and operational queries that require an understanding of contract interdependencies. A common use case is generating a report of all contracts related to a master agreement or identifying sub-contracts linked to a prime contract. For audit purposes, queries often join this table with change requests to trace when specific relationships were established or modified. A typical SQL pattern retrieves the related contract details for a given header ID:

SELECT rel.k_header_id, rel.related_entity_id, rel.related_entity_version, hdr.contract_number
FROM oke_k_related_entities rel, oke_k_headers hdr
WHERE rel.related_entity_id = hdr.k_header_id
AND rel.k_header_id = :p_contract_id;

Another critical scenario involves change management reporting, where queries join OKE_K_RELATED_ENTITIES, OKE_K_HEADERS, and OKE_CHG_REQUESTS to analyze the impact of a specific change order on contract relationships.

Related Objects

The OKE_K_RELATED_ENTITIES table maintains documented foreign key relationships with two other central OKE tables, forming a critical part of the data model.

  • OKE_K_HEADERS: The table has two distinct foreign key relationships with this master contract table.
    • Via K_HEADER_ID: Links the relationship record to the primary contract.
    • Via RELATED_ENTITY_ID: Links the relationship record to the associated contract entity.
  • OKE_CHG_REQUESTS: The table is linked via CHG_REQUEST_ID, connecting the establishment or update of a relationship to a formal change management process.

These relationships confirm the table's purpose in managing versioned, auditable links between contracts within a structured change control framework.