Search Results igf_ap_exclude_items_pk

Overview

The IGF_AP_EXCLUDE_ITEMS table is a pre-seeded configuration table within the IGF (Financial Aid) product module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its documented purpose is to store the items that must be excluded while rendering the View ISIR (Institutional Student Information Record) pages. During ISIR review and verification workflows, certain data elements are not displayed to end users because they are either system-generated, non-editable, or not relevant to the student-facing presentation. This table supplies that exclusion list, allowing the rendering engine to filter these items dynamically rather than hard-coding them into the application logic.

Because the table is described as pre-seeded, its rows are shipped by Oracle and are not typically maintained by customers, though institutions with extended configurations may add or adjust entries. The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modeling terms, this suggests the table behaves neither as a classic hub, link, nor satellite, but as a standalone reference or configuration set keyed by its own composite business key. Modelers treating it as a reference table would carry the composite key forward into dependent structures rather than normalizing it into separate hub entities.

Key Information Stored

The table is documented with eight columns in the 12.1.1 physical schema. The attributes of primary functional importance are the three columns that together form the documented unique index and primary key constraint:

• SYSTEM_AWARD_YEAR — Identifies the award year to which the exclusion rule applies. Because ISIR rules and item applicability change between award years, this column scopes the entire exclusion list to a specific processing cycle.
• REGION_CODE — Identifies the region or jurisdictional grouping associated with the exclusion. This allows different ISIR layouts or item sets to be excluded depending on regional requirements.
• ITEM_NAME — The name of the ISIR item that is to be suppressed during rendering; this is the actual value the view layer acts upon.

The primary key, IGF_AP_EXCLUDE_ITEMS_PK, is defined on the composite of SYSTEM_AWARD_YEAR, REGION_CODE, and ITEM_NAME. No separate surrogate key column (such as a sequence-generated ID) is documented, so the composite business key serves as the physical primary key. The remaining documented columns are the standard Oracle EBS audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support traceability of the seeded or subsequently modified rows but carry no business meaning for ISIR rendering.

Common Use Cases and Queries

The most common operational use is diagnostic: administrators troubleshooting why a particular ISIR item does not appear on the View ISIR page query this table to confirm the item has been excluded for the active award year and region. Reporting use cases typically enumerate the exclusions in effect for a given cycle to document configuration baselines or to compare exclusions across award years.

A representative query retrieves all excluded items for a specific award year and region:

• SELECT system_award_year, region_code, item_name FROM igf.igf_ap_exclude_items WHERE system_award_year = :p_year AND region_code = :p_region ORDER BY item_name;

A second pattern determines whether a specific item is suppressed, which is useful when validating rendering behavior:

• SELECT COUNT(*) FROM igf.igf_ap_exclude_items WHERE system_award_year = :p_year AND region_code = :p_region AND item_name = :p_item;

A cross-year comparison highlights additions or removals of exclusions between cycles by joining the table to itself on ITEM_NAME and REGION_CODE while varying SYSTEM_AWARD_YEAR.

Related Objects

The provided metadata classifies this object as standalone with no documented foreign keys, which limits the number of definitively related objects. The most significant dependencies are therefore logical rather than enforced by constraints:

• IGF_AP_EXCLUDE_ITEMS_PK — the primary key constraint that enforces uniqueness across SYSTEM_AWARD_YEAR, REGION_CODE, and ITEM_NAME.
• ISIR rendering views and View ISIR page components — the application-layer consumers that read the exclusion list to filter displayed items, keyed by award year, region, and item name.
• ISIR item definition entities (IGF schema) — the source of valid ITEM_NAME values referenced logically by this table.
• Award year and region reference data — the parent reference sets that provide the domain of SYSTEM_AWARD_YEAR and REGION_CODE.
• IGF financial aid setup tables — configuration tables within the same schema that govern ISIR processing and are validated in conjunction with this exclusion list.

Because no foreign keys are documented, joins to these objects should be based on shared business-key columns rather than enforced referential integrity, and integrators should treat the table as a read-mostly seeded configuration source.