Results for “oke_k_fund_vers_summary_v”

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

Overview

OKE_K_FUND_VERS_SUMMARY_V is a reporting view in the APPS schema belonging to the OKE - Project Contracts product family. Its documented description is "Funding allocation summary by version view." The view aggregates funding allocation amounts across two currency representations for a given contract, funding source, and contract version, exposing both a funding currency (prefixed F_CURR_) and a functional or "K" currency (prefixed K_CURR_) set of amounts. It is intended to support funding inquiry and reporting screens rather than transactional processing, and therefore acts as a read-only presentation layer over the underlying funding allocation data.

In Oracle EBS 12.1.1 and 12.2.2 the view remains a VALID object in the APPS schema. It is commonly invoked when the end user searches on fund_status, since the view is the layer that resolves grouping selections such as FUND_STATUS into display values and codes via lookup decoding.

Underlying Base Objects

The view is defined over the following documented base objects, which are listed as referenced objects in the ETRM metadata:

• OKE_K_FUND_ALLOCATIONS_V and OKE_K_FUND_ALLOCATIONS_HV — the primary allocation views supplying the F_CURR and K_CURR amount columns that are summed in the outer query.
• OKE_K_FUNDING_SOURCES_V — provides the funding source attributes, notably OBJECT_TYPE, OBJECT_ID, and the funding party (FUNDING_PARTY, K_PARTY_ID).
• OKE_K_VERS_NUMBERS_V — supplies MAJOR_VERSION, enabling the summary to be broken out by contract version.
• OKE_FUNDING_INQUIRY (PACKAGE) — provides the runtime grouping directives GROUP_BY1, GROUP_BY2, and GROUP_BY3 referenced inside the DECODE expressions.
• FND_LOOKUP_VALUES (SYNONYM) — the standard EBS lookup view used to translate lookup codes into meaningful display values.

The view references these objects through an inline query and applies DECODE logic to map USER-selected grouping tokens to concrete columns, then aggregates with SUM().

Key Columns

• OBJECT_TYPE / OBJECT_ID — identify the owning entity (for example a contract) being reported.
• MAJOR_VERSION — the contract version the allocation belongs to.
• FUNDING_CURRENCY_CODE — the currency of the underlying funding allocation.
• GROUP_BY1, GROUP_BY2, GROUP_BY3 — the display values chosen at runtime (for example FUND_TYPE, FUND_STATUS, PROJECT, TASK, SOURCE, LINE, FISCAL).
• GROUP_BY1_CODE, GROUP_BY2_CODE, GROUP_BY3_CODE — the corresponding internal codes/IDs for each grouping, matching the display column.
• F_CURR_INIT_AMOUNT, F_CURR_INCR_AMOUNT, F_CURR_AMOUNT, F_CURR_HARD_LIMIT, F_CURR_REV_HARD_LIMIT — funding-currency initial, incremental, current, hard-limit, and revised hard-limit amounts.
• K_CURR_INIT_AMOUNT, K_CURR_INCR_AMOUNT, K_CURR_AMOUNT, K_CURR_HARD_LIMIT, K_CURR_REV_HARD_LIMIT — the equivalent amounts in the functional/K currency.

For searches on fund_status, the relevant columns are GROUP_BY1/GROUP_BY1_CODE and GROUP_BY2/GROUP_BY2_CODE, which resolve to the funding status display value and its code through the DECODE on A.FUNDING_STATUS and A.FUNDING_STATUS_CODE.

Common Use Cases and Queries

The view is most useful for reporting total allocated funding grouped by status or version. A representative query filtering on funding status via the grouping columns follows:

SELECT major_version,
       group_by1,
       group_by1_code,
       funding_currency_code,
       SUM(f_curr_amount)     f_curr_amount,
       SUM(k_curr_amount)     k_curr_amount
FROM   apps.oke_k_fund_vers_summary_v
WHERE  group_by1_code = :fund_status_code
GROUP  BY major_version, group_by1, group_by1_code, funding_currency_code;

Other common usages include:

• Displaying a funding allocation summary by contract version for a specific project or task (group by PROJECT or TASK).
• Comparing hard limit versus revised hard limit totals in both currency views to assess committed versus available funding.
• Feeding funding inquiry dashboard regions where the grouping is user-selectable, relying on OKE_FUNDING_INQUIRY to determine GROUP_BY1/2/3 at runtime.