Results for “award_date”

50+ results




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

Overview

IGF_AW_LI_AWD_INTS is an awards interface (staging) table in the Oracle E-Business Suite Financial Aid (IGF) module. Its documented purpose is "Awards Interface Table for Legacy Data Import," meaning it serves as the landing area for award records extracted from external or legacy financial aid systems before they are validated, transformed, and posted into the production award tables. The table is owned by the IGF schema and is marked VALID in the ETRM 12.1.1 repository, with 25 documented columns.

Because the table is populated by batch import processes rather than by direct end-user entry, it carries the standard EBS concurrent-request audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) alongside transaction-level staging fields. The mnemonic "LI" reflects the legacy import orientation, and "AWD_INTS" denotes the awards interface. The table acts as an inbound staging area for award amounts, award statuses, and student identifiers that must be reconciled to an existing person and award before final processing.

Under a heuristic Data Vault classification, the mined FK structure shows no inbound/outbound foreign key dependencies, i.e., the object is standalone. In Data Vault modeling terms this suggests treating IGF_AW_LI_AWD_INTS as a standalone hub-keyed staging entity rather than a pure link or satellite; the primary key is a business composite rather than a generated surrogate.

Key Information Stored

The primary key index IGF_AW_LI_AWD_INTS_PK is defined on the composite business columns (CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT). There is no separate numeric surrogate key column documented; the composite PK is itself the business-key candidate. The most important columns include:

  • CI_ALTERNATE_CODE – institution/student alternate identifier, part of the composite primary key.
  • PERSON_NUMBER – the student's person number used to resolve to a person record in HR/student systems; PK component.
  • AWARD_NUMBER_TXT – the textual award number for the record being imported; PK component.
  • BATCH_NUM – batch identifier for grouping an import run, used to control and reconcile loads.
  • FUND_CODE – the fund or program fund code corresponding to the award source.
  • OFFERED_AMT / ACCEPTED_AMT – the offered and accepted award amounts, the core financial figures being imported.
  • AWARD_STATUS_CODE / IMPORT_STATUS_TYPE – status flags indicating award state and the import disposition of the staging row.
  • AWARD_DATE / AUTHORIZATION_DATE – award and authorization dates.
  • IMPORT_RECORD_TYPE / IMPORT_STATUS_TYPE – classification and processing state of the imported record.
  • ALT_PELL_SCHEDULE_TYPE – alternate Pell schedule type relevant to federal aid processing.
  • LOCK_AWARD_FLAG – flag controlling whether the award is locked against update.
  • PUBLISH_IN_SS_FLAG – flag controlling publication to self-service.
  • APP_TRANS_NUM_TXT – application transaction number (text).
  • Standard EBS audit/concurrent columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on validating, monitoring, and reconciling inbound award imports. A common query groups staging rows by batch to confirm expected row counts and amounts:

SELECT batch_num, COUNT(*) rows_loaded, SUM(offered_amt) offered_total
FROM   igf.igf_aw_li_awd_ints
GROUP  BY batch_num;

An exception query identifies rows not yet processed or flagged as errors via the import status column:

SELECT person_number, award_number_txt, import_status_type, offered_amt
FROM   igf.igf_aw_li_awd_ints
WHERE  import_status_type NOT IN ('PROCESSED')
ORDER  BY person_number;

Reconciliation by award number or person supports tie-out between the legacy extract and the production award tables:

SELECT ci_alternate_code, person_number, award_number_txt,
       SUM(offered_amt) offered, SUM(accepted_amt) accepted
FROM   igf.igf_aw_li_awd_ints
WHERE  batch_num = :batch_num
GROUP  BY ci_alternate_code, person_number, award_number_txt;

Reporting use cases include batch import dashboards, audit extracts of award staging by fund code, and self-service publication monitoring via PUBLISH_IN_SS_FLAG. Because of the composite PK, joins back to person or award data are performed on PERSON_NUMBER and AWARD_NUMBER_TXT rather than on a numeric ID.

Related Objects

Given the mined standalone classification, no explicit foreign keys are documented; related objects are therefore inferred from shared business keys and EBS concurrent/interface conventions:

  • Production award table (IGF award master) – joined on AWARD_NUMBER_TXT and PERSON_NUMBER to post staging records.
  • Person/HR staging objects – joined on PERSON_NUMBER to resolve student identity; CI_ALTERNATE_CODE links to institution alternate identifiers.
  • Fund code reference data – joined on FUND_CODE to validate the fund against active aid funds.
  • Award status lookup – joined on AWARD_STATUS_CODE for status validation and translation.
  • Import status lookup – joined on IMPORT_STATUS_TYPE to interpret processing state.
  • FND concurrent requests / programs – joined on REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID to trace the import run.
  • BATCH_NUM control objects – joined on BATCH_NUM to manage batch-level reconciliation of staging loads.

Because FK metadata shows this object as standalone, integration is driven by these shared business-key columns rather than enforced referential constraints.