Search Results oke_k_deliverables_bh




Overview
Explore in AI Chat

Overview

The OKE_K_DELIVERABLES_BH table is a core historical data repository within the Oracle E-Business Suite Project Contracts (OKE) module. It serves the critical function of maintaining a complete, auditable history of changes made to contract deliverable definitions. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is essential for tracking the evolution of deliverables—such as reports, milestones, or physical goods—associated with project contracts over their lifecycle. Its role is to preserve every major version of a deliverable's attributes, enabling compliance, audit reporting, and the ability to review the state of a contract at any point in historical time. This historical tracking is a fundamental principle in contract management systems to ensure non-repudiation and accurate historical reporting.

Key Information Stored

The table stores snapshots of deliverable records keyed by a composite primary key. The most critical columns include DELIVERABLE_ID, which uniquely identifies the specific deliverable across all versions, and MAJOR_VERSION, which denotes the historical snapshot or iteration of that deliverable. Together, these columns form the primary key (OKE_K_DELIVERABLES_BH_PK). While the full column list is not detailed in the provided metadata, a historical table of this nature typically contains all columns present in its corresponding current business table (often OKE_K_DELIVERABLES_B), plus versioning metadata. This would include deliverable details like name, description, type, associated contract header, due dates, completion status, and the system-generated audit information (e.g., creation date, last update date, who updated it) relevant to each major version.

Common Use Cases and Queries

Primary use cases revolve around audit trails, historical analysis, and regulatory compliance reporting. A common requirement is to retrieve the complete version history of a specific deliverable or to reconstruct the state of all deliverables for a contract as of a past date. For example, to audit changes to a deliverable, one might query:

  • SELECT * FROM OKE.OKE_K_DELIVERABLES_BH WHERE DELIVERABLE_ID = :p_deliverable_id ORDER BY MAJOR_VERSION DESC;

For reporting on deliverable status history linked to a contract, a join to the contract headers history table would be necessary. Another critical use case is supporting the standard Oracle EBS "View History" functionality from the Contract Deliverables form, where this table serves as the direct data source for the presented historical information.

Related Objects

The table maintains defined foreign key relationships, indicating its integration within the Project Contracts historical schema. Based on the provided metadata:

  • OKE_K_STANDARD_NOTES_BH: This historical table for standard notes references OKE_K_DELIVERABLES_BH. The foreign key is established on the composite columns (DELIVERABLE_ID, MAJOR_VERSION), meaning historical notes are linked to specific historical versions of deliverables. A typical join would be: ... FROM OKE_K_DELIVERABLES_BH dh JOIN OKE_K_STANDARD_NOTES_BH nh ON dh.DELIVERABLE_ID = nh.DELIVERABLE_ID AND dh.MAJOR_VERSION = nh.MAJOR_VERSION.

Logically, this table also has a strong relationship with the main transactional table for deliverables (presumably OKE_K_DELIVERABLES_B or similar), from which historical rows are generated. It is also commonly referenced in custom historical reports alongside other contract history tables like OKE_K_HEADERS_BH for a complete historical contract view.