Results for “daip_uk”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_CA_DA_INST_PAIR is a table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in both the 12.1.1 and 12.2.2 releases. Its stated purpose is to store the pairing of two date alias instances, thereby enabling the definition of a period of time that is inclusive of the two date aliases. In the broader calendar architecture of the Student System, a date alias instance (held in IGS_CA_DA_INST) represents a single occurrence of a named date alias within a specific calendar instance. The IGS_CA_DA_INST_PAIR table extends that model by relating one such occurrence to a second, related occurrence, producing an explicit start/end pairing that downstream processes can treat as a bounded period.
From a Data Vault modeling perspective, the mined relationship metadata classifies this object heuristically as a link. This is consistent with its structure: the table's identity is defined by two references to the same parent entity (IGS_CA_DA_INST), and it carries no descriptive attributes of its own beyond the standard Who columns. Any downstream dimensional model would therefore treat IGS_CA_DA_INST_PAIR as a link table resolving a many-to-many or self-referencing relationship between date alias instances, rather than as a hub or satellite.
Key Information Stored
The documented physical schema for 12.1.1 contains 13 columns. The most significant are listed below.
- DT_ALIAS, DAI_SEQUENCE_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — this four-column group identifies the first (primary) date alias instance in the pairing. Together they form the leading portion of both the primary key and the unique index.
- RELATED_DT_ALIAS, RELATED_DAI_SEQUENCE_NUMBER, RELATED_CAL_TYPE, RELATED_CI_SEQUENCE_NUMBER — the mirrored four-column group identifying the second (related) date alias instance. These columns point to the same parent table as their non-related counterparts, making the relationship self-referencing at the instance level.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit (Who) columns recording insert and update provenance.
Two key constraints are documented. The primary key, IGS_CA_DA_INST_PAIR_PK, is defined over DT_ALIAS, DAI_SEQUENCE_NUMBER, CAL_TYPE, and CI_SEQUENCE_NUMBER. A second unique index, IGS_CA_DA_INST_PAIR_U2, is also documented over the same four columns and is listed as the unique constraint DAIP_UK; in the ETRM metadata this index is flagged as a business-key candidate. The table has no separately generated surrogate key column — the identity of a row is the composite business key of the primary date alias instance.
Common Use Cases and Queries
Typical usage centers on resolving a named period for a given calendar. A reporting query joins the pairing table back to IGS_CA_DA_INST twice, once through the primary alias columns and once through the RELATED_ columns, to retrieve both endpoints of the period.
- Retrieving the start and end date aliases for a pairing: join IGS_CA_DA_INST a on a.DT_ALIAS = p.DT_ALIAS and a.DAI_SEQUENCE_NUMBER = p.DAI_SEQUENCE_NUMBER and a.CAL_TYPE = p.CAL_TYPE and a.CI_SEQUENCE_NUMBER = p.CI_SEQUENCE_NUMBER, and join IGS_CA_DA_INST b on b.DT_ALIAS = p.RELATED_DT_ALIAS and the three matching RELATED_ columns.
- Reporting all pairings within a calendar: filter the pairing table by CAL_TYPE and CI_SEQUENCE_NUMBER to scope results to a single calendar instance before joining to the instance table.
- Checking pair integrity: because both halves of the pair must exist in IGS_CA_DA_INST, a consistency report can left-join each side and flag any row where either endpoint fails to resolve.
- Period derivation: applications that need an inclusive date range for a given academic or administrative period select the pairing and translate the two alias instances into concrete dates through their underlying alias definitions.
Related Objects
The following objects are most significant in relation to IGS_CA_DA_INST_PAIR, based on the documented foreign key structure.
- IGS_CA_DA_INST — the sole documented parent table, referenced twice. The foreign key maps IGS_CA_DA_INST_PAIR.DT_ALIAS, DAI_SEQUENCE_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER to IGS_CA_DA_INST. A second foreign key maps the RELATED_ version of the same four columns to the same parent table.
- IGS_CA_DA_INST_PAIR_PK — the primary key constraint on the four primary alias columns.
- IGS_CA_DA_INST_PAIR_U2 / DAIP_UK — the unique index and business-key candidate over the same four columns.
Because the table carries no columns beyond its key groups and Who columns, it functions purely as a connective link; the substantive date alias definition and instance data reside in IGS_CA_DA_INST, which supplies both endpoints for every row in this table.
-
Table: IGS_CA_DA_INST_PAIR 12.2.2
Stores the pairing of two date alias instances and enables the definition of a period of time inclusive of the two date aliases
Not implemented in this database·Explore IGS module →
-
Stores the pairing of two date alias instances and enables the definition of a period of time inclusive of the two date aliases
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.