Results for “related_entity_id”

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

Overview

OKE_K_RELATED_ENTITIES is a transactional table within the OKE – Project Contracts module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It functions as the "Related Entity" table, capturing the associations between contract headers (K_HEADERS) and the change requests (OKE_CHG_REQUESTS) with which they are affiliated, together with version tracking. In the contract authoring and change-management lifecycle, this table records which related contract entities participate in a given change request and at what version, enabling downstream processes to reconcile contract terms against approved amendments.

Heuristically mined from its foreign key structure, this object classifies as a link table in a Data Vault modeling sense. It resolves a many-to-many-style relationship between contract headers and change requests via its key columns, rather than serving as a descriptive satellite or a core hub.

Key Information Stored

Because this is a link-style table, its columns are dominated by keys and audit metadata rather than descriptive attributes. The most significant columns include:

• K_HEADER_ID — Foreign key to OKE_K_HEADERS; identifies the contract header participating in the relationship.
• RELATED_ENTITY_ID — Also foreign keyed to OKE_K_HEADERS; identifies the related contract entity associated with the header.
• CHG_REQUEST_ID — Foreign key to OKE_CHG_REQUESTS; ties the related-entity association to a specific change request. Note the presence of both CHANGE_REQUEST_ID and CHG_REQUEST_ID among the documented columns.
• RELATED_ENTITY_VERSION — Tracks the version of the related entity at the time of association.
• VERSION — Version identifier for the row/record itself.
• CREATION_DATE, CREATED_BY — Standard "who/when created" audit columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "who/when last modified" audit columns.

The unique index OKE_K_RELATED_ENTITIES_UK01 (also documented as U1) is a business-key candidate on the combination K_HEADER_ID, CHG_REQUEST_ID, RELATED_ENTITY_ID, RELATED_ENTITY_VERSION. This composite key reflects the link's grain: one row per header, change request, related entity, and version. No separate surrogate single-column primary key is documented; the composite unique index serves as the identifying key.

Common Use Cases and Queries

Typical usage centers on contract-change reporting and traceability. Common scenarios include:

• Listing all related entities tied to a specific change request.
• Identifying all change requests that affected a given contract header.
• Reconstructing entity versions for audit and reconciliation against approved amendments.

A representative join pattern:

SELECT h.K_HEADER_ID, r.RELATED_ENTITY_ID, r.RELATED_ENTITY_VERSION, c.CHG_REQUEST_ID
FROM OKE_K_RELATED_ENTITIES r
JOIN OKE_K_HEADERS h ON r.K_HEADER_ID = h.K_HEADER_ID
JOIN OKE_CHG_REQUESTS c ON r.CHG_REQUEST_ID = c.CHG_REQUEST_ID
WHERE r.CHG_REQUEST_ID = :p_change_request_id;

Reporting use cases include version-drift analysis (comparing RELATED_ENTITY_VERSION across rows) and change-history extracts for contract audit packs.

Related Objects

The most significant dependent and referenced objects are:

• OKE_K_HEADERS — Referenced twice via K_HEADER_ID and RELATED_ENTITY_ID; supplies the contract header and related entity definitions.
• OKE_CHG_REQUESTS — Referenced via CHG_REQUEST_ID; supplies change-request context.
• OKE_K_RELATED_ENTITIES_UK01 / U1 — The unique business-key index enforcing the composite grain.
• Project Contracts (OKE) concurrent programs and contract authoring forms — Consume and maintain the related-entity associations surfaced by this table.

Because both foreign keys to OKE_K_HEADERS originate from the same table, ad-hoc queries must alias OKE_K_HEADERS carefully to avoid ambiguous column resolution.