Results for “insert_update_flag”

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

Overview

OKE_K_FUND_ALLOCATIONS is the contract funding allocation table within the Oracle E-Business Suite Project Contracts (OKE) module. It stores the distribution of funding across contract lines, projects, tasks, and funding sources, forming the transactional backbone that controls how much money is authorized against a given contract or project agreement. Each row represents a single allocation of an amount from a funding source to an object (contract line, project, or task), together with the hard-limit, revenue, and currency-conversion attributes that govern whether expenditures and revenue may be charged against it.

The object is owned by the OKE schema and is classified as VALID in both 12.1.1 and 12.2.2. The documented physical schema in ETRM 12.2.2 contains 59 columns. Applying a heuristic Data Vault classification, the foreign-key pattern (references outward to OKE_K_LINES, OKE_K_FUNDING_SOURCES, PA_PROJECTS_ALL, and PA_TASKS while being referenced only by its own history table) is satellite-leaning: it behaves as a descriptive, attribute-rich child record hanging off multiple business entities rather than as an independent hub or a pure intersection link. This classification is a modeling suggestion, not an Oracle-designated label.

Key Information Stored

The surrogate primary key is FUND_ALLOCATION_ID, defined by the constraint OKE_K_FUND_ALLOCATIONS_PK and reinforced by the unique index OKE_K_FUND_ALLOCATIONS_U1. Because no natural business key is separately documented as unique, FUND_ALLOCATION_ID is the reliable identifier for joins and references. The columns of greatest functional significance are:

• FUNDING_SOURCE_ID — foreign key to OKE_K_FUNDING_SOURCES, identifying the source of authorized funds.
• K_LINE_ID — foreign key to OKE_K_LINES, tying the allocation to a specific contract line.
• PROJECT_ID and TASK_ID — foreign keys to PA_PROJECTS_ALL and PA_TASKS, mapping the allocation to the project and task structure.
• AMOUNT and PREVIOUS_AMOUNT — the current and prior allocated amounts, supporting change tracking.
• HARD_LIMIT and REVENUE_HARD_LIMIT — caps that restrict expenditure and revenue charging against the allocation.
• PA_CONVERSION_TYPE, PA_CONVERSION_DATE, and PA_CONVERSION_RATE — currency conversion attributes, with PA_CONVERSION_TYPE referencing GL_DAILY_CONVERSION_TYPES.
• FUND_TYPE, FUNDING_STATUS, and FUNDING_CATEGORY — classification and lifecycle state of the allocation.
• OBJECT_ID — the identifier of the underlying object the allocation is applied to.
• START_DATE_ACTIVE, END_DATE_ACTIVE, and FISCAL_YEAR — effective-dating and period context.
• AGREEMENT_VERSION, CREATED_IN_VERSION, UPDATED_IN_VERSION, and INSERT_UPDATE_FLAG — versioning and change-propagation controls.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY, and the PA_ATTRIBUTE series — descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include funding-status reporting, remaining-funds analysis, hard-limit validation, and reconciliation of contract allocations to project budgets. A representative query joins the allocation to its funding source and project:

SELECT fa.FUND_ALLOCATION_ID,
       fs.NAME              funding_source,
       fa.PROJECT_ID,
       fa.TASK_ID,
       fa.AMOUNT,
       fa.FUNDING_STATUS,
       fa.HARD_LIMIT
FROM   OKE.OKE_K_FUND_ALLOCATIONS fa,
       OKE.OKE_K_FUNDING_SOURCES fs
WHERE  fa.FUNDING_SOURCE_ID = fs.FUNDING_SOURCE_ID
AND    fa.PROJECT_ID = :p_project_id;

Additional scenarios include identifying allocations exceeding a hard limit, tracing allocations back to contract lines via K_LINE_ID, and comparing AMOUNT against PREVIOUS_AMOUNT to detect revisions. Because history is retained in OKE_K_FUND_ALLOCATIONS_H, audit queries should union the base and history tables where prior states are required.

Related Objects

The most significant related objects, based on documented FK relationships, are:

• OKE_K_FUNDING_SOURCES — joined on FUNDING_SOURCE_ID; provides the funding authorization.
• OKE_K_LINES — joined on K_LINE_ID; the contract line receiving the allocation.
• PA_PROJECTS_ALL — joined on PROJECT_ID; the project context.
• PA_TASKS — joined on TASK_ID; the task context.
• GL_DAILY_CONVERSION_TYPES — joined on PA_CONVERSION_TYPE; currency conversion definitions.
• OKE_K_FUND_ALLOCATIONS_H — the history table, linked by FUND_ALLOCATION_ID, capturing prior versions of allocation rows.

These relationships make OKE_K_FUND_ALLOCATIONS the central point where contract funding, project structure, and currency conversion converge, and any integration or reporting effort should treat it as such.