Search Results awd_hist

Overview

The view IGF_AW_AWARD_LEVEL_HIST_V belongs to the IGF — Financial Aid product family, a module that Oracle has designated as obsolete in the EBS 12.1.1 and 12.2.2 release streams. The view is documented in ETRM as the Award Level History Details View. Its purpose is to expose the transactional audit trail of changes applied to individual awards at the award-attribute level, presenting both the prior ("old") and revised ("new") values for each tracked attribute, together with human-readable lookup descriptions.

In practice this view supports historical auditing and reconciliation of financial aid awards: rather than simply displaying the current state of an award row, it reports what a specific attribute value was before a change and what it became after. Because the underlying product is obsolete, the view is not implemented in current databases and should be treated as reference metadata for upgrade, migration, or legacy-data analysis rather than as a runtime reporting object.

Underlying Base Objects

ETRM records no owner and no formally documented referenced base objects for this view. However, the view text preserved in the documentation clearly identifies the principal source object as AWD_HIST, an award-history (change log) table keyed by AWARD_ID and AWARD_HIST_TRAN_ID. Supporting objects referenced within the SQL include:

• IGF_AW_GEN — a PL/SQL package supplying lookup and translation functions such as LOOKUP_DESC and GET_CONCURRENT_PROG_NAME.
• Award distribution plan source rows aliased as OLD_DIST_PLAN and NEW_DIST_PLAN, providing AWD_DIST_PLAN_CD_DESC values.
• Lookup types accessed by name, including IGF_AW_AWARD_ATTRIBUTES, IGF_AW_AWARD_CHANGE_SOURCE, IGF_AWARD_STATUS, and IGF_AW_LOCK_STATUS.

The view therefore acts as a denormalized, presentation-layer projection over the award history base table and its reference data.

Key Columns

• ROW_ID, AWARD_ID, AWARD_HIST_TRAN_ID — identifiers linking each history row to the award and its change transaction.
• AWARD_ATTRIB_CODE / AWARD_ATTRIBUTE_DESC — the attribute that was changed and its decoded description (for example IGF_AW_AWARD_STATUS, IGF_AW_AMOUNT_OFFERED, IGF_AW_AMOUNT_PAID, IGF_AW_DIST_PLAN).
• AWARD_CHANGE_SOURCE_CODE / AWARD_CHANGE_SOURCE_DESC — the origin of the change, decoded either as a change-source lookup or as the concurrent program name and request ID when the change was driven by a batch process.
• OLD_OFFERED_AMT / NEW_OFFERED_AMT, OLD_ACCEPTED_AMT / NEW_ACCEPTED_AMT, OLD_PAID_AMT / NEW_PAID_AMT — monetary before-and-after values for the offered, accepted, and paid amounts.
• OLD_AWARD_STATUS_CODE / NEW_AWARD_STATUS_CODE — the award status before and after the change, surfaced in the OLD_VALUE and NEW_VALUE calculated columns via the IGF_AWARD_STATUS lookup — the object of interest in the search term igf_award_status.
• OLD_LOCK_AWARD_FLAG / NEW_LOCK_AWARD_FLAG — award lock indicator transitions.
• OLD_ADPLANS_ID / NEW_ADPLANS_ID — distribution plan identifiers.
• DERIVED_AWARD_UPDATE_DATE — a computed timestamp that uses LAST_UPDATE_DATE for manual changes or PROGRAM_UPDATE_DATE for programmatic changes.
• OLD_VALUE / NEW_VALUE — decoded presentation values selected by attribute via nested DECODE logic.

Common Use Cases and Queries

Typical usage centers on investigating how an award's status or monetary values changed over time and identifying the source of each change.

• Award status audit: filter on AWARD_ATTRIB_CODE = 'IGF_AW_AWARD_STATUS' to isolate status transitions for a given AWARD_ID.
• Financial reconciliation: compare OLD_OFFERED_AMT versus NEW_OFFERED_AMT to trace disbursement-driven amount adjustments.
• Change-source attribution: use AWARD_CHANGE_SOURCE_DESC to distinguish user-driven changes from concurrent program activity.

A representative query:

• SELECT award_id, award_hist_tran_id, award_attribute_desc, award_change_source_desc, old_value, new_value, derived_award_update_date FROM igf_aw_award_level_hist_v WHERE award_id = :p_award_id AND award_attrib_code = 'IGF_AW_AWARD_STATUS' ORDER BY derived_award_update_date;

Because ETRM lists no implemented objects and the module is obsolete, deployment depends on legacy IGF schemas; in modern environments the query should be validated against available synonyms before use.