Results for “igc_cc_headers”

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

Overview

IGC_CC_HEADERS is the master header table within the Oracle E-Business Suite Contract Commitment (IGC) module. It stores the general information that constitutes the financial representation of a contract. In the Contract Commitment architecture, a "commitment" is the accounting recognition of an obligation arising from a procurement document — typically a purchase order or release — and IGC_CC_HEADERS serves as the top-level record that anchors each commitment's header-level attributes. All downstream commitment detail (accounting lines, process data, exceptions) is keyed back to this table through CC_HEADER_ID.

The ETRM metadata classifies this object, heuristically via its foreign-key topology, as satellite-leaning. This is a modeling suggestion rather than a physical designation: the table carries a dense set of outbound foreign keys to descriptive and reference entities (currencies, users, sets of books, vendors, locations) while serving as the anchor for a small set of dependent children. In Data Vault terms it behaves partly as a hub for the commitment business key and partly as a satellite holding the descriptive context of that commitment at a point in time. The documentation notes the table is "Not implemented in this database," meaning the reference metadata was mined from the shipped schema definition rather than a live instance.

Key Information Stored

The primary key is IGC_CCH_PK, defined on the single surrogate column CC_HEADER_ID. Notably, CC_HEADER_ID also carries a foreign-key relationship to PO_HEADERS_ALL, meaning the surrogate identifier of a commitment header doubles as the reference to the originating purchasing document — a design that tightly couples commitment records to their source transactions.

• CC_HEADER_ID — surrogate primary key and link to PO_HEADERS_ALL.
• PARENT_HEADER_ID — self-referencing FK supporting hierarchical or parent/child commitment structures.
• CURRENCY_CODE — FK to FND_CURRENCIES, the transaction currency of the commitment.
• SET_OF_BOOKS_ID — FK to GL_SETS_OF_BOOKS, identifying the ledger in which the commitment is recognized.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — FKs to PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS respectively, capturing the supplier context.
• LOCATION_ID — FK to HR_LOCATIONS_ALL, the ship-to or obligation location.
• CC_OWNER_USER_ID, CC_PREPARER_USER_ID, CC_CURRENT_USER_ID — FKs to FND_USER recording ownership, preparation, and current responsibility for the commitment record.

Common Use Cases and Queries

Typical reporting centers on reconciling commitments to their purchasing and accounting sources, auditing ownership, and identifying commitments that failed processing.

• Commitments for a given ledger and currency: SELECT cc_header_id, currency_code, vendor_id FROM igc_cc_headers WHERE set_of_books_id = :sob_id;
• Ownership and responsibility audit joining to FND_USER on CC_OWNER_USER_ID and CC_CURRENT_USER_ID.
• Reconciling commitments to purchase orders via igc_cc_headers.cc_header_id = po_headers_all.po_header_id.
• Locating commitments with processing problems by joining to IGC_CC_PROCESS_EXCEPTIONS on CC_HEADER_ID.
• Traversing parent/child hierarchies using the PARENT_HEADER_ID self-join.

Related Objects

• IGC_CC_PROCESS_DATA — child table referencing IGC_CC_HEADERS.CC_HEADER_ID; holds processing state.
• IGC_CC_PROCESS_EXCEPTIONS — child table keyed to CC_HEADER_ID; stores error and exception records.
• IGC_CC_ACCT_LINES_INTERFACE — references the header via INTERFACE_HEADER_ID, carrying accounting line interface data.
• PO_HEADERS_ALL — source purchasing document matched through CC_HEADER_ID.
• GL_SETS_OF_BOOKS — ledger definition via SET_OF_BOOKS_ID.
• FND_USER — supplies owner, preparer, and current user identities.
• PO_VENDORS / PO_VENDOR_SITES_ALL / PO_VENDOR_CONTACTS — supplier master and contact hierarchy.
• FND_CURRENCIES and HR_LOCATIONS_ALL — currency and location reference data.