Search Results oke_k_funding_sources




Overview

The OKE_K_FUNDING_SOURCES table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as the master repository for all funding sources associated with project contracts. In the context of contract management, a funding source represents the financial origin—such as a customer, internal budget, or grant—from which contract revenue is authorized and drawn. This table is essential for tracking the financial commitments and allocations tied to a contract, enabling detailed revenue planning, billing, and fund utilization analysis. Its integrity is critical for the financial controls and reporting within the OKE module.

Key Information Stored

The table's primary key is FUNDING_SOURCE_ID, a unique system-generated identifier. Based on the documented foreign key relationships, other significant columns include POOL_PARTY_ID, which links to a party in OKE_POOL_PARTIES, likely representing a funding pool or group. The AGREEMENT_NUMBER references a specific funding agreement in PA_AGREEMENTS_ALL. The K_PARTY_ID column holds the identifier for the funding party (e.g., customer or organization) from HZ_PARTIES. Financial attributes include CURRENCY_CODE (linked to FND_CURRENCIES) and K_CONVERSION_TYPE (linked to GL_DAILY_CONVERSION_TYPES), which define the monetary denomination and exchange rate type for the funding source, respectively. These columns collectively define the contractual, party, and financial dimensions of a funding source.

Common Use Cases and Queries

A primary use case is generating reports on available funding for a contract or project. Financial controllers may run queries to monitor committed versus utilized funds. A typical query might join OKE_K_FUNDING_SOURCES with OKE_K_FUND_ALLOCATIONS to summarize total allocated amounts per source. For auditing purposes, one might join with OKE_K_FUNDING_SOURCES_H (the history table) to track changes over time. When processing invoices or revenue, the system references this table to validate that sufficient funding exists and to determine the correct billing party and currency. Sample SQL to list funding sources for a specific contract party would filter on K_PARTY_ID and potentially join with HZ_PARTIES to retrieve the party name.

Related Objects

The OKE_K_FUNDING_SOURCES table has defined relationships with several key EBS objects, as per the provided metadata. It is referenced as a parent table by:

  • OKE_K_COMMUNICATIONS via FUNDING_SOURCE_ID, linking funding to contract communications.
  • OKE_K_FUNDING_SOURCES_H via FUNDING_SOURCE_ID, maintaining a history of changes.
  • OKE_K_FUND_ALLOCATIONS via FUNDING_SOURCE_ID, which is a critical relationship for tracking how funding is distributed to contract deliverables or lines.
It references (has foreign keys to) the following tables:
  • OKE_POOL_PARTIES via POOL_PARTY_ID.
  • PA_AGREEMENTS_ALL via AGREEMENT_NUMBER.
  • FND_CURRENCIES via CURRENCY_CODE.
  • HZ_PARTIES via K_PARTY_ID.
  • GL_DAILY_CONVERSION_TYPES via K_CONVERSION_TYPE.
These relationships integrate contract funding with Projects (PA), Trading Community Architecture (HZ), and General Ledger (GL) modules.