Search Results fund_allocation_id




Overview
Explore in AI Chat

Overview

The OKE_K_FUND_ALLOCATIONS_H table is a history table within the Oracle E-Business Suite Project Contracts (OKE) module. Its primary role is to maintain a historical record of changes made to contract funding allocation records. In the context of contract management, funding allocations define how monetary funds from a funding source are distributed and committed against specific contract deliverables, work breakdown structures, or periods. This table captures the versioned state of these allocations, enabling audit trails, compliance reporting, and the analysis of funding changes over time. It is integral to the financial governance and historical tracking capabilities of the Project Contracts application.

Key Information Stored

The table stores historical snapshots of funding allocation records. The primary key is a composite key consisting of FUND_ALLOCATION_ID and MAJOR_VERSION, which uniquely identifies each historical version of a funding allocation. The FUND_ALLOCATION_ID column is the unique identifier that links all historical versions back to the current, active record in the base table, OKE_K_FUND_ALLOCATIONS. The MAJOR_VERSION column tracks the sequential version number for each change. While the provided metadata does not list all columns, typical data stored in such a history table would include the complete set of allocation attributes (e.g., allocated amount, status, date ranges, project or task associations) as they existed at the time the version was created, along with system who columns (CREATED_BY, CREATION_DATE) to record the audit information for each change.

Common Use Cases and Queries

This table is primarily used for auditing and historical analysis. A common scenario involves tracing the evolution of a specific funding allocation to understand how its committed amount or other attributes have been amended over the life of a contract. Financial controllers may query this table to generate reports for internal audits or regulatory compliance, demonstrating the complete change history of contract funding. A typical query pattern retrieves all historical versions for a given allocation, ordered to show the progression of changes.

SELECT fund_allocation_id, major_version, allocated_amount, creation_date
FROM oke_k_fund_allocations_h
WHERE fund_allocation_id = :p_alloc_id
ORDER BY major_version;

Another use case is comparative reporting, where the state of allocations at different fiscal period-ends is compared by querying the version active as of a specific date.

Related Objects

The table has a direct and documented foreign key relationship with the base transactional table, OKE_K_FUND_ALLOCATIONS. This relationship is fundamental to its purpose.

  • OKE_K_FUND_ALLOCATIONS: This is the primary transactional table holding the current, active version of each funding allocation record. The foreign key constraint from OKE_K_FUND_ALLOCATIONS_H.FUND_ALLOCATION_ID to OKE_K_FUND_ALLOCATIONS ensures referential integrity, linking every historical version to its source record. All historical entries for a given allocation share the same FUND_ALLOCATION_ID value as the active record in this base table.