Search Results system_award_year

Overview

IGF.IGF_AP_EXCLUDE_ITEMS is a pre-seeded configuration table in the Oracle E-Business Suite IGF (Oracle Grants/Proposal) schema. Its documented purpose is to store the item names that must be excluded while rendering Integrated Search and Information Repository (ISIR) view pages. The table is owned by the IGF schema, resides in the APPS_TS_SEED tablespace, and is registered as FND Design Data (IGF.IGF_AP_EXCLUDE_ITEMS) with a status of VALID. Because the contents are seeded by Oracle and not maintained by end users, the design intentionally omits foreign key constraints on the business columns; referential enforcement is therefore not applied at the database level.

From a dimensional modeling perspective, the mined relationship structure classifies this object as standalone, which suggests it is best modeled as a small reference or lookup table rather than as part of a hub-and-satellite or link construct. The physical schema is identical in the documented 12.1.1 metadata and is carried forward into the 12.2.2 release; there are no structural differences reported between the two versions aside from the standard online patching considerations in 12.2.2. The table holds eight columns and one unique index.

Key Information Stored

The table is deliberately narrow. The three business columns form the composite unique key, and the remaining five columns are standard WHO audit attributes.

• SYSTEM_AWARD_YEAR (VARCHAR2(30)) — stores the System Award Year to which the exclusion rule applies. This is the first component of the primary key and is the column most frequently used as a filter, since the value is a text representation of the award year rather than a numeric year.
• REGION_CODE (VARCHAR2(30)) — stores the Page Region Code identifying the ISIR page region from which the item should be suppressed.
• ITEM_NAME (VARCHAR2(30)) — stores the name of the item to be excluded from rendering within the identified region.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns, populated automatically at insert and update, providing the audit trail for seeded data.

The surrogate-style uniqueness is enforced by the index IGF_AP_EXCLUDE_ITEMS_PK, a NORMAL UNIQUE index in APPS_TS_SEED spanning SYSTEM_AWARD_YEAR, REGION_CODE, and ITEM_NAME. Because no separate single-column surrogate key exists, these three columns also serve as the business-key candidate: the same item may be excluded in multiple award years or in multiple regions, but only once per award-year/region/item combination.

Common Use Cases and Queries

The principal use case is diagnostics and configuration review. When an ISIR page fails to display an expected item, developers and functional analysts query this table to confirm whether the item has been deliberately seeded for exclusion.

• Retrieve all exclusions for a specific award year: SELECT system_award_year, region_code, item_name FROM igf.igf_ap_exclude_items WHERE system_award_year = :award_year ORDER BY region_code, item_name;
• Confirm whether a particular item is suppressed in a region: SELECT COUNT(*) FROM igf.igf_ap_exclude_items WHERE system_award_year = :award_year AND region_code = :region_code AND item_name = :item_name;
• Produce a seeded-configuration listing for audit or upgrade comparison, grouping counts by award year and region: SELECT system_award_year, region_code, COUNT(*) excluded_items FROM igf.igf_ap_exclude_items GROUP BY system_award_year, region_code;
• Compare seeded rows between environments after a 12.1.1 to 12.2.2 upgrade by extracting the three key columns and diffing them externally.

Reporting should always be read-only. Because Oracle owns and reseeds the content, direct DML is not supported and any manual change risks being overwritten by patching or upgrade activity.

Related Objects

The documented dependency information states that IGF_AP_EXCLUDE_ITEMS does not reference any database object and that it is referenced only by its APPS synonym or view wrapper IGF_AP_EXCLUDE_ITEMS. No foreign key relationships to other IGF tables are defined, which limits the number of directly joinable objects. In practice, the following objects are most relevant when working with or around this table:

• APPS.IGF_AP_EXCLUDE_ITEMS — the APPS-layer synonym or wrapper through which the seeded data is normally queried.
• IGF_AP_EXCLUDE_ITEMS_PK — the unique index on (SYSTEM_AWARD_YEAR, REGION_CODE, ITEM_NAME) used to validate and drive lookups.
• ISIR page and region definitions in the IGF/IGS reporting framework, joined conceptually on REGION_CODE and ITEM_NAME.
• Award year reference data in the grants schemas, joined conceptually on the textual SYSTEM_AWARD_YEAR value rather than by a declared foreign key.
• Standard EBS access objects such as FND_APPLICATION and the WHO-related FND_USER, used to resolve CREATED_BY and LAST_UPDATED_BY.

Given the absence of enforced foreign keys, joins to any related object must be constructed on the documented business columns and validated against seeded values rather than assumed from the data model.