Results for “related_date_alias_description”

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

Overview

The view IGSBV_CAL_PRD_EVNT_TYPE_PAIRS is the base view for the entity Calendar Period Event Type Pairs within the Oracle E-Business Suite Student System (IGS) product family. The entity describes combinations of date aliases organized into related pairs, providing the semantic foundation used by the academic calendar engine to associate one date alias with a corresponding related date alias. In Oracle EBS 12.1.1 and 12.2.2, this object belongs to the IGS module, which ETRM documents as obsolete; implementations therefore typically encounter this view only in historical or upgraded environments that retain legacy Student System objects.

From a reporting and integration perspective, the view presents a denormalized, read-only projection of the relationship between a date alias and its related date alias, together with the descriptions of both. This enables downstream reporting, calendar rule configuration, and integration extracts to resolve the pairing without repeatedly joining the underlying alias definitions. The view is explicitly defined with the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting access rather than transactional maintenance.

Underlying Base Objects

Although the documented ETRM metadata records no referenced base objects, the view text identifies three source tables, all from the IGS_CA_% namespace: IGS_CA_DA_PAIR, IGS_CA_DA (aliased twice as DA1 and DA2), and their join conditions. Specifically, IGS_CA_DA_PAIR supplies the pairing (DT_ALIAS and RELATED_DT_ALIAS) plus audit columns, while IGS_CA_DA is joined twice to resolve the description for each side of the pair. The join predicates DA.DT_ALIAS = DA1.DT_ALIAS and DA.RELATED_DT_ALIAS = DA2.DT_ALIAS enforce that both aliases in the pair must exist as defined date aliases.

The ETRM metadata states the view is "Not implemented in this database," meaning the object may be absent in certain environments or database instances documented by that repository. Where present, it is a database view rather than a table, so no independent storage or DML is supported.

Key Columns

• DATE_ALIAS — the primary date alias in the pair (source DA.DT_ALIAS).
• RELATED_DATE_ALIAS — the corresponding related date alias (source DA.RELATED_DT_ALIAS).
• DATE_ALIAS_DESCRIPTION — descriptive text for the primary alias (from DA1.DESCRIPTION).
• RELATED_DATE_ALIAS_DESCRIPTION — descriptive text for the related alias (from DA2.DESCRIPTION).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns carried from the pair record.

Note the column naming distinction: the view text references RELATED_DT_ALIAS internally, while the exposed column is documented as RELATED_DATE_ALIAS — this is the field commonly surfaced when users search for the related date alias attribute.

Common Use Cases and Queries

Typical usage includes reporting on calendar alias pairings and resolving related date aliases during calendar configuration or data migration from legacy IGS implementations. A simple listing query is:

SELECT DATE_ALIAS, RELATED_DATE_ALIAS, DATE_ALIAS_DESCRIPTION, RELATED_DATE_ALIAS_DESCRIPTION FROM IGSBV_CAL_PRD_EVNT_TYPE_PAIRS;

A filtered lookup for a specific related date alias, matching the user's search term, would take the form:

SELECT DATE_ALIAS, RELATED_DATE_ALIAS FROM IGSBV_CAL_PRD_EVNT_TYPE_PAIRS WHERE RELATED_DATE_ALIAS = :p_related_date_alias;

Because the view is read-only and its source tables are legacy, these queries are best confined to historical reporting and audit activities rather than active functional processing.