Search Results icaal_pk

Overview

IGC_CC_ARC_ACCT_LINES is a table owned by the IGC schema within the Oracle E-Business Suite Contract Commitment module. Its documented description is "Account lines for contracts to be archived," which positions it as a staging or archive counterpart to the live contract commitment account line entity. In Oracle EBS 12.1.1 and 12.2.2, Contract Commitment supports the capture and tracking of commitments against contracts, projects, tasks, and expenditure types, and account lines represent the distribution-level detail — the individual accounting rows generated against a commitment header. The "_ARC_" infix indicates that this table is purposed for archival processing, holding account line rows that are being moved out of the active commitment tables for retention, purge, or long-term storage. It is therefore an operational and historical record rather than a configuration or transactional master.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table's identity is defined by a single surrogate primary key (CC_ACCT_LINE_ID) and it carries numerous descriptive, amount, and status attributes alongside its parent references, which is characteristic of a satellite attached to a parent hub or link (the contract commitment header) rather than a hub or link itself.

Key Information Stored

The table is documented with 46 columns. The principal identifiers and business-critical attributes include:

• CC_ACCT_LINE_ID — the surrogate primary key (constraint ICAAL_PK) and the column backing the unique index IGC_CC_ARC_ACCT_LINES_U1, making it the sole documented business-key candidate.
• CC_HEADER_ID — the foreign key to the commitment header, tying the archived account line back to its parent contract commitment.
• PARENT_ACCT_LINE_ID and PARENT_HEADER_ID — self-referencing lineage columns that allow hierarchical or split account line structures to be reconstructed in the archive.
• CC_ACCT_LINE_NUM — the human-readable line sequence number.
• CC_CHARGE_CODE_COMBINATION_ID and CC_BUDGET_CODE_COMBINATION_ID — foreign keys to GL_CODE_COMBINATIONS representing the charge and budget accounting flexfield combinations.
• CC_ACCT_ENTERED_AMT, CC_ACCT_FUNC_AMT, CC_ACCT_BILLED_AMT, and CC_ACCT_UNBILLED_AMT — the core monetary attributes in entered, functional, billed, and unbilled form.
• CC_ACCT_ENCMBRNC_AMT, CC_ACCT_ENCMBRNC_DATE, and CC_ACCT_ENCMBRNC_STATUS — encumbrance amount, date, and status.
• PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE — project accounting context referencing PA_PROJECTS_ALL, PA_TASKS, and PA_EXPENDITURE_TYPES.
• TAX_ID and CC_ACCT_TAXABLE_FLAG — tax code reference (AP_TAX_CODES_ALL) and taxable indicator.
• CC_ACCT_DESC — the descriptive text for the account line.

Standard EBS audit and DFF columns (LAST_UPDATE_DATE, CREATED_BY, CONTEXT, ATTRIBUTE1 through ATTRIBUTE15) are also present, supporting auditability and descriptive flexibility.

Common Use Cases and Queries

Because this table is oriented to archival, its primary use cases center on historical reporting, reconciliation, and purge verification. Typical scenarios include reconciling archived commitment amounts against GL balances for a closed period, reconstructing the full commitment detail for contracts no longer in the active tables, and validating that archival jobs transferred all lines before deletion from live tables.

A representative query joining archived lines to project and accounting context:

• SELECT a.CC_ACCT_LINE_ID, a.CC_HEADER_ID, a.CC_ACCT_LINE_NUM, a.CC_ACCT_FUNC_AMT, a.CC_ACCT_ENCMBRNC_AMT, a.CC_ACCT_ENCMBRNC_STATUS, a.PROJECT_ID, a.TASK_ID, a.EXPENDITURE_TYPE, gcc.concatenated_segments charge_cc FROM igc.igc_cc_arc_acct_lines a LEFT JOIN gl_code_combinations_kfv gcc ON gcc.code_combination_id = a.cc_charge_code_combination_id WHERE a.cc_header_id = :p_header_id ORDER BY a.cc_acct_line_num;

Additional patterns include aggregating functional and encumbrance amounts by expenditure type or project for cost analysis, and self-joining on PARENT_ACCT_LINE_ID to expose split or hierarchical structures. Reporting tools such as Oracle Reports, BI Publisher, and discoverer-style ad hoc queries are frequently pointed at this table when historical commitment detail is required.

Related Objects

The most significant related objects, with their documented join columns, are:

• IGC_CC_ARC_ACCT_LINES (self) — joined via PARENT_ACCT_LINE_ID to PARENT_ACCT_LINE_ID for hierarchical lineage.
• GL_CODE_COMBINATIONS — joined via CC_CHARGE_CODE_COMBINATION_ID and CC_BUDGET_CODE_COMBINATION_ID for accounting flexfield detail.
• PA_PROJECTS_ALL — joined via PROJECT_ID for project context.
• PA_TASKS — joined via TASK_ID for task-level detail.
• PA_EXPENDITURE_TYPES — joined via EXPENDITURE_TYPE for expenditure classification.
• AP_TAX_CODES_ALL — joined via TAX_ID for tax code reference.
• PO_LINES_ALL and PO_LINE_LOCATIONS_ALL — related through CC_ACCT_LINE_ID, providing purchasing document context for the commitment.

These relationships confirm that the table functions as a central accounting-detail satellite for archived contract commitments, linking commitment headers, purchasing documents, project accounting structures, and general ledger combinations.