Results for “igc_cc_process_data”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGC_CC_PROCESS_DATA is a table within the IGC – Contract Commitment module of Oracle E-Business Suite. Its documented purpose is to hold general contract information used for year-end processing. In practice, this table supports the period-end and fiscal year-end close routines that reconcile committed contract values against actual activity, carrying forward or resetting balances as required by the Commitment Control accounting cycle.

According to the ETRM metadata, the table is classified under the IGC product family and is described as not implemented in this database. This status is significant: the object may exist only as a seeded or placeholder definition in certain releases, may be enabled conditionally by specific localization or patch levels, or may be present only in environments where the Commitment Control year-end process has been configured. Administrators encountering this object should verify its physical existence in ALL_TABLES rather than assuming the documented definition is deployed.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests the table behaves as a descriptive companion to a central hub or parent record — IGC_CC_HEADERS — capturing attributes that change over processing cycles rather than defining a new business entity.

Key Information Stored

The documented metadata exposes a limited but meaningful column set. The principal documented columns are:

• CC_HEADER_ID — The foreign key column referencing IGC_CC_HEADERS. This is the join anchor linking process data to the parent contract commitment header record.
• Attributes implied by the description as "general contract information used for year-end processing" — including year-end processing flags, carry-forward indicators, and reconciliation amounts.

Because the documentation does not enumerate a full column list, the surrogate primary key for this table is not explicitly documented in the excerpt provided. Following the naming convention observed across the IGC schema, a column such as a process data identifier would typically serve as the primary key, while CC_HEADER_ID functions as a business-key candidate and foreign key. Where a unique index exists on CC_HEADER_ID combined with a processing period identifier, that composite should be treated as the natural business key. Confirmation requires inspection of ALL_CONS_COLUMNS and ALL_IND_COLUMNS in the target instance.

Common Use Cases and Queries

The dominant use case is year-end reconciliation reporting for contract commitments. Typical queries join process data to headers to report which commitments remain open at fiscal close:

• Identifying contracts requiring carry-forward into the new fiscal year.
• Auditing which header records participated in the year-end run.
• Reconciling committed versus expended amounts at period close.

A representative SQL pattern is:

• SELECT h.cc_header_id, h.*, p.* FROM igc_cc_headers h, igc_cc_process_data p WHERE h.cc_header_id = p.cc_header_id;

Additional patterns include filtering by processing status for exception reporting, and using the table to drive re-processing where a prior year-end batch aborted mid-cycle.

Related Objects

The documented relationship data identifies the following dependency:

• IGC_CC_HEADERS — The parent table. Join predicate: IGC_CC_PROCESS_DATA.CC_HEADER_ID = IGC_CC_HEADERS.CC_HEADER_ID.

Broader IGC Contract Commitment objects commonly consulted alongside this table include contract line and commitment balance tables, the year-end processing concurrent programs, and reporting views that expose header-level commitment summaries. Because the metadata confirms only the header relationship, all further associations should be validated against the specific instance before reliance.