Results for “igf_aw_awd_ltr_tmp”

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

Overview

IGF_AW_AWD_LTR_TMP is a transient staging table owned by the IGF schema within the Oracle E-Business Suite Financial Aid (IGF) product family. Its documented purpose is to store temporary data that is rendered onto the Award Notification Letter — the correspondence sent to students or applicants communicating the details of an award package. Rather than persisting letter content permanently, the table functions as a short-lived workspace where award lines, fund descriptions, and term-level amounts are assembled immediately prior to letter generation.

The table resides only in the IGF schema and is not a public synonym or shared reference object. Under the heuristic Data Vault classification mined from its foreign-key structure, the object is assessed as standalone, meaning it references no parent entities through enforced foreign keys and is not itself referenced. From a modeling perspective, this suggests it behaves less like a conformed hub or link and more like a disposable satellite-style staging artifact: a scratch structure whose rows are populated, consumed, and typically purged or replaced per notification run.

Because the object is temporary by design, its row population is volatile and should never be treated as an authoritative historical record. Financial aid administrators, integration developers, and reporting authors should rely on it strictly for the duration of a letter-generation cycle.

Key Information Stored

The documented physical schema contains fourteen columns. The most significant are listed below.

• PERSON_ID — identifies the student or applicant to whom the notification letter pertains; part of the composite primary key.
• CI_CAL_TYPE and CI_SEQUENCE_NUMBER — the calendar type and sequence that identify the academic period or term against which awards are communicated; both are part of the primary key.
• LINE_ID — the line-level identifier distinguishing individual rows within a person/term combination; completes the primary key.
• FUND_CODE and FUND_DESCRIPTION — the award fund identifier and its human-readable description as they appear on the letter.
• AWARD_NAME — the award or award-category label presented to the recipient.
• AWARD_TOTAL — the monetary total for the award line, used in letter totals.
• TERM_AMOUNT_TEXT — formatted textual representation of the term-level amount, suited to direct rendering on the printed letter.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who loaded the temporary rows and when.

The surrogate primary key is IGF_AW_AWD_LTR_TMP_PK on (PERSON_ID, CI_CAL_TYPE, CI_SEQUENCE_NUMBER, LINE_ID). The unique index IGF_AW_AWD_LTR_TMP_U1 carries the identical column set, so the primary key and the business key coincide; there is no separate artificial sequence key.

Common Use Cases and Queries

Typical usage centers on verifying the staged content of a letter before or after generation, and on diagnosing missing or duplicated award lines.

• Retrieve all staged lines for one recipient and term: SELECT line_id, fund_code, award_name, award_total FROM igf.igf_aw_awd_ltr_tmp WHERE person_id = :p AND ci_cal_type = :c AND ci_sequence_number = :s ORDER BY line_id;
• Aggregate staged totals per person for reconciliation against persisted award records.
• Audit staged rows by CREATED_BY and CREATION_DATE to confirm a given letter run executed correctly.
• Detect orphan or stale rows when a generation process terminates before purging.

Because this is a working table, queries should always be scoped by PERSON_ID and calendar keys and should not be relied upon for period-over-period reporting.

Related Objects

The documented metadata records no enforced foreign keys, so the object is classified as standalone. Practically, it is populated by the IGF award notification process and derives its PERSON_ID and calendar values from the same student and award entities maintained elsewhere in the IGF schema. Objects most commonly implicated alongside it include the IGF award and fund definition tables that supply FUND_CODE, FUND_DESCRIPTION, and AWARD_NAME, the IGF person/application tables behind PERSON_ID, and the calendar tables behind CI_CAL_TYPE and CI_SEQUENCE_NUMBER. The letter-generation concurrent program that consumes this table, and any award notification views built over it, complete the dependency chain. Join keys are the composite (PERSON_ID, CI_CAL_TYPE, CI_SEQUENCE_NUMBER, LINE_ID) tuple.