Search Results fund_status




Overview
Explore in AI Chat

Overview

OKE_K_FUND_VERS_SUMMARY_V is an APPS-owned reporting view in Oracle E-Business Suite that presents aggregated funding information for Oracle Project Contracts (OKE) documents at the contract-version level. The view consolidates commitment and funding balances expressed in both the funding currency and the functional (K) currency, and it exposes all monetary columns as SUM() aggregates over a driving inline sub-query. This design allows the view to return one summarized row per combination of object type, object ID, major version, funding currency code, and up to three user-selected grouping attributes.

Its principal role is to power the Contract Funding Inquiry and funding status reporting functionality. The presence of the FUND_STATUS option in the DECODE logic, and of the FUNDING_STATUS_CODE column, confirms that the view is the source used when a user requests a funding inquiry grouped by fund status. It is therefore a presentation-layer object rather than a transactional table, intended for inquiry, reporting, and integration extracts rather than direct data maintenance.

Underlying Base Objects

The documented base objects are FND_LOOKUP_VALUES (SYNONYM), the OKE_FUNDING_INQUIRY package, OKE_K_FUNDING_SOURCES_V, OKE_K_FUND_ALLOCATIONS_HV, OKE_K_FUND_ALLOCATIONS_V, and OKE_K_VERS_NUMBERS_V. The inline sub-query aliases these as follows: S supplies the funding source rows (OBJECT_TYPE, OBJECT_ID, CURRENCY_CODE, FUNDING_PARTY, K_PARTY_ID), while A supplies the versioned allocation detail (MAJOR_VERSION, FUND_TYPE, FUNDING_STATUS, PROJECT, TASK, CONTRACT_LINE, FISCAL_YEAR, reference columns, and the corresponding code/ID columns). FND_LOOKUP_VALUES resolves the descriptive values for fund type and funding status, and OKE_K_VERS_NUMBERS_V provides the major version context.

The critical dependency is the OKE_FUNDING_INQUIRY package, whose global variables GROUP_BY1, GROUP_BY2, and GROUP_BY3 drive the DECODE expressions that dynamically label the grouping columns. Because these are package-level globals, the view must be queried in the context of an active funding inquiry session; the grouping attribute selected at runtime determines which underlying column populates each group-by slot.

Key Columns

  • OBJECT_TYPE, OBJECT_ID, MAJOR_VERSION — Identify the source contract or document and its version, forming the aggregate grain together with the currency and grouping columns.
  • FUNDING_CURRENCY_CODE — The currency of the funding source, inherited from S.CURRENCY_CODE.
  • GROUP_BY1, GROUP_BY2, GROUP_BY3 — Descriptive labels resolved dynamically; for example, when the inquiry groups by fund status, GROUP_BY1 returns A.FUNDING_STATUS via the 'FUND_STATUS' branch of the DECODE. Other supported values include FUND_TYPE, PROJECT, TASK, SOURCE, LINE, FISCAL, and REFERENCE1 through REFERENCE3.
  • GROUP_BY1_CODE, GROUP_BY2_CODE, GROUP_BY3_CODE — The corresponding identifier or code values, such as FUNDING_STATUS_CODE, used for drill-down and joins.
  • F_CURR_* columns — Initial amount, incremental amount, current amount, hard limit, and reverse hard limit expressed in the funding currency.
  • K_CURR_* columns — The same five measures converted to the functional currency.

Common Use Cases and Queries

The view is typically accessed after the funding inquiry package has set its grouping globals, or directly for reporting where the default grouping is acceptable.

  • Funding status summary by contract version, filtering to the fund-status grouping.
  • Currency exposure analysis across funding and functional currencies.
  • Hard-limit versus current-amount reconciliation for funds control reporting.
  • Integration extracts feeding downstream commitment or budget dashboards.

A representative query:

SELECT object_type, object_id, major_version, funding_currency_code,
  group_by1, group_by1_code,
  SUM(f_curr_amount), SUM(k_curr_amount),
  SUM(f_curr_hard_limit), SUM(k_curr_hard_limit)
FROM apps.oke_k_fund_vers_summary_v
WHERE group_by1_code = '&fund_status'
GROUP BY object_type, object_id, major_version, funding_currency_code, group_by1, group_by1_code
ORDER BY object_id, major_version;

Because all measures are already aggregated in the view definition, additional GROUP BY clauses are generally unnecessary unless the caller requires a coarser grain than the view supplies.