Results for “igc_cc_process_exceptions”

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

Overview

The IGC_CC_PROCESS_EXCEPTIONS table belongs to the Oracle EBS IGC – Contract Commitment module. Its documented purpose is to capture errors generated during year-end processing of contract commitments. In the commitment control lifecycle, year-end routines roll open commitments forward from one fiscal year to the next; when individual records cannot be processed successfully — due to invalid funding, missing accounting distributions, unbalanced amounts, or referential integrity issues — the offending rows and their associated error detail are written to this table rather than silently discarded. As a result, the table functions as a diagnostic and reconciliation surface for period-end close activities rather than as a transactional working table.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies this object as satellite-leaning. That is a modeling suggestion only: the table hangs off a parent business entity (the commitment header) and stores descriptive, process-specific attributes about that entity rather than introducing new hubs or many-to-many link relationships. Its grain is one row per processing exception, and its load is driven by a batch year-end program.

Practically, the table is valuable to close teams and technical support because it isolates exactly which commitment headers failed and prevents a mass year-end rollover from becoming an opaque failure. Reviewers typically query it before, during, and after the rollover window to resolve exceptions and re-run processing.

Key Information Stored

The documented metadata confirms a foreign-key relationship to the commitment header entity, which anchors the table's identifying and descriptive columns:

• CC_HEADER_ID — The foreign key to IGC_CC_HEADERS. This is the principal business-key candidate, identifying the commitment header that produced the exception. It is the join column used in virtually every diagnostic query against this table.
• Exception/error detail columns — Attribute columns record what went wrong during year-end processing, typically error messages, codes, and contextual values. These are the payload of the satellite.
• Surrogate primary key — As with most EBS interface/exception tables, a system-generated unique identifier (commonly a sequence-populated ID column) is expected to serve as the surrogate PK, distinct from the business key CC_HEADER_ID. Because CC_HEADER_ID is not unique across exception rows (a header may fail for multiple reasons), it cannot itself be the primary key.
• Processing/audit columns — Creation and last-update audit fields (WHO columns) and any processing date or batch identifier support traceability back to the specific year-end run.

The metadata excerpt does not enumerate individual column names beyond CC_HEADER_ID; the remaining columns should be verified against the live data dictionary for the target release (12.1.1 or 12.2.2), since the ETRM notes that the table is not implemented in this database.

Common Use Cases and Queries

Typical scenarios center on diagnosing year-end rollover failures. A close analyst or DBA runs the year-end commitment process, then immediately reports exceptions. The standard pattern joins the exception table back to the header to retrieve identifying context:

• List all exceptions for the run — SELECT * FROM igc_cc_process_exceptions WHERE cc_header_id = :header_id;
• Count failures by header — aggregate on CC_HEADER_ID to find headers with repeated failures.
• Join to the parent — SELECT e.*, h.* FROM igc_cc_process_exceptions e JOIN igc_cc_headers h ON e.cc_header_id = h.cc_header_id; to obtain commitment number, funding source, and amounts for remediation.
• Reconciliation reporting — extract the exception population to a spreadsheet or BI report for the close checklist, then clear it after corrections and re-run.

Because the table is a transient error log, periodic purging or archiving after successful remediation is a recommended housekeeping practice.

Related Objects

• IGC_CC_HEADERS — The immediate parent via IGC_CC_PROCESS_EXCEPTIONS.CC_HEADER_ID; the primary object joined in all investigative queries.
• IGC_CC_LINES and IGC_CC_DISTRIBUTIONS — Child entities of the header, frequently inspected to understand why a header raised an exception.
• IGC_CC_COMMITMENTS / commitment control views — Used to reconcile failed rollovers against the commitment ledger.
• Year-end processing concurrent programs — The batch jobs that populate this table during the close.
• GL period-close and funds-check related objects — Downstream consumers that depend on successful commitment rollover before the period can close.

Note: the ETRM metadata marks this table as not implemented in the source database; column-level verification against the target instance is therefore advisable before relying on any non-documented column.