Results for “igs_ca_inst_rel”

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

Overview

IGS_CA_INST_REL is a relationship table within the IGS (Student System) product family of Oracle E-Business Suite. Its documented purpose is to describe the relationships among calendar instances. In the academic calendar model used by the Student System, a "calendar instance" is a concrete occurrence of a calendar type — for example, a specific academic year, term, or admission cycle. Certain calendar instances are hierarchically or functionally dependent on others, and IGS_CA_INST_REL captures those dependencies by pairing a subordinate instance with a superior instance.

The table is classified in the ETRM documentation as belonging to IGS - Student System (Obsolete). Notably, the implementation/DBA metadata states that the object is "Not implemented in this database," meaning that in the reference environment from which the ETRM extract was taken, the physical table was not present even though the design metadata is retained. This is consistent with the Obsolete designation: the object exists in the historical data model but is not actively deployed. Where it is deployed, it functions as a pure association structure between calendar instances.

From a Data Vault modeling perspective, the metadata heuristic classifies IGS_CA_INST_REL as satellite-leaning. However, its all-key primary key and its role as a connector between two instances of the same parent entity (IGS_CA_INST_ALL) suggest it is best treated as a link table capturing a many-to-many relationship among calendar instances, with satellite attributes such as LOAD_RESEARCH_PERCENTAGE carried alongside.

Key Information Stored

The table's primary key, IGS_CA_INST_REL_PK, is composed of four business-key columns rather than a generated surrogate identifier. These four columns also form the unique index IGS_CA_INST_REL_U1, confirming that the documented business key and the physical unique constraint are identical:

• SUB_CAL_TYPE — the calendar type of the subordinate (child) calendar instance in the relationship.
• SUB_CI_SEQUENCE_NUMBER — the sequence number identifying the specific subordinate calendar instance within that calendar type.
• SUP_CAL_TYPE — the calendar type of the superior (parent) calendar instance.
• SUP_CI_SEQUENCE_NUMBER — the sequence number identifying the specific superior calendar instance.

Together, these four columns define a directed edge from a subordinate instance to a superior instance. The remaining documented attributes include LOAD_RESEARCH_PERCENTAGE, which carries a numeric weighting used in student load or research-load calculations associated with the linked instances, and the standard EBS audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. Because the object is not implemented in the reference database, no active rows or runtime dependencies should be assumed.

Common Use Cases and Queries

The principal use case for this object is resolving calendar hierarchy and dependency questions: determining which admission or academic calendar instances roll up to which parent instances, and how subordinate terms relate to a superior academic year. A typical query joins the table twice to IGS_CA_INST_ALL, once for the subordinate side and once for the superior side:

• SELECT sub.CAL_TYPE, sub.CI_SEQUENCE_NUMBER, sup.CAL_TYPE, sup.CI_SEQUENCE_NUMBER FROM IGS_CA_INST_REL r JOIN IGS_CA_INST_ALL sub ON r.SUB_CAL_TYPE = sub.CAL_TYPE AND r.SUB_CI_SEQUENCE_NUMBER = sub.CI_SEQUENCE_NUMBER JOIN IGS_CA_INST_ALL sup ON r.SUP_CAL_TYPE = sup.CAL_TYPE AND r.SUP_CI_SEQUENCE_NUMBER = sup.CI_SEQUENCE_NUMBER;
• Filtering by SUP_CAL_TYPE or SUP_CI_SEQUENCE_NUMBER to list all subordinate instances of a given parent calendar.
• Reverse traversal from a subordinate instance to identify its superior instance for reporting roll-ups.
• Reporting on LOAD_RESEARCH_PERCENTAGE where research-load apportionment between linked instances is required.

Analysts migrating or auditing legacy IGS data should first verify existence of the table, since the metadata records it as not implemented.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• IGS_CA_INST_ALL — the parent calendar instance table, referenced twice via SUB_CAL_TYPE/SUB_CI_SEQUENCE_NUMBER and SUP_CAL_TYPE/SUP_CI_SEQUENCE_NUMBER.
• IGS_AD_APPL_ALL — the admissions application table, which references this table through its ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ACAD_CAL_TYPE, and ACAD_CI_SEQUENCE_NUMBER columns.
• IGS_RC_I_APPL_ALL — the recruitment/admissions application interface table, likewise referencing this table through its ADM and ACAD calendar instance columns.

These relationships establish IGS_CA_INST_REL as a low-level calendar dependency structure whose keys are surfaced in the admissions and recruitment application tables, making it relevant to any reporting that correlates application records with academic and admission calendar hierarchies.