Search Results funding_source_id




Overview
Explore in AI Chat

Overview

The OKE_K_FUNDING_SOURCES_H table is a critical history table within the Oracle E-Business Suite Project Contracts (OKE) module. It serves as the audit and versioning repository for changes made to contract funding sources. When a funding source record in the primary transactional table (OKE_K_FUNDING_SOURCES) is modified, a historical snapshot is created in this table. This design is essential for maintaining a complete audit trail, enabling compliance reporting, and supporting the analysis of funding arrangements over the lifecycle of a project contract. Its role is to preserve the state of funding source data at each major version, ensuring data integrity for financial and contractual reporting.

Key Information Stored

The table stores historical versions of funding source attributes. The composite primary key, consisting of FUNDING_SOURCE_ID and MAJOR_VERSION, uniquely identifies each historical snapshot. The FUNDING_SOURCE_ID column links the history record back to its master record in the OKE_K_FUNDING_SOURCES table. The MAJOR_VERSION column tracks the sequential version number of the change. A critical foreign key column is K_PARTY_ID, which historically stores the identifier for the funding party (e.g., customer, internal organization) as referenced in the HZ_PARTIES table. Other columns typically found in such history tables would include various descriptive fields for the funding source, creation date, last update date, and the identifier of the user who made the change, though these specific column names are not detailed in the provided excerpt.

Common Use Cases and Queries

Primary use cases revolve around auditing and historical analysis. Financial controllers may query this table to trace the evolution of funding commitments for a specific contract, while auditors use it to verify the change history of financial terms. A common reporting requirement is to generate a timeline of all changes for a given funding source. A sample SQL pattern to retrieve the full history, joining to the party table for descriptive information, would be:

  • SELECT h.FUNDING_SOURCE_ID, h.MAJOR_VERSION, h.K_PARTY_ID, p.PARTY_NAME, h.CREATION_DATE
  • FROM OKE.OKE_K_FUNDING_SOURCES_H h,
  • HZ_PARTIES p
  • WHERE h.K_PARTY_ID = p.PARTY_ID(+)
  • AND h.FUNDING_SOURCE_ID = :p_funding_source_id
  • ORDER BY h.MAJOR_VERSION;

This supports use cases such as understanding when a funding party was changed and by whom.

Related Objects

The table maintains defined foreign key relationships with two core tables, as documented in the metadata:

  • OKE_K_FUNDING_SOURCES: This is the primary transactional table. The relationship is established via the FUNDING_SOURCE_ID column in OKE_K_FUNDING_SOURCES_H, which references the primary key of OKE_K_FUNDING_SOURCES. This links every history record to its current master record.
  • HZ_PARTIES: This is the Trading Community Architecture (TCA) master table for parties. The relationship is through the K_PARTY_ID column in OKE_K_FUNDING_SOURCES_H, which references HZ_PARTIES.PARTY_ID. This join provides the name and details of the historical funding entity.

These relationships are fundamental for constructing accurate historical reports that combine funding source details with party information.