Search Results date_alias_inst_alias_value

Overview

The view APPS.IGSFV_CAL_PRD_EVNT_PAIRS is a read-only reporting object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the Application Object Library (APPS) schema. It is part of the Oracle Student System (formerly iGS, or Intellection Global Student) product family, specifically residing within the Calendar (IGS_CA) module. The view presents configured pairs of date alias instances that participate in period and event calculations, exposing both the "source" and "related" date alias definitions alongside their computed absolute and derived values.

The view is a critical integration point for academic calendar processing, where date aliases (such as term start, add/drop deadline, or census date) are frequently paired to define relationships between events. By exposing both members of a pair in a single row, the view simplifies reporting on calendar rules and supports downstream integration with student records, admissions, and financial aid processes. The user search term cals_clc_dt_from_dai corresponds to a PL/SQL function invoked within the view definition, which calculates a date from a date alias instance, underscoring the view's reliance on runtime computation rather than purely stored data.

Underlying Base Objects

According to the documented view text, IGSFV_CAL_PRD_EVNT_PAIRS is defined over three base tables:

• IGS_CA_DA_INST_PAIR (aliased as da) — the driving table, storing the pairing relationship. It contains the primary date alias instance identifier and the related date alias instance identifier.
• IGS_CA_DA_INST da1 — joined to da on DT_ALIAS, SEQUENCE_NUMBER (mapped to DAI_SEQUENCE_NUMBER), CAL_TYPE, and CI_SEQUENCE_NUMBER. This provides the source date alias instance attributes and the ABSOLUTE_VAL.
• IGS_CA_DA_INST da2 — joined to da on the related alias columns (RELATED_DT_ALIAS, RELATED_DAI_SEQUENCE_NUMBER, RELATED_CAL_TYPE, RELATED_CI_SEQUENCE_NUMBER), supplying the related instance's ABSOLUTE_VAL.

The joins are inner joins on all key columns, ensuring that a row is returned only when both the source and related date alias instances exist. The IGS_CA_DA_INST table stores the actual instance values for date aliases within a calendar instance, while IGS_CA_DA_INST_PAIR stores the configuration that links two such instances.

Key Columns

The view exposes a wide set of columns, many of which are computed at query time:

• DT_ALIAS, DAI_SEQUENCE_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — identify the source date alias instance (alias name, instance sequence, calendar type, and calendar instance sequence).
• RELATED_DT_ALIAS, RELATED_DAI_SEQUENCE_NUMBER, RELATED_CAL_TYPE, RELATED_CI_SEQUENCE_NUMBER — identify the related (paired) date alias instance using the same four-part key.
• DA1.ABSOLUTE_VAL and DA2.ABSOLUTE_VAL — the raw absolute values stored for the source and related date alias instances, respectively. These typically represent offset values or numeric representations of dates.
• IGS_CA_GEN_001.CALP_SET_ALIAS_VALUE(...) — a function call that resolves an alias value using the absolute value and a computed date, producing a display-ready value for each side of the pair.
• IGS_CA_GEN_002.CALS_CLC_DT_FROM_DAI(...) — the function referenced by the search term cals_clc_dt_from_dai. It calculates a date from a date alias instance by taking the calendar instance sequence, calendar type, date alias, and sequence number. This computed date is passed into CALP_SET_ALIAS_VALUE and also returned directly as a column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from IGS_CA_DA_INST_PAIR.

Common Use Cases and Queries

This view is primarily used in reporting and validation scenarios where two related date alias instances must be examined together. Typical use cases include verifying that paired calendar events are correctly configured, generating date comparison reports for academic periods, and supporting integration extracts that require both the source and related dates in a single row. The presence of audit columns also supports data lineage and change tracking.

Because the view performs function-based date calculations, queries should filter on the indexed columns (CAL_TYPE, CI_SEQUENCE_NUMBER, DT_ALIAS) to minimize performance overhead. A representative query follows:

• SELECT dt_alias, related_dt_alias, cal_type, ci_sequence_number, iGS_CA_GEN_002.CALS_CLC_DT_FROM_DAI(ci_sequence_number, cal_type, dt_alias, dai_sequence_number) AS src_date FROM apps.igsfv_cal_prd_evnt_pairs WHERE cal_type = 'ACAD_YR' AND ci_sequence_number = 2024;

Note that the computed date column is not directly named in the view; callers may reference it by ordinal position or re-invoke the function. For integration, the view is often joined to IGS_CA_DA_INST or calendar instance tables to enrich reporting with descriptive calendar names and instance labels.