Search Results cc_det_pf_version_num




Overview
Explore in AI Chat

Overview

IGC_CC_DET_PF_VERSION_V is an APPS-owned database view in Oracle E-Business Suite classified under the IGC (Contract Commitment) product family. It presents a version-aware projection of contract commitment detail lines for the detail performance (PF) entity, returning the effective row for each commitment line based on a runtime version number supplied by the IGC_CC_VERSION_VIEW_PKG package. The view exists primarily to support reporting and inquiry against contract commitments without requiring the calling application to resolve versioning logic explicitly.

Because contract commitment records in IGC are versioned, the base transactional table IGC_CC_DET_PF holds current rows while historical revisions reside in IGC_CC_DET_PF_HISTORY. Consumers that need to know what a commitment looked like at a particular version must reconcile these two sources. IGC_CC_DET_PF_VERSION_V encapsulates that reconciliation in a single queryable object, so reports, concurrent programs, and integration extracts can retrieve point-in-time commitment detail lines through a normal SELECT statement.

Underlying Base Objects

The view is defined over three documented objects:

  • IGC_CC_DET_PF — the primary detail performance table holding the live commitment line rows.
  • IGC_CC_DET_PF_HISTORY — the history table capturing prior version revisions of the same lines.
  • IGC_CC_VERSION_VIEW_PKG — the PL/SQL package supplying GET_VERSION_NUM, the parameter that drives which version snapshot the view returns.

The view text combines a MINUS operation and a UNION. Rows in IGC_CC_DET_PF that have no matching version-qualified entry in history are returned directly. Separately, history rows whose minimum version number is greater than or equal to the current version supplied by IGC_CC_VERSION_VIEW_PKG.GET_VERSION_NUM, and whose action is not 'I' (insert), are returned. This construction yields the appropriate effective record for each commitment line across the version boundary.

Key Columns

The view exposes the same column set as the underlying detail performance tables, notably:

Common Use Cases and Queries

Typical usage involves commitment reporting, encumbrance reconciliation, and integration feeds that must respect versioning. A sample query follows:

SELECT cc_det_pf_line_id, cc_det_pf_line_num, cc_det_pf_func_amt, cc_det_pf_encmbrnc_status FROM apps.igc_cc_det_pf_version_v WHERE cc_acct_line_id = :p_acct_line_id;

Additional scenarios include joining the view to commitment header data for lifecycle reporting, extracting commitment amounts for downstream encumbrance validation, and building version-sensitive audit extracts. Because the returned rows depend on IGC_CC_VERSION_VIEW_PKG.GET_VERSION_NUM, callers should confirm the package state is initialized for the intended version context before relying on the output.