Search Results aw_alternate_code

Overview

The IGF_SE_AUTH_V view resides in the APPS schema and belongs to the IGF (Financial Aid) product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes authorization records that have been transmitted to the student financial aid interface layer, and it simultaneously preserves historical and inactive authorization rows. The view is therefore both a transactional feeder for downstream processing (such as loan certification, disbursement authorization, and Title IV reporting) and an audit trail covering the full lifecycle of an authorization.

A governing business rule is embedded in the underlying design: for any single award line, only one authorization record may remain active at a time. Superseded authorizations are retained as inactive history, which makes the view suitable for reconciliation, change tracking, and compliance evidence. Because it is a view rather than a table, no DML should be issued against it; consumers read it directly or embed it in concurrent programs and BI Publisher data templates.

Underlying Base Objects

The documented SQL definition joins four base objects:

• IGF_SE_AUTH (aliased SAI) — the primary authorization entity, supplying dates, person attributes, fund references, thresholds, accepted amount, award calendar coordinates, and auditing columns.
• IGS_CA_INST (aliased CA1) — the calendar instance table, matched on CAL_TYPE and SEQUENCE_NUMBER, providing the award-year alternate code and start/end dates.
• IGF_AW_FUND_MAST (aliased FM) — the fund master, joined on FUND_ID, supplying the fund code and description.
• IGF_AW_AWARD_ALL (aliased AWD) — the award allocation, joined on AWARD_ID, and also used inside the IGF_SL_LAR_CREATION.GET_LOAN_START_DT and GET_LOAN_END_DT PL/SQL function calls.

Notably, the user search term aw_alternate_code maps to the view column AW_ALTERNATE_CODE, sourced from CA1.ALTERNATE_CODE in IGS_CA_INST, alongside AW_START_DATE and AW_END_DATE.

Key Columns

• AUTH_ID, SEQUENCE_NO, AUTH_DATE, FLAG — identity, ordering, effective date, and status indicator for the authorization.
• PERSON_ID, FIRST_NAME, LAST_NAME, address fields, SSN_NO, BIRTH_DT, MARITAL_STATUS, SEX_MEANING — student demographic and identification data.
• VISA_TYPE, VISA_CATEGORY, VISA_NUMBER, VISA_EXPIRY_DT, ENTRY_DATE — non-citizen eligibility attributes.
• FUND_ID, FUND_CODE, DESCRIPTION — the aid fund being authorized.
• THRESHOLD_PERCT, THRESHOLD_VALUE, ACCEPTED_AMNT, MIN_HR_RATE, MAX_HR_RATE, GOVT_SHARE_PER — award calculation and funding-share parameters.
• AW_CAL_TYPE, AW_SEQUENCE_NUMBER, AW_ALTERNATE_CODE, AW_START_DATE, AW_END_DATE — the award year context.
• AWARD_ID, NOTIFICATION_DATE, REQUEST_ID, plus standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical scenarios include verifying which authorization is active for a given award line, extracting award-year context via the alternate code, and reconciling accepted amounts against fund masters for disbursement.

SELECT auth_id, person_id, fund_code, accepted_amnt,
       aw_cal_type, aw_sequence_number, aw_alternate_code,
       aw_start_date, aw_end_date, auth_date, flag
FROM   apps.igf_se_auth_v
WHERE  award_id = :p_award_id
AND    flag = 'Y';

To identify active authorizations by award year:

SELECT aw_alternate_code, fund_code, COUNT(*)
FROM   apps.igf_se_auth_v
WHERE  aw_alternate_code = :p_alt_code
GROUP  BY aw_alternate_code, fund_code;

Because the view returns DISTINCT rows and includes inactive history, filters on FLAG and AUTH_DATE are essential to avoid double counting when aggregating amounts for interface feeds or audit reports.