Search Results isir_map_col




Overview

IGF.IGF_AP_INST_VER_ITEM_ALL is a transaction-level table in the Oracle E-Business Suite 12.1.1 / 12.2.2 Financial Aid (IGF) module. It stores the verification values captured for every user-defined ISIR (Institutional Student Information Record) field associated with a student financial aid record. In practice, the table acts as the repository where institution-specific verification items — configured as user-defined fields — are persisted alongside the base aid record they belong to. This allows institutions to record, waive, and evaluate verification data that is not part of the standard ISIR layout.

The object resides in the IGF schema, uses the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is classified as VALID. Its design follows the standard Oracle EBS multi-tenant pattern through the ORG_ID operating unit column. Based on the documented foreign key structure — a link between IGF_AP_FA_BASE_REC_ALL (the parent aid record) and IGF_AP_USR_DEF_FLDS_ALL (the user-defined field definition) — a Data Vault modeling heuristic would classify this table as a link entity resolving the many-to-many relationship between base aid records and user-defined verification items, with the item values themselves behaving as link attributes. This classification is a modeling suggestion rather than a physical constraint.

Key Information Stored

The most significant columns capture the identity of the verification item, its value, and its verification state:

  • BASE_ID — Unique identifier for the student financial aid record (the parent).
  • UDF_VERN_ITEM_SEQ_NUM — Identifier for the user-defined verification item; this is the column most commonly searched (the user's query term udf_vern_item_seq_num targets it directly).
  • ITEM_VALUE — The captured value of the user-defined verification item. Length 100.
  • WAIVE_FLAG — Denotes whether the verification item is waived.
  • ISIR_MAP_COL — Stores the ISIR SAR column number sourced from lookups; identifies which verification item the row represents. Length 30.
  • INCL_IN_TOLERANCE — Indicates whether the item is included in the Total Tolerance Amount.
  • USE_BLANK_FLAG — A Y/N identifier determining whether a null value counts as a documented value.
  • LEGACY_RECORD_FLAG — Indicates whether the record was imported through a legacy process.
  • ORG_ID — Operating unit identifier.
  • Standard Who columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The documented primary key is IGF_AP_INST_VERN_ITEM_ALL_PK, composite over (UDF_VERN_ITEM_SEQ_NUM, BASE_ID). A separate business-key candidate unique index, IGF_AP_INST_VERN_ITEM_ALL_U1, covers (UDF_VERN_ITEM_SEQ_NUM, BASE_ID, ISIR_MAP_COL), enforcing that a given verification item maps to a single ISIR column per base record.

Common Use Cases and Queries

Typical reporting scenarios include auditing captured verification values for a specific student, identifying waived items, and reviewing tolerance-eligible items. A representative pattern retrieves all verification rows for a base record:

  • Join verification items to aid records by BASE_ID.
  • Filter by UDF_VERN_ITEM_SEQ_NUM to locate a specific item.
  • Aggregate by WAIVE_FLAG or INCL_IN_TOLERANCE for summary reporting.

The documented query text uses a full-column projection from IGF.IGF_AP_INST_VER_ITEM_ALL, which supports extracting all verification attributes for downstream analysis. Additional filtering by ORG_ID is advisable in multi-org implementations.

Related Objects

The following objects are the most significant to this table:

  • IGF.IGF_AP_FA_BASE_REC_ALL — parent aid record, joined via BASE_ID.
  • IGF.IGF_AP_USR_DEF_FLDS_ALL — user-defined field definitions, referenced via UDF_VERN_ITEM_SEQ_NUM.
  • IGF_AP_INST_VERN_ITEM_ALL_PK — primary key constraint (UDF_VERN_ITEM_SEQ_NUM, BASE_ID).
  • IGF_AP_INST_VERN_ITEM_ALL_U1 — unique index (UDF_VERN_ITEM_SEQ_NUM, BASE_ID, ISIR_MAP_COL).

No additional database objects are documented as referencing this table, so its principal dependencies are the two parent tables identified above through its foreign keys.