Search Results cc_det_pf_line_id




Overview
Explore in AI Chat

Overview

IGC_CC_DET_PF_VERSION_V is a version-aware reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, delivered as part of the Oracle Grants / Contracts (IGC) Cost Collection and pre-formatted detail functionality. The view presents a flattened, de-normalised projection of cost-collection detail line rows (the CC_DET_PF family) resolved to a specific cost version. Its central purpose is to expose the effective detail line for a given version context, so that downstream reporting, reconciliation, commitment (encumbrance) analysis, and integrations see the correct historical or current version of a line rather than every stored version.

The version is determined at query time by the packaged function IGC_CC_VERSION_VIEW_PKG.GET_VERSION_NUM. Because the selection criteria are evaluated dynamically, the same view returns different logical rowsets depending on the version currently set in the session/application context. This makes it a convenient, stable interface for consumers that should not themselves implement the version-merge logic against the base and history tables.

Underlying Base Objects

The view is defined over the following documented objects:

  • IGC_CC_DET_PF (SYNONYM) — the current/active pre-formatted cost detail lines.
  • IGC_CC_DET_PF_HISTORY (SYNONYM) — historical and versioned copies of those lines, including the CC_DET_PF_VERSION_NUM and CC_DET_PF_VERSION_ACTION columns used for version resolution.
  • IGC_CC_VERSION_VIEW_PKG (PACKAGE) — provides GET_VERSION_NUM, the function that supplies the version threshold driving the view's filtering.

Structurally, the view is a UNION of two branches. The first branch selects from IGC_CC_DET_PF only those CC_DET_PF_LINE_ID values that do not appear in the relevant version slice of IGC_CC_DET_PF_HISTORY (i.e., the row is an unversioned/current line). The second branch selects the minimum version number greater than or equal to the requested version from IGC_CC_DET_PF_HISTORY, restricted to rows whose CC_DET_PF_VERSION_ACTION is not 'I' (insert), for each CC_DET_PF_LINE_ID. The union therefore yields exactly one effective row per line for the applied version context.

Key Columns

Common Use Cases and Queries

Typical use is version-accurate reconciliation and reporting. Analysts query the view instead of writing the union/version logic directly. Example:

  • SELECT CC_DET_PF_LINE_ID, CC_DET_PF_LINE_NUM, CC_DET_PF_FUNC_AMT, CC_DET_PF_ENCMBRNC_AMT FROM APPS.IGC_CC_DET_PF_VERSION_V WHERE CC_ACCT_LINE_ID = :p_acct_line_id;
  • Filtering on CC_DET_PF_ENCMBRNC_STATUS to report open commitments for the active version.
  • Joining on CC_DET_PF_LINE_ID or PARENT_DET_PF_LINE_ID to reconstruct line hierarchies for a chosen version.

Because results depend on IGC_CC_VERSION_VIEW_PKG.GET_VERSION_NUM, callers must ensure the intended version context is established before querying; otherwise the rowset reflects whatever version the package returns for the current session.