Search Results igc_cc_arc_actions_u1

Overview

IGC.IGC_CC_ARC_ACTIONS is a table in the IGC (Oracle Contracts) schema that temporarily stores contract actions which have been archived. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the table serves as a staging and retention area for commitment-related action history that has been moved out of the active transaction tables, allowing the Contracts module to preserve an auditable trail of actions without burdening primary operational tables. The object is owned by the IGC schema, carries a FND Design Data reference of IGC.IGC_CC_ARC_ACTIONS, holds VALID status, and resides in the APPS_TS_ARCHIVE tablespace with a PCT Free of 10.

Because the table stores descriptive attributes of contract actions keyed to a parent contract commitment header, its heuristic Data Vault classification is satellite-leaning. Under this modeling suggestion, IGC_CC_ARC_ACTIONS functions as a satellite attached to the contract commitment hub represented by the header identifier, capturing the changing state, status, and version attributes of archived actions rather than defining new business entities of its own.

Key Information Stored

The table contains thirteen documented columns. The primary key, ICAA_PK, is composed of the composite business key (CC_HEADER_ID, CC_ACTION_NUM), which is also enforced by the unique index IGC_CC_ARC_ACTIONS_U1 in the APPS_TS_ARCHIVE tablespace. There is therefore no separate surrogate key column in the documented schema; the unique index itself serves as the business-key candidate. CC_HEADER_ID identifies the contract commitment defining column, while CC_ACTION_NUM is the contract commitment action line number.

• CC_HEADER_ID — Contract commitment defining column; foreign key to the parent commitment.
• CC_ACTION_NUM — Contract commitment action line number.
• CC_ACTION_VERSION_NUM — Version number of the contract commitment action.
• CC_ACTION_TYPE — Category of the action committed against the contract.
• CC_ACTION_STATE — State of the contract at the time of the action.
• CC_ACTION_CTRL_STATUS — Control status of the contract commitment.
• CC_ACTION_APPRVL_STATUS — Approval status of the contract commitment.
• CC_ACTION_NOTES — Free-formatted text (max 240) describing the nature of the action.

The remaining columns are the standard Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY, which provide audit lineage for each archived row.

Common Use Cases and Queries

Typical use cases include auditing historical contract actions, reconstructing the state and approval trajectory of a commitment, and reporting on archived activity without querying live action tables. A baseline retrieval for a single commitment is:

• SELECT CC_ACTION_NUM, CC_ACTION_VERSION_NUM, CC_ACTION_TYPE, CC_ACTION_STATE, CC_ACTION_APPRVL_STATUS FROM IGC.IGC_CC_ARC_ACTIONS WHERE CC_HEADER_ID = :p_header_id ORDER BY CC_ACTION_NUM;
• Count archived actions by type: SELECT CC_ACTION_TYPE, COUNT(*) FROM IGC.IGC_CC_ARC_ACTIONS GROUP BY CC_ACTION_TYPE;
• Identify approvals archived in a period: SELECT CC_HEADER_ID, CC_ACTION_NUM, CC_ACTION_APPRVL_STATUS FROM IGC.IGC_CC_ARC_ACTIONS WHERE CREATION_DATE BETWEEN :p_from AND :p_to;

Because the table is archival, insert and read operations dominate; reports should join back to the commitment header using CC_HEADER_ID.

Related Objects

The documented foreign key on CC_HEADER_ID links this table to the contract commitment header in the IGC schema, shown as IGC.IGC_CC_ARC_ACTIONS.CC_HEADER_ID → % in the metadata. The most significant related objects are therefore:

• The contract commitment header table referenced by CC_HEADER_ID (join key: CC_HEADER_ID).
• IGC contract action tables that feed the archival process, sharing CC_HEADER_ID and CC_ACTION_NUM.
• IGC_CC_ARC_ACTIONS_U1, the unique index enforcing the (CC_HEADER_ID, CC_ACTION_NUM) business key.
• FND_USER, referenced conceptually by LAST_UPDATED_BY and CREATED_BY (USER_ID).
• FND_LOGINS, referenced conceptually by LAST_UPDATE_LOGIN (LOGIN_ID).
• APPS_TS_ARCHIVE tablespace, the physical storage location.

These relationships support archival reconciliation, purge verification, and historical audit reporting across the Contracts commitment model.