Results for “sys_award_year”

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

Overview

IGF_AW_LKUPS_OVRD is a configuration table in the Oracle E-Business Suite Financial Aid (IGF) module. It stores the System Award Year together with the lookup types whose lookup codes must be excluded from processing for that award year. In effect, the table acts as an override or exclusion register: instead of redefining lookup values, institutions record which existing lookup codes should be suppressed in the context of a specific award year, allowing year-specific behavior without altering the underlying lookup definitions.

The table resides in the IGF schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its structure is deliberately narrow, carrying only the essential identification attributes plus standard Oracle who-columns. The documented physical schema lists seven columns in total: SYS_AWARD_YEAR, LOOKUP_TYPE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as hub-leaning. This is a modeling suggestion rather than a mandated design: the table carries a compact, stable business key and a low rate of change, which resembles a hub entity. Its dependent detail rows are held separately in IGF_AW_LKUP_OVD_DET, reinforcing the hub-and-dependent pattern.

Key Information Stored

The most important columns are those forming the primary key and the associated audit attributes.

• SYS_AWARD_YEAR — the System Award Year for which lookup exclusions apply. This is the primary temporal discriminator of the row.
• LOOKUP_TYPE — the lookup type whose lookup codes must be excluded for the referenced award year.
• CREATED_BY — the application user or process that created the row.
• CREATION_DATE — the date and time of row creation.
• LAST_UPDATED_BY — the user or process responsible for the most recent update.
• LAST_UPDATE_DATE — the timestamp of the last modification.
• LAST_UPDATE_LOGIN — the login context associated with the last update.

The surrogate primary key is IGF_AW_LKUPS_OVRD_PK, defined over (SYS_AWARD_YEAR, LOOKUP_TYPE). A unique index, IGF_AW_LKUPS_OVRD_U1, is documented over the same two columns, making them the business-key candidates for the table. Because the primary key and the unique index coincide, there is no separate numeric surrogate column; the business key itself enforces uniqueness of award-year and lookup-type combinations.

Common Use Cases and Queries

Typical usage centers on determining which lookup codes are excluded for a given award year, and on reporting the override configuration by award year or lookup type.

To list all exclusions for a specific award year:

SELECT lookup_type
FROM   igf.igf_aw_lkups_ovrd
WHERE  sys_award_year = :p_award_year;

To find all award years in which a given lookup type is excluded:

SELECT sys_award_year
FROM   igf.igf_aw_lkups_ovrd
WHERE  lookup_type = :p_lookup_type
ORDER  BY sys_award_year;

To inspect recently maintained overrides:

SELECT sys_award_year, lookup_type,
       last_updated_by, last_update_date
FROM   igf.igf_aw_lkups_ovrd
WHERE  last_update_date >= :p_since
ORDER  BY last_update_date DESC;

Reporting use cases include auditing year-over-year configuration drift in lookup exclusions, reconciling which lookup types remain active for award processing, and producing change-control extracts that capture the who-columns for compliance review.

Related Objects

The metadata documents the following foreign key relationships.

• IGF_AW_LKUP_OVD_DET — the dependent detail table. Its columns IGF_AW_LKUP_OVD_DET.SYS_AWARD_YEAR and IGF_AW_LKUP_OVD_DET.LOOKUP_TYPE reference the corresponding key columns of IGF_AW_LKUPS_OVRD, forming a parent-child relationship. This is the primary documented dependent object and the natural join partner for exclusion-detail reporting.

In practice, ad hoc joins to lookup value definition objects, such as those maintained through the FND lookup administration UI, are common when resolving LOOKUP_TYPE and excluded lookup codes to their displayed meanings. Any dependent view or concurrent program that reads IGF_AW_LKUP_OVD_DET should also be reviewed, since those programs ultimately rely on the parent row in IGF_AW_LKUPS_OVRD to determine applicability for the System Award Year.