Search Results cc_smry_pf_func_amt




Overview
Explore in AI Chat

Overview

APPS.IGC_CC_SMRY_PF_VERSION_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Grants / Contracts (IGC) application family. In the ETRM metadata it is classified as a "supplementary view used to simplify forms coding," meaning that it exists primarily to support the Oracle Forms–based user interface rather than to serve as a general-purpose reporting object. Oracle explicitly warns that this view may change dramatically in subsequent minor or major releases and does not recommend that developers or integrators query or alter data through it directly. Despite that caution, the object remains documented and valid in both release 12.1.1 and 12.2.2, and its columns are commonly surfaced when users search for cost summary figures such as the functional amount field cc_smry_pf_func_amt.

The view presents summarized cost collection figures tied to a specific version of a cost budget or cost summary record. Its name components indicate a Cost Collection (CC) summary (SMRY) at the "PF" (project funding / period-funded) level, scoped to a particular version (VERSION_V). This makes it relevant to organizations that track burdened and unburdened cost totals across fiscal periods for sponsored projects and contract funding.

Underlying Base Objects

According to the documented view source, IGC_CC_SMRY_PF_VERSION_V is not defined over base tables directly. Instead, it is composed from other views and packages, reinforcing its role as a convenience layer for forms logic. The documented dependencies are:

  • IGC_CC_DET_PF_VERSION_V — a detail-level view supplying the granular period-funded cost collection records from which the summary is derived.
  • IGC_CC_PERIODS_V — a view providing the fiscal period and calendar context used to align amounts to fiscal years and periods.
  • IGC_CC_VERSION_VIEW_PKG — a PL/SQL package that encapsulates the version-aware query logic, ensuring the view returns data for the correct cost version.
  • FND_GLOBAL — the standard EBS package used to resolve session-level context such as the current organization (ORG_ID) and user environment.

Notably, the view is not referenced by any other database object, confirming that it is a terminal, presentation-oriented construct intended for form invocation rather than downstream reuse.

Key Columns

The view exposes six columns that together identify the record and carry the summarized monetary values:

  • CC_ACCT_LINE_ID (NUMBER) — the cost collection account line identifier, the primary key linking the summary to its source accounting line.
  • CC_FISCAL_YEAR (NUMBER) — the fiscal year to which the summarized amounts apply.
  • ORG_ID (NUMBER) — the organization identifier, enforcing multi-org security and partitioning of the data.
  • CC_SMRY_PF_ENT_AMT (NUMBER) — the entered amount for the period-funded summary.
  • CC_SMRY_PF_FUNC_AMT (NUMBER) — the functional (converted) amount for the period-funded summary, expressed in the functional currency. This is the field most commonly associated with user searches for cc_smry_pf_func_amt.
  • CC_SMRY_PF_ENCMBRNC_AMT (NUMBER) — the encumbrance amount recorded against the period-funded summary, useful for commitment tracking.

Common Use Cases and Queries

Because the view is forms-oriented, the most reliable supported usage is invoking it through the Oracle Forms UI in the cost collection and budget versioning screens. When direct querying is required for diagnostics or reporting, it should be treated as read-only and validated against the underlying detail views, especially before any upgrade. A representative query, consistent with the documented query text, is:

  • SELECT cc_acct_line_id, cc_fiscal_year, org_id, cc_smry_pf_ent_amt, cc_smry_pf_func_amt, cc_smry_pf_encmbrnc_amt FROM apps.igc_cc_smry_pf_version_v;
  • Filtering by fiscal year and organization, e.g. adding WHERE cc_fiscal_year = :year AND org_id = :org_id, to isolate a single entity's summarized functional and encumbrance totals.
  • Joining CC_ACCT_LINE_ID back to the detail view IGC_CC_DET_PF_VERSION_V for drill-down reconciliation between summary and detail amounts.

Given Oracle's explicit warning, integration architects should avoid embedding this view in permanent interfaces and instead derive the equivalent functional amount logic from documented base tables where stable interfaces are required.