Search Results igs_ca_da_pair_pk

Overview

The IGS_CA_DA_PAIR table is a data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically belonging to the now-obsolete IGS (Student System) product. Its core function is to define logical pairings between date aliases. In academic systems, date aliases are symbolic names for significant calendar dates (e.g., TERM_START, ENROLLMENT_END). This table establishes relationships between two such aliases, creating a paired context that was likely used for date validation, dependency rules, or scheduling logic within the legacy student administration modules. Critically, the provided ETRM metadata indicates this table was "Not implemented in this database," suggesting it may exist as a reference or placeholder object without populated data in standard deployments.

Key Information Stored

The table's structure is defined by a composite primary key, consisting of two columns that also serve as foreign keys. This design enforces the uniqueness and validity of each date alias pairing. The key columns are:

• DT_ALIAS: The primary date alias in the pair. This column references the IGS_CA_DA (Date Alias) table.
• RELATED_DT_ALIAS: The related or secondary date alias that is paired with the first. This column also references the IGS_CA_DA table, creating a symmetric relationship.

The table's sole purpose is to store and validate these two-column combinations, with no other attributes indicated in the provided metadata.

Common Use Cases and Queries

Given its status as obsolete and potentially unimplemented, direct operational use in active processes is unlikely. Historically, its purpose would have been to support queries enforcing date dependencies. For instance, a rule might require that the "ENROLLMENT_END" date alias must always be paired with and occur after a "TERM_START" date alias. A typical query to retrieve all defined pairs would be:

SELECT dt_alias, related_dt_alias FROM igs_ca_da_pair ORDER BY 1;

To validate a specific date alias against its permitted related aliases, a query might join to the master IGS_CA_DA table:

SELECT da1.dt_alias_name, da2.dt_alias_name FROM igs_ca_da_pair pair, igs_ca_da da1, igs_ca_da da2 WHERE pair.dt_alias = da1.dt_alias AND pair.related_dt_alias = da2.dt_alias;

In a reporting context, this table would have served as a lookup to understand mandated date relationships within the academic calendar framework.

Related Objects

The IGS_CA_DA_PAIR table has a direct and exclusive relationship with the IGS_CA_DA (Date Alias) table, as evidenced by its two foreign key constraints. Both the DT_ALIAS and RELATED_DT_ALIAS columns reference the IGS_CA_DA table, ensuring that only valid, predefined date aliases can be members of a pair. The primary key constraint IGS_CA_DA_PAIR_PK enforces the uniqueness of each combination. As a component of the obsolete IGS Student System, it is not referenced by newer Oracle Student Management or Campus Solutions modules, and its dependencies are confined to the legacy schema.