Search Results group_by1_code

Overview

OKE_K_FUNDING_SUMMARY_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Project Contracts (OKE) module. It is documented as valid in ETRM 12.1.1 and 12.2.2, and its stated purpose is to present a funding allocation summary. The view consolidates funding figures across multiple grouping dimensions — object type, object identifier, funding currency code, and three generic group-by attributes — producing a single aggregated row per unique combination of those keys. It retains the maximum major version of the underlying funding versions while summing monetary amounts across the aggregated set. The view is typically consumed by funding inquiry screens and by downstream reporting or integration logic that requires summarized hard-limit and revised hard-limit figures, including the F_CURR_REV_HARD_LIMIT column that prompted its inspection. Because it aggregates rather than exposes line-level detail, it is well suited to display-only inquiry, summary reporting, and lightweight integration extracts rather than as a transactional source of record.

Underlying Base Objects

The view is defined over OKE_K_FUND_VERS_SUMMARY_V, which is itself a summary view within the OKE funding stack. OKE_K_FUNDING_SUMMARY_V does not directly reference a base table; it inherits the funding, version, and currency semantics already resolved by OKE_K_FUND_VERS_SUMMARY_V and then re-aggregates them. The documented referenced objects for this view are the OKE_FUNDING_INQUIRY package and OKE_K_FUND_VERS_SUMMARY_V. The OKE_FUNDING_INQUIRY package supplies the funding inquiry transactional logic that generates and retrieves the summary data presented in the Project Contracts funding inquiry user interface, while OKE_K_FUND_VERS_SUMMARY_V provides the version-level and currency-level rows that this view rolls up. The relationship is strictly read-only: the view performs no DML and depends on the underlying summary view for both amount and version information.

Key Columns

• OBJECT_TYPE / OBJECT_ID — Identify the funding source object being summarized.
• MAJOR_VERSION — The maximum major version number across the aggregated rows, indicating the latest published version represented.
• FUNDING_CURRENCY_CODE — The currency in which all summarized amounts are expressed.
• GROUP_BY1 / GROUP_BY1_CODE, GROUP_BY2 / GROUP_BY2_CODE, GROUP_BY3 / GROUP_BY3_CODE — Paired display name and code columns that define the aggregation grouping dimensions.
• F_CURR_INIT_AMOUNT, F_CURR_INCR_AMOUNT, F_CURR_AMOUNT — Initial, incremental, and total funding amounts in functional currency.
• F_CURR_HARD_LIMIT, F_CURR_REV_HARD_LIMIT — Functional-currency hard limit and revised hard limit, summed across the group. F_CURR_REV_HARD_LIMIT reflects revised hard-limit values after changes.
• K_CURR_INIT_AMOUNT, K_CURR_INCR_AMOUNT, K_CURR_AMOUNT — Initial, incremental, and total funding amounts in the funding currency.
• K_CURR_HARD_LIMIT, K_CURR_REV_HARD_LIMIT — Funding-currency hard limit and revised hard limit.

Common Use Cases and Queries

The view supports funding inquiry reports, hard-limit utilization checks, and cross-currency reconciliation between functional and funding currency amounts. The following query retrieves summarized funding for a given object:

SELECT object_type, object_id, funding_currency_code, MAX(major_version),
  SUM(f_curr_amount), SUM(f_curr_hard_limit), SUM(f_curr_rev_hard_limit)
FROM apps.oke_k_funding_summary_v
WHERE object_id = :p_object_id
GROUP BY object_type, object_id, funding_currency_code;

To compare total funding against revised hard limits by grouping dimension:

SELECT group_by1_code, group_by2_code, funding_currency_code,
  SUM(k_curr_amount) total_funding,
  SUM(k_curr_hard_limit) hard_limit,
  SUM(k_curr_rev_hard_limit) revised_hard_limit
FROM apps.oke_k_funding_summary_v
GROUP BY group_by1_code, group_by2_code, funding_currency_code;

Because the view already applies aggregation, avoid joining it to detail-level funding tables unless the join keys (OBJECT_TYPE, OBJECT_ID, FUNDING_CURRENCY_CODE, and the GROUP_BY codes) are correctly matched to prevent row multiplication. All access should be treated as read-only, and results reflect the maximum major version available in the underlying summary view at query time.