Results for “project_org_use_type”

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

Overview

The IGCFV_CC_ACCOUNT_LINES view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the IGC (Contract Commitment) product family and presents contract commitment account line detail in a denormalized, user-readable form. The physical storage of account line data resides in IGC_CC_ACCT_LINES; this view joins that table to header, project, task, expenditure type, organization, GL account, and tax code reference data to expose descriptive attributes alongside the raw transactional columns. The view is used primarily for inquiry, reporting, and downstream integration where account line amounts, encumbrance status, and project/tax context must be presented together without requiring the consumer to reproduce the underlying joins. Because it is defined with Oracle Forms-style value clauses, it also supports the Contract Commitment forms UI, supplying description and meaning values for code columns. The user search term AP_TAX_CODES_ALL reflects one of the principal join columns in this view: tax name resolution.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the following base objects, all referenced as synonyms:

• IGC_CC_ACCT_LINES — the primary driving table, aliased IGCCAL.
• IGC_CC_HEADERS_ALL — contract commitment headers, supplying the commitment number and header reference.
• GL_CODE_COMBINATIONS — General Ledger code combinations for the charge, budget, and derived GL account key flexfield.
• AP_TAX_CODES_ALL — Payables tax codes, providing the tax name for the line's tax identifier.
• PA_ALL_ORGANIZATIONS — project organization definitions and organization use type.
• PA_EXPENDITURE_TYPES — expenditure type definitions and their expenditure category.
• PA_PROJECTS_ALL — project definitions, supplying project number and name.
• PA_TASKS — project task definitions, supplying task number and name.

The view therefore connects Contract Commitment transactional data directly to the Payables and Projects reference models, making it a cross-module reporting artifact rather than a purely IGC-local object.

Key Columns

The view exposes account line identifiers and amounts (ACCOUNT_LINE_NUMBER, ACCOUNT_ENTERED_AMOUNT, ACCOUNT_FUNCTIONAL_AMOUNT, ACCOUNT_BILLED_AMOUNT, ACCOUNT_UNBILLED_AMOUNT, ACCOUNT_ENCUMBRANCE_AMOUNT, ACCOUNT_ENCUMBRANCE_DATE), together with descriptive labels such as ACCOUNT_TAXABLE_FLAG, ACCT_ENCUMBRANCE_STATUS, DESCRIPTION, and the GL account key flexfield column GL_ACCOUNT. Join and context columns include CONTRACT_COMMITMENT_ID, CONTRACT_COMMIMTMENT_NUMBER, PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, and PROJECT_ORG_USE_TYPE. Tax context is provided through TAX_ID and TAX_NAME (sourced from AP_TAX_CODES_ALL.NAME). Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are also exposed.

Common Use Cases and Queries

Typical usage includes reconciliation of commitment account lines against project and tax configuration, and reporting of billed versus unbilled and encumbered amounts by project or task. A representative query joining on tax and project context follows:

• SELECT ACCOUNT_LINE_NUMBER, CONTRACT_COMMIMTMENT_NUMBER, TAX_NAME, PROJECT_NUMBER, TASK_NUMBER, ACCOUNT_ENTERED_AMOUNT FROM APPS.IGCFV_CC_ACCOUNT_LINES WHERE TAX_NAME IS NOT NULL;
• SELECT PROJECT_NUMBER, EXPENDITURE_CATEGORY, SUM(ACCOUNT_FUNCTIONAL_AMOUNT) FROM APPS.IGCFV_CC_ACCOUNT_LINES GROUP BY PROJECT_NUMBER, EXPENDITURE_CATEGORY;
• SELECT CONTRACT_COMMITMENT_ID, ACCOUNT_ENCUMBRANCE_AMOUNT, ACCT_ENCUMBRANCE_STATUS FROM APPS.IGCFV_CC_ACCOUNT_LINES WHERE ACCOUNT_ENCUMBRANCE_DATE IS NOT NULL;

Because the view performs several outer and inner joins, queries should constrain on indexed identifiers such as CONTRACT_COMMITMENT_ID or PROJECT_ID to limit the result set.