Results for “igs_en_spa_awd_aim_v”

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

Overview

The IGS_EN_SPA_AWD_AIM_V view is a reporting and inquiry object within the Oracle E-Business Suite Student System (IGS) product family. It exposes information about the maintenance of a student's targeted awards for each student program attempt. Specifically, the view consolidates the student's intended or targeted award records, capturing the start and end dates associated with the award aim and a completion flag that indicates whether the targeted award was satisfied.

Within the EBS architecture, this view functions as a denormalized read layer over the award aim maintenance table. It joins the student program attempt award aim data to the award definition table so that the descriptive award title is presented alongside the identifying award code. This makes the view suitable for reporting, inquiry forms, and integration extracts where a human-readable award description is required without forcing the consuming application to perform an additional lookup against the award catalog. The view is documented as part of the IGS Student System, which is flagged as obsolete in the ETRM documentation, meaning it is retained for backward compatibility with legacy student administration deployments rather than for new implementations.

Underlying Base Objects

The view is defined over two base objects as documented in the view text:

• IGS_EN_SPA_AWD_AIM ESA — the primary table storing award aim maintenance records for each student program attempt. This table supplies the person, course, award code, dates, completion indicator, conferral date, grading attributes, and standard WHO audit columns.
• IGS_PS_AWD AWD — the award definition table, joined on AWARD_CD, supplying the AWARD_TITLE that the view aliases as DESCRIPTION.

The join condition is an equi-join on ESA.AWARD_CD = AWD.AWARD_CD, so only award aim records whose award code exists in the award definition table are returned. The documented ETRM metadata lists no additional referenced base objects beyond these two. The view also exposes ESA.ROWID as ROW_ID, which is a common EBS technique used to support updateable views and row-level identification in Forms-based interfaces.

Key Columns

• ROW_ID — the ROWID of the underlying award aim row, used for row identification and updateable view support.
• PERSON_ID — the identifier of the student to whom the targeted award pertains.
• COURSE_CD — the course code associated with the student program attempt context.
• AWARD_CD — the code of the targeted award; the join key to the award definition.
• DESCRIPTION — the award title drawn from IGS_PS_AWD, providing the readable award name.
• START_DT / END_DT — the effective start and end dates for the award aim record.
• COMPLETE_IND — flag indicating whether the targeted award aim has been completed.
• CONFERRAL_DATE — the date on which the award was conferred, where applicable.
• AWARD_MARK / AWARD_GRADE / GRADING_SCHEMA_CD / GS_VERSION_NUMBER — grading outcomes and the grading schema context under which the mark or grade was assigned.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

Typical usage centers on reporting a student's targeted awards and their completion status. A straightforward query retrieving all award aims for a given student would be:

SELECT person_id, course_cd, award_cd, description,
       start_dt, end_dt, complete_ind, conferral_date
FROM   igs_en_spa_awd_aim_v
WHERE  person_id = :p_person_id;

A second common pattern filters by completion status to list outstanding versus achieved targeted awards:

SELECT person_id, award_cd, description, complete_ind
FROM   igs_en_spa_awd_aim_v
WHERE  complete_ind = 'N'
ORDER  BY person_id, award_cd;

A third pattern joins the view to grading information when producing transcripts or award audit reports, using AWARD_MARK, AWARD_GRADE, and CONFERRAL_DATE to present outcomes. Because the object is documented as obsolete, integration and reporting development should confirm its availability in the target environment prior to reliance; the DBA data indicates the view is not implemented in all databases.