Results for “aw_sequence_number”

3 results




Overview
Explore in AI Chat

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

Overview

The view IGF_AW_AWD_LD_CAL_V belongs to the IGF - Financial Aid product family, which is documented in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 as an obsolete module. Its purpose, as stated in the ETRM metadata, is to retrieve all load calendars that fall within an award year. In practical terms, the view correlates award-year calendars (category AWARD) with their associated load calendars (category LOAD) by traversing the calendar instance relationship table.

Because financial aid processing requires disbursement and fund-delivery schedules to align with the academic award year, this view provides a convenient, pre-joined projection over the underlying calendar infrastructure. Rather than requiring a report or integration to re-derive the parent/child relationship between award calendars and load calendars, the view exposes both sides side-by-side. It is a reporting and integration artifact: a consumer can select from it directly to list every load calendar tied to a given award year, along with the start and end dates and alternate codes on both sides. The view carries no scheduling or business logic of its own; it is a read-only SELECT.

Underlying Base Objects

The documented view text defines the object over five base tables, all drawn from the IGS (Student System / Campus Community calendar) schema:

  • IGS_CA_INST AW — the award calendar instance (aliased AW), joined through CAL_TYPE and SEQUENCE_NUMBER.
  • IGS_CA_INST LD — the load calendar instance (aliased LD), the subordinate calendar.
  • IGS_CA_TYPE AW_T — the calendar type for the award side, filtered so that S_CAL_CAT = 'AWARD'.
  • IGS_CA_TYPE LD_T — the calendar type for the load side, filtered so that S_CAL_CAT = 'LOAD'.
  • IGS_CA_INST_REL REL — the calendar instance relationship table, which supplies the supervisory/subordinate linkage between the award calendar and the load calendar.

The join path is the key structural fact: REL.SUP_CAL_TYPE and REL.SUP_CI_SEQUENCE_NUMBER must match the award calendar, while REL.SUB_CAL_TYPE and REL.SUB_CI_SEQUENCE_NUMBER must match the load calendar. The two calendar type lookups then constrain the higher-level categories to AWARD and LOAD respectively. The ETRM metadata notes that no referenced base objects were separately documented for the 12.2.2 object record and that the view is not implemented in this database, so it should be treated as a legacy/shipped definition rather than an active runtime object.

Key Columns

The view selects ROW_ID from the award instance together with two parallel sets of five attributes:

  • ROW_ID — the identifier of the award calendar instance row.
  • AW_CAL_TYPE / AW_SEQUENCE_NUMBER — the calendar type and instance sequence number of the award-year calendar.
  • AW_ALTERNATE_CODE — the alternate code assigned to the award calendar instance; this is the column users frequently probe when searching on aw_alternate_code.
  • AW_START_DT / AW_END_DT — the effective start and end dates of the award calendar.
  • LD_CAL_TYPE / LD_SEQUENCE_NUMBER — the calendar type and instance sequence number of the associated load calendar.
  • LD_ALTERNATE_CODE — the alternate code for the load calendar instance.
  • LD_START_DT / LD_END_DT — the start and end dates of the load calendar, which should fall within the award-year window.

Note that the underlying instance table stores ALTERNATE_CODE; the view prefixes it as AW_ALTERNATE_CODE and LD_ALTERNATE_CODE to disambiguate the two sides.

Common Use Cases and Queries

Typical use cases include validating that every load calendar is bound to an award year, auditing alternate-code assignment, and feeding downstream disbursement or packaging reports. A representative query filtering on the award alternate code is:

  • SELECT ROW_ID, AW_CAL_TYPE, AW_SEQUENCE_NUMBER, AW_ALTERNATE_CODE, AW_START_DT, AW_END_DT, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE, LD_START_DT, LD_END_DT FROM IGF_AW_AWD_LD_CAL_V WHERE AW_ALTERNATE_CODE = :code;
  • A date-range check to confirm load calendars fall inside the award year: SELECT * FROM IGF_AW_AWD_LD_CAL_V WHERE LD_START_DT >= AW_START_DT AND LD_END_DT <= AW_END_DT;
  • An inventory of load calendars per award type, grouped by AW_CAL_TYPE and LD_CAL_TYPE.

Because the module is obsolete and the view is not implemented in the reference database, confirm availability in the target instance before relying on it in production reports.