Search Results icaa_pk

Overview

IGC_CC_ARC_ACTIONS is a table in the IGC (Contract Commitment) product schema within Oracle E-Business Suite, holding records of actions performed against contracts that are slated for archival. In the Oracle EBS 12.1.1 and 12.2.2 data models, this table functions as an archival audit trail: as contracts progress toward archival, each action—whether workflow-driven, approval-related, or system-triggered—is captured here so that a complete action history survives the archival lifecycle. The table is owned by the IGC schema and is marked VALID in the ETRM documentation.

From a modeling standpoint, the provided heuristic Data Vault classification is satellite-leaning. In practical terms, this suggests treating IGC_CC_ARC_ACTIONS as a satellite structure attached to a parent contract hub: the header identifier serves as the hub reference, while the action-level descriptive attributes (action number, type, state, and statuses) carry the changing context of each action event. This classification should be regarded as a modeling suggestion rather than a normative definition, since the physical implementation is a conventional EBS table with composite primary key enforcement.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• CC_HEADER_ID — Identifier of the parent contract header; the principal linkage back to the contract being archived. It participates in both the primary key and the foreign key relationship.
• CC_ACTION_NUM — Sequence number of the action recorded against the contract. Together with CC_HEADER_ID it forms the composite business key.
• CC_ACTION_VERSION_NUM — Version indicator for the action record, useful for tracking revisions or repeated processing of the same action.
• CC_ACTION_TYPE — Categorizes the action (for example approval, workflow, or archival-related event).
• CC_ACTION_STATE — Current state of the action within its lifecycle.
• CC_ACTION_CTRL_STATUS — Control status of the action, reflecting processing or control-stage outcomes.
• CC_ACTION_APPRVL_STATUS — Approval status, indicating whether the action has been approved, rejected, or is pending.
• CC_ACTION_NOTES — Free-form notes or comments attached to the action.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns identifying when and by whom the row was last modified.
• CREATION_DATE, CREATED_BY — Standard creation audit columns indicating row inception.

The surrogate primary key is ICAA_PK, defined over the composite of CC_HEADER_ID and CC_ACTION_NUM. The unique index IGC_CC_ARC_ACTIONS_U1 also covers CC_HEADER_ID and CC_ACTION_NUM, confirming this pair as the business-key candidate that enforces one row per action number per contract header. A documented foreign key relates CC_HEADER_ID back to a parent contract table referenced through the same column.

Common Use Cases and Queries

Typical usage centers on auditing and reconciling the archival lifecycle of contracts. Reporting queries join the action table back to the contract header using CC_HEADER_ID, and filter or sort on CC_ACTION_NUM to reconstruct the ordered action history for a contract.

• Action history for a contract: Select all rows for a given CC_HEADER_ID ordered by CC_ACTION_NUM to view the full sequence of archived actions.
• Approval monitoring: Filter on CC_ACTION_APPRVL_STATUS and CC_ACTION_STATE to identify actions pending approval or stalled in a particular state before archival completes.
• Control reconciliation: Group by CC_ACTION_CTRL_STATUS and CC_ACTION_TYPE to summarize volumes and outcomes of archival actions for a period, bounded by CREATION_DATE or LAST_UPDATE_DATE.
• Trend analysis: Aggregate counts of actions per type and state to detect bottlenecks in the archival pipeline.

A representative pattern is: SELECT CC_HEADER_ID, CC_ACTION_NUM, CC_ACTION_TYPE, CC_ACTION_STATE, CC_ACTION_APPRVL_STATUS FROM IGC.IGC_CC_ARC_ACTIONS WHERE CC_HEADER_ID = :header_id ORDER BY CC_ACTION_NUM. Because the composite key is indexed, such lookups are efficient for per-contract retrieval.

Related Objects

IGC_CC_ARC_ACTIONS depends primarily on the contract header it references. The documented foreign key columns are CC_HEADER_ID within both IGC_CC_ARC_ACTIONS and its foreign table, establishing the parent-child linkage. Practically, the most significant related objects are:

• The parent IGC contract header table (referenced via CC_HEADER_ID), which supplies the contract identity for every action row.
• IGC_CC_ARC_ACTIONS itself, whose self-referencing FK entry (IGC_CC_ARC_ACTIONS.CC_HEADER_ID) documents the column used in the relationship.
• Archival and workflow objects in the IGC schema that drive action transitions recorded in CC_ACTION_STATE and CC_ACTION_APPRVL_STATUS.
• Standard EBS audit and concurrency infrastructure that populates the LAST_UPDATE_* and CREATION_* columns.
• Reporting views and concurrent programs in IGC that consume this table to produce contract archival histories.

The FK metadata provided is limited to the CC_HEADER_ID relationship shown as IGC_CC_ARC_ACTIONS.CC_HEADER_ID → %, so additional dependent objects should be confirmed against the deployed 12.1.1 or 12.2.2 dictionary before finalizing integration designs.