Results for “oke_k_fund_allocations_v”

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

Overview

OKE_K_FUND_ALLOCATIONS_V is an APPS-owned database view within the OKE – Project Contracts module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents contract funding source allocation information, consolidating allocation records held in the OKE_K_FUND_ALLOCATIONS base table with descriptive attributes drawn from contract lines, projects, tasks, currencies, and lookup values. The view functions as a denormalized reporting and integration layer: rather than requiring consumers to join the fund allocation table to a half-dozen supporting entities, the view surfaces a single, query-ready result set that includes line numbers, item descriptions, project and task identifiers, monetary amounts, funding status and type meanings, currency conversion details, and the full descriptive flexfield (DFF) attribute columns inherited from the base table.

Because it carries the version number of the contract and the version in which a record was created or updated, the view is well suited to contract versioning analysis, funding reconciliation, and external interfaces that must extract allocation data tied to a specific contract version. It is defined under the APPS schema, so it is normally accessed by application users or reporting tools connected with APPS privileges rather than through a custom schema.

Underlying Base Objects

The view is defined over a combination of core contract and project tables, joined predominantly with outer joins so that allocations survive even when optional descriptive data is absent. The documented base objects are:

• OKE_K_FUND_ALLOCATIONS – the driving table containing the funding allocation records themselves, including amounts, limits, statuses, and attributes.
• OKC_K_LINES_B and OKC_K_LINES_TL – the contract line base and translation tables, supplying line numbers, dates, and item descriptions (the translation join is language-restricted via USERENV('LANG')).
• PA_PROJECTS_ALL and PA_TASKS – Oracle Projects entities providing the project segment and task number, plus project currency and billing attributes.
• OKE_K_VERS_NUMBERS_V – a supporting view supplying the major version of the contract.
• FND_LOOKUP_VALUES – joined three times (aliases LV1, LV2, LV3) to resolve the meanings for funding status, fund type, and funding category lookups, restricted to VIEW_APPLICATION_ID 777.
• GL_DAILY_CONVERSION_TYPES – resolves the user-facing name of the currency conversion type.

Key Columns

The view exposes the primary key and foreign keys FUND_ALLOCATION_ID, FUNDING_SOURCE_ID, K_LINE_ID, OBJECT_ID, PROJECT_ID, and TASK_ID. Descriptive columns include LINE_NUMBER, ITEM_DESCRIPTION, SEGMENT1 (project number), TASK_NUMBER, and MAJOR_VERSION. Financial columns cover AMOUNT, PREVIOUS_AMOUNT, HARD_LIMIT, and REVENUE_HARD_LIMIT, alongside FUND_TYPE, FUNDING_STATUS, and FUNDING_CATEGORY with their resolved lookup MEANING values. Currency handling is represented by PA_CONVERSION_TYPE, USER_CONVERSION_TYPE, PA_CONVERSION_DATE, PA_CONVERSION_RATE, and project currency flags. Version tracking is provided through CREATED_IN_VERSION, UPDATED_IN_VERSION, and AGREEMENT_VERSION, while auditing columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE) and two sets of DFF attributes (standard ATTRIBUTE1–15 and PA_ATTRIBUTE1–10) complete the structure.

Common Use Cases and Queries

Typical scenarios include reconciling funded amounts against contract hard limits, reporting funding status by project or task, and extracting allocation data for interfaces or conversions. For example, to list active allocations by project with their funding status:

• SELECT fund_allocation_id, segment1, task_number, line_number, amount, hard_limit, funding_status, meaning, funding_category FROM oke_k_fund_allocations_v WHERE project_id = :p_project_id;
• SELECT k_line_id, major_version, fund_type, amount, start_date_active, end_date_active FROM oke_k_fund_allocations_v WHERE funding_status = 'ACTIVE' ORDER BY k_line_id, major_version;

Because the view resolves lookup meanings and currency conversion types, it eliminates repetitive joins in custom reports and is preferable to querying OKE_K_FUND_ALLOCATIONS directly whenever descriptive or project context is required.