Search Results alias_val




Overview

The IGS_CA_DA_INST_ALIAS_VAL_V view is a reporting and integration object within the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It belongs to the APPS schema and is documented as a VALID view in the ETRM metadata. Its stated purpose is to provide derived, absolute, and effective dates for a date alias instance.

Institutional calendar functionality in IGS relies heavily on "date aliases" — named points in time (for example, census date, withdrawal deadline, or fee due date) that are attached to a calendar instance rather than hard-coded. This view resolves those aliases into concrete date values. It exposes three distinct representations of the same alias value: the raw stored ABSOLUTE_VAL, a computed DERIVED_VAL obtained from the calendar generation package, and the final resolved ALIAS_VAL produced by applying the calendar pattern logic. This layered resolution makes the view valuable wherever downstream processes, reports, or integrations require the definitive date associated with a date alias for a specific calendar instance.

Underlying Base Objects

The ETRM metadata does not document a referenced base object list, but the embedded view text confirms that the view is defined over a single base table:

The view does not join to additional tables. Instead, it invokes two database functions owned by the APPS schema to perform date resolution at query time:

Key Columns

  • DT_ALIAS — the date alias identifier, naming the calendar event being resolved.
  • SEQUENCE_NUMBER — identifies which occurrence of the alias applies where an alias repeats.
  • CAL_TYPE — the calendar type under which the alias instance is defined.
  • CI_SEQUENCE_NUMBER — the calendar instance (the specific calendar, such as an academic year) to which the alias belongs.
  • ABSOLUTE_VAL — the stored absolute date value held on the instance record.
  • DERIVED_VAL — the date computed by CALS_CLC_DT_FROM_DAI, reflecting relative placement within the calendar pattern.
  • ALIAS_VAL — the effective, resolved date returned by CALP_SET_ALIAS_VALUE; this is the column users seek when searching on "alias_val".
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include validating that a date alias resolves to the expected date for an academic period, feeding resolved dates into enrollment or fee-calculation extracts, and auditing discrepancies between stored and computed values. A basic query follows:

SELECT dt_alias, cal_type, ci_sequence_number, absolute_val, derived_val, alias_val
FROM apps.igs_ca_da_inst_alias_val_v
WHERE ci_sequence_number = :ci_seq;

Because DERIVED_VAL and ALIAS_VAL call PL/SQL functions per row, filtering by DT_ALIAS, CAL_TYPE, and CI_SEQUENCE_NUMBER is recommended to limit execution cost. Be aware that function exceptions or missing calendar setup can suppress rows or raise errors at runtime.