Search Results contract_commitment_number




Overview
Explore in AI Chat

Overview

The APPS.IGCFV_CC_ACTION_HISTORIES view is a read-only reporting object within the Oracle E-Business Suite Contract Commitment (IGC) module. It presents a consolidated, denormalized history of actions performed against contract commitments, combining action-level detail from the actions table with header-level context from the contract header table. The view carries a documented status of VALID and is owned by the APPS schema, which is consistent with standard ETRM (Enterprise Trade and Risk Management) object provisioning in Oracle EBS 12.1.1 and 12.2.2.

The view's role is primarily reporting, inquiry, and integration. By resolving foreign keys and embedding flexfield-style lookup references into named columns, it reduces the join complexity an external tool, custom report, or OAF-based page would otherwise need to reproduce. Notably, several columns are defined using the _LA: lookup convention (for example, _LA:ACTION_TYPE), which signals that the underlying IDs are translated by the application lookup layer rather than stored as descriptive text in the view itself.

Underlying Base Objects

The view is defined over two base objects:

  • IGC_CC_ACTIONS (referenced as synonym IGC_CCA) — the transaction table holding each individual action taken against a contract commitment, including action number, notes, and control/approval state identifiers.
  • IGC_CC_HEADERS (referenced as synonym IGC_CCH; documented as IGC_CC_HEADERS_ALL in the 12.2.2 metadata) — the header table holding the contract commitment number, version number, and header identifier.

The join condition is IGC_CCA.CC_HEADER_ID = IGC_CCH.CC_HEADER_ID, an inner join that returns only actions whose parent commitment header exists. The view is created WITH READ ONLY, so it supports SELECT operations exclusively and cannot be used as a DML target.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing the workflow history of a commitment, reporting approval and control status progression, and integrating action histories into external systems keyed by commitment ID. A representative query filters by the searched identifier:

  • SELECT ACTION_NUMBER, "_LA:ACTION_TYPE", "_LA:ACTION_STATE", CONTRACT_COMMITMENT_NUMBER, CONTRACT_VERSION_NUMBER, ACTION_NOTES FROM APPS.IGCFV_CC_ACTION_HISTORIES WHERE CONTRACT_COMMITMENT_ID = :p_commitment_id ORDER BY ACTION_NUMBER;
  • SELECT CONTRACT_COMMITMENT_ID, COUNT(*) FROM APPS.IGCFV_CC_ACTION_HISTORIES GROUP BY CONTRACT_COMMITMENT_ID;
  • SELECT * FROM APPS.IGCFV_CC_ACTION_HISTORIES WHERE "_LA:ACTION_APPROVAL_STATUS" = 'Approved';

Because the lookup columns are resolved by the application layer, reports executed directly in SQL against this view may observe the underlying IDs rather than translated meanings unless the reporting tool applies the lookup convention. Where translated values are required, join to FND_LOOKUPS on the corresponding lookup type and language.