Results for “related_dt_alias”

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

Overview

IGS_CA_DA_PAIR is a configuration table within the Oracle E-Business Suite IGS (Student System) product family. It describes the combination of date aliases into pairs, providing the metadata that links one calendar date alias to a related date alias. In the context of the IGS calendar and date-alias subsystem, this table enables rules and processes to reference two aliases together — for example, pairing an enrollment open alias with its corresponding close alias, or associating a term start alias with a term end alias.

Within the ETRM 12.1.1 documentation this object carries the annotation "Not implemented in this database," and the product itself is marked Obsolete. It should therefore be regarded as a legacy structural artifact retained for historical schema completeness rather than an actively populated configuration entity in current Oracle EBS 12.1.1 or 12.2.2 environments.

Applying the heuristic Data Vault classification supplied in the metadata, IGS_CA_DA_PAIR is best modeled as a link table. It resolves a many-to-many style association between two instances of the same parent entity (IGS_CA_DA), which is the classic signature of a link construct in Data Vault terms. This is a modeling suggestion only, derived from the foreign-key topology, not a formal Oracle designation.

Key Information Stored

The table contains seven documented columns. The most significant are listed below; the audit columns are noted collectively.

• DT_ALIAS — The first date alias in the pair. This is a business-key column that also participates in both the primary key and the foreign key to IGS_CA_DA.
• RELATED_DT_ALIAS — The second, related date alias in the pair. Like DT_ALIAS, it is a business-key column, part of the primary key, and a foreign key to IGS_CA_DA.
• CREATED_BY — Standard EBS audit column identifying the user who created the row.
• CREATION_DATE — Standard EBS audit column recording row creation timestamp.
• LAST_UPDATED_BY — Standard EBS audit column identifying the last user to modify the row.
• LAST_UPDATE_DATE — Standard EBS audit column recording the last modification timestamp.
• LAST_UPDATE_LOGIN — Standard EBS audit column capturing the login session of the last update.

The primary key is IGS_CA_DA_PAIR_PK, defined over the composite business key (DT_ALIAS, RELATED_DT_ALIAS). A unique index, IGS_CA_DA_PAIR_U1, is documented over the same two columns, confirming that the pair combination is the natural business-key candidate. There is no separate surrogate key column; the pairing itself enforces uniqueness.

Common Use Cases and Queries

Because the object is obsolete and not implemented in the documented database, practical queries are largely of an investigative or migration-audit nature. Typical patterns include:

• Verifying existence or population — a simple SELECT COUNT(*) FROM igs_ca_da_pair; to confirm whether the table is populated in a given environment.
• Resolving paired aliases — joining both alias columns back to IGS_CA_DA to retrieve the descriptive names of each alias in a pair.
• Detecting orphan pairs — outer joins from IGS_CA_DA_PAIR to IGS_CA_DA on either DT_ALIAS or RELATED_DT_ALIAS to find pairs whose parent alias no longer exists.
• Data-migration assessment — extracting all pairs when consolidating or retiring legacy IGS calendar configuration.

A representative query resolves both sides of each pair:

SELECT p.DT_ALIAS, a1.DESCRIPTION AS ALIAS_DESC, p.RELATED_DT_ALIAS, a2.DESCRIPTION AS RELATED_DESC FROM igs_ca_da_pair p JOIN igs_ca_da a1 ON a1.DT_ALIAS = p.DT_ALIAS JOIN igs_ca_da a2 ON a2.DT_ALIAS = p.RELATED_DT_ALIAS;

Reporting use cases center on documenting calendar alias relationships for impact analysis before decommissioning the obsolete IGS Student System components.

Related Objects

The most significant related objects are driven by the two foreign keys, both of which target the same parent table.

• IGS_CA_DA — the parent date-alias table. Referenced twice: IGS_CA_DA_PAIR.DT_ALIAS → IGS_CA_DA and IGS_CA_DA_PAIR.RELATED_DT_ALIAS → IGS_CA_DA. This dual dependency is what establishes the link classification.
• IGS_CA_DA_PAIR_PK — the primary key constraint over (DT_ALIAS, RELATED_DT_ALIAS).
• IGS_CA_DA_PAIR_U1 — the unique index validating the same business key.
• IGS_CA_DA_PAIR (self-referential role) — both foreign keys originate from and resolve to the same table, so the object acts as its own relationship resolver.
• IGS calendar date-alias API and concurrent programs — processes that read alias pairings during calendar generation or validation; these depend on the pair definitions when populated.

Given the obsolete status, no active application views or public APIs are documented as depending on IGS_CA_DA_PAIR. Any dependencies in a 12.1.1 or 12.2.2 instance should be validated directly against the deployed schema, since the ETRM metadata records the object as not implemented.