Results for “igf_aw_coa_itm_terms”

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

Overview

IGF_AW_COA_ITM_TERMS is an Oracle E-Business Suite table owned by the IGF (Financial Aid) schema. It is documented as VALID in EBS 12.1.1 and 12.2.2 and stores the amount split setup for a given cost of attendance (COA) item. In practice, the table defines how a single cost of attendance item is divided into amount terms across an academic calendar instance, allowing institutions to model disbursement or budgeting structure at the term level. Each row therefore represents one amount term assignment for a COA item tied to a specific calendar type and sequence.

Under a heuristic Data Vault classification mined from the foreign key structure, the table is best treated as a link. It resolves a many-to-many relationship between a cost of attendance item (IGF_AW_COA_ITEMS) and a calendar instance (IGS_CA_INST_ALL), while also carrying descriptive measures and audit attributes. This classification is a modeling suggestion rather than a fixed EBS construct.

Key Information Stored

The table's primary key, IGF_AW_COA_ITM_TERMS_PK, is a composite surrogate key over four columns: BASE_ID, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, and ITEM_CODE. A matching unique index, IGF_AW_COA_ITM_TERMS_U1, exists on the same four columns, making them the documented business-key candidate that enforces uniqueness of an amount-term split per COA item and calendar instance. The 15 documented columns include the following significant attributes:

• BASE_ID — identifies the parent cost of attendance base record; part of the business key and FK to IGF_AW_COA_ITEMS.
• ITEM_CODE — the cost of attendance item being split; part of the business key and FK to IGF_AW_COA_ITEMS.
• LD_CAL_TYPE — the academic calendar type of the term; part of the business key and FK to IGS_CA_INST_ALL.
• LD_SEQUENCE_NUMBER — the calendar instance sequence identifying the specific term; part of the business key and FK to IGS_CA_INST_ALL.
• AMOUNT — the amount attributed to this item for the given term, representing the split value.
• LOCK_FLAG — indicates whether the term record is locked against modification, a common EBS concurrency and edit-control attribute.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns capturing row creation and change history.
• LAST_UPDATE_LOGIN — the login context of the most recent update.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context columns recorded when rows are populated by batch processes.

Common Use Cases and Queries

Typical reporting retrieves the amount split for a COA item across terms. A representative query joins the item table to the terms table and filters on the calendar instance:

• List all term splits for a given base and item: SELECT item_code, ld_cal_type, ld_sequence_number, amount FROM igf.igf_aw_coa_itm_terms WHERE base_id = :base_id AND item_code = :item_code;
• Summarize amounts per term for a COA base: aggregate AMOUNT grouped by LD_CAL_TYPE and LD_SEQUENCE_NUMBER.
• Audit changes using LAST_UPDATED_BY, LAST_UPDATE_DATE, and REQUEST_ID to trace which concurrent program populated or last touched a record.
• Identify locked rows via LOCK_FLAG before attempting updates in interfaces or conversion scripts.

These patterns support financial aid packaging validation, disbursement planning, and reconciliation of COA budgets against term schedules.

Related Objects

The following documented relationships are the most significant for joins and dependency analysis:

• IGF_AW_COA_ITEMS — parent COA item definition; joined on BASE_ID and ITEM_CODE.
• IGS_CA_INST_ALL — academic calendar instance; joined on LD_CAL_TYPE and LD_SEQUENCE_NUMBER.
• IGF_AW_COA_ITM_TERMS_PK — composite primary key constraint over BASE_ID, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, ITEM_CODE.
• IGF_AW_COA_ITM_TERMS_U1 — unique index on the same four business-key columns.

Broader dependencies include other IGF Financial Aid objects that consume COA item amounts, such as award packaging and disbursement setup tables, though these are not explicitly documented in the supplied metadata.