Search Results igc_cc_acct_line_version_v




Overview
Explore in AI Chat

Overview

IGC_CC_ACCT_LINE_VERSION_V is an APPS-owned database view in the Oracle E-Business Suite Contract Commitment (IGC) module. Its purpose is to expose the currently effective version of each contract commitment account line, resolving version history so that downstream reporting, inquiry screens, and integration interfaces always read a single, consistent row per account line. In EBS 12.1.1 and 12.2.2 the object is delivered with a VALID status and is defined over the account line base table and its history table, filtered against the version number returned by IGC_CC_VERSION_VIEW_PKG.GET_VERSION_NUM.

The view is version-aware rather than a simple projection. It returns the live row from IGC_CC_ACCT_LINES when no qualifying history exists, and otherwise returns the earliest history row whose CC_ACCT_VERSION_NUM is greater than or equal to the version supplied by the version package. This makes it suitable for commitment-versus-actual comparisons and for expenditure analysis where the account line must reflect a specific commitment version.

Underlying Base Objects

The documented base objects referenced by the view are:

  • IGC_CC_ACCT_LINES (SYNONYM) — the current account line records.
  • IGC_CC_ACCT_LINE_HISTORY (SYNONYM) — historical versions of account lines, keyed by CC_ACCT_LINE_ID and CC_ACCT_VERSION_NUM.
  • IGC_CC_VERSION_VIEW_PKG (PACKAGE) — supplies the active version number via GET_VERSION_NUM, which drives the history filter.

The effective row set is produced by a MINUS of the current table against history at or above the active version, unioned with the corresponding history rows. Parent-child relationships are preserved through PARENT_HEADER_ID and PARENT_ACCT_LINE_ID.

Key Columns

Common Use Cases and Queries

Typical scenarios include commitment reporting by expenditure item date, reconciliation of encumbered amounts, and integration extracts that must respect commitment versioning.

  • Listing active account lines for a commitment header.
  • Filtering commitment lines by expenditure item date range.
  • Extracting project and task level commitment balances.

Sample query by expenditure item date:

SELECT cc_acct_line_id, cc_header_id, project_id, task_id, expenditure_type, expenditure_item_date, cc_acct_func_amt, cc_acct_en cmbrnc_amt FROM apps.igc_cc_acct_line_version_v WHERE expenditure_item_date BETWEEN TO_DATE('01-JAN-2024','DD-MON-YYYY') AND TO_DATE('31-JAN-2024','DD-MON-YYYY') ORDER BY expenditure_item_date, cc_header_id;

Joining to project and task for descriptive reporting:

SELECT v.cc_acct_line_id, v.project_id, p.name project_name, v.task_id, v.expenditure_item_date, v.cc_acct_func_amt FROM apps.igc_cc_acct_line_version_v v, apps.pa_projects_all p WHERE v.project_id = p.project_id AND v.cc_acct_en cmbrnc_status = 'Y';

Because the view applies version logic internally, consumers should not add their own version predicates; any additional filtering should be limited to business columns such as expenditure_item_date, project_id, or encumbrance status.