Search Results igc_cch




Overview
Explore in AI Chat

Overview

APPS.IGCFV_CC_ACTION_HISTORIES is a read-only database view in Oracle E-Business Suite that consolidates contract commitment action history records into a single, reportable structure. The view joins action-level data from IGC_CC_ACTIONS with header-level data from IGC_CC_HEADERS_ALL, exposing the full action trail associated with each contract commitment. Its name, combining "CC" (Contract Commitment) and "Action Histories," reflects its purpose as an audit and tracking surface for lifecycle events such as state transitions, approvals, and control status changes. In this context, "action" refers to a discrete event applied to a contract commitment version, and the view surfaces those events alongside the identifying attributes of the parent commitment.

For report development, the view provides an OAF-friendly, denormalized shape that avoids requiring report authors to hand-code joins between the transactional action table and the header table. The embedded "_LA:" column aliases confirm that the view is designed to support lookup-driven display, where the descriptive meaning of coded values is resolved through FND_LOOKUPS at runtime rather than by the SQL itself.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed through APPS synonyms:

  • IGC_CC_ACTIONS (IGC_CCA) — the driving, transactional table holding one row per contract commitment action. The view's primary columns (action number, notes, header id, and Who columns) derive from this object.
  • IGC_CC_HEADERS_ALL (IGC_CCH) — the header table supplying contract commitment number and version number.

The join predicate is IGC_CCA.CC_HEADER_ID = IGC_CCH.CC_HEADER_ID, which links each action to the specific header version it belongs to. Because the header is the versioned entity, the combination of CC_NUM and CC_VERSION_NUM in the result identifies the exact version against which the action was taken. The view is compiled WITH READ ONLY, so it is a query-only surface — no DML is permitted through it. No WHERE clause filters are applied in the definition, so all actions matching a valid header are returned.

Key Columns

Common Use Cases and Queries

Typical uses include contract commitment audit reporting, approval tracking, control status monitoring, and integration extracts feeding downstream analytics. A current-state query returns all actions for a commitment version:

SELECT action_number, action_type, action_state,
       action_approval_status, action_notes,
       contract_commitment_number, contract_version_number
  FROM apps.igcfv_cc_action_histories
 WHERE contract_commitment_number = :cc_num
 ORDER BY creation_date;

An audit query by user or date window supports compliance review:

SELECT contract_commitment_number, contract_version_number,
       action_number, action_type, action_state,
       last_updated_by, last_update_date
  FROM apps.igcfv_cc_action_histories
 WHERE last_update_date >= :from_date
   AND last_update_date <  :to_date;

A filter on approval disposition isolates actions awaiting or denied approval:

SELECT contract_commitment_number, contract_version_number,
       action_number, action_approval_status, action_notes
  FROM apps.igcfv_cc_action_histories
 WHERE action_approval_status <> :approved_meaning;

Because the lookup columns are rendered as "_LA:" aliases, report tools resolve their meanings against FND_LOOKUPS rather than returning raw codes, so displayed values are already user-friendly.