Results for “pa_conversion_date”

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

Overview

OKE_K_FUND_ALLOCATIONS_H is the contract funding allocations history table in the Oracle E-Business Suite Project Contracts (OKE) module. It stores the historical or versioned form of records held in OKE_K_FUND_ALLOCATIONS, preserving successive major versions of each funding allocation as contract terms, funding sources, and allocation amounts evolve over the life of an award. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the OKE schema and is marked VALID. Its documented description is "Contract Funding Allocations History."

The physical schema exposes 60 columns and two indexes: a composite primary key, OKE_K_FUND_ALLOC_H_PK, defined on (FUND_ALLOCATION_ID, MAJOR_VERSION), and a unique index, OKE_K_FUND_ALLOC_H_U1, on the same column pair. From a Data Vault modeling perspective, the FK structure mined from the relationships—references out to OKE_K_FUND_ALLOCATIONS, OKE_K_FUNDING_SOURCES, and OKE_K_LINES—suggests a satellite-leaning classification, where the history table augments a parent allocation entity across successive major versions rather than acting as a pure hub or link.

Key Information Stored

The surrogate/business key is the combination of FUND_ALLOCATION_ID and MAJOR_VERSION, which also forms the documented unique index. FUND_ALLOCATION_ID is the foreign key tying the historical row back to the live allocation in OKE_K_FUND_ALLOCATIONS, while MAJOR_VERSION distinguishes each retained version of that allocation. The functional columns describe the funding relationship itself: FUNDING_SOURCE_ID identifies the funding source drawn upon, K_LINE_ID links the allocation to a contract line, and OBJECT_ID, PROJECT_ID, and TASK_ID anchor the allocation to its project and task context. AMOUNT and PREVIOUS_AMOUNT capture the current and prior allocation values, while HARD_LIMIT and REVENUE_HARD_LIMIT define the ceiling against which funding is validated. PA_CONVERSION_TYPE, PA_CONVERSION_DATE, and PA_CONVERSION_RATE support currency conversion into Projects accounting. FUND_TYPE, FUNDING_STATUS, and FUNDING_CATEGORY classify and control the allocation state, and START_DATE_ACTIVE and END_DATE_ACTIVE bound its effective period. The remaining columns include standard audit attributes.

Common Use Cases and Queries

The primary usage is version comparison: reconstructing how a contract's funded amount and hard limit changed across major versions. A typical reporting query joins the history table to the current allocation and to the funding source, filtered by MAJOR_VERSION ordering:

• Version history of a single allocation: SELECT fund_allocation_id, major_version, amount, previous_amount, hard_limit, funding_status FROM oke_k_fund_allocations_h WHERE fund_allocation_id = :id ORDER BY major_version.
• Funding source usage across projects: join FUNDING_SOURCE_ID to OKE_K_FUNDING_SOURCES to report allocations by source and category.
• Audit and compliance inquiries into who changed funding status and when, using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
• Effective-dated funding analysis using START_DATE_ACTIVE and END_DATE_ACTIVE to determine which allocation version was in force on a given date.
• Conversion reconciliation using PA_CONVERSION_TYPE, PA_CONVERSION_DATE, and PA_CONVERSION_RATE.

Related Objects

The table participates in a small but tightly coupled set of relationships within the OKE schema:

• OKE_K_FUND_ALLOCATIONS — referenced through FUND_ALLOCATION_ID; the current-version parent from which historical rows are derived.
• OKE_K_FUNDING_SOURCES — referenced through FUNDING_SOURCE_ID; supplies the funding source definition behind each allocation.
• OKE_K_LINES — referenced through K_LINE_ID; identifies the contract line funded by the allocation.
• OKE_K_FUND_ALLOC_H_PK and OKE_K_FUND_ALLOC_H_U1 — the primary and unique indexes defined on FUND_ALLOCATION_ID and MAJOR_VERSION.
• FUNDING_CATEGORY and FUND_TYPE value sets — used to validate and report allocation classifications.