Search Results igs_ca_da_inst

Overview

The table IGS_CA_DA_INST is a core data structure within the Oracle E-Business Suite Student System (IGS), specifically within the Calendar subsystem. Its primary function is to define and manage specific instances of date aliases within a given calendar instance. A date alias is a meaningful, user-defined label for a significant date (e.g., "TERM_START", "FEE_DUE_DATE"). This table links the abstract definition of a date alias to its concrete, actual calendar date within a specific occurrence (instance) of an academic calendar. This mapping is fundamental for driving time-sensitive processes across the student lifecycle, such as enrollment periods, fee assessments, and academic scheduling. It is critical to note that the provided metadata explicitly states this table is part of the "Student System (Obsolete)" product and was "Not implemented in this database," indicating it may be a legacy or reference object in the documented versions (EBS 12.1.1 / 12.2.2).

Key Information Stored

The table's composite primary key uniquely identifies a single date alias instance and consists of four columns: DT_ALIAS, SEQUENCE_NUMBER, CAL_TYPE, and CI_SEQUENCE_NUMBER. The DT_ALIAS and SEQUENCE_NUMBER pair references the base date alias definition from the IGS_CA_DA table. The CAL_TYPE (Calendar Type) and CI_SEQUENCE_NUMBER (Calendar Instance Sequence Number) pair references the specific calendar instance from the IGS_CA_INST_ALL table where this alias is realized. While the excerpt does not list all data columns, the structure implies the table would store the actual DATE value for the alias in this specific context, along with potential control columns like CREATION_DATE and LAST_UPDATE_DATE common to EBS tables.

Common Use Cases and Queries

The primary use case is to retrieve the actual calendar date for a named event within a specific academic term or session. For example, an interface or report needing to determine the "ADD_DROP_DEADLINE" for the "FALL-2023" semester would query this table. A typical SQL pattern involves joining to the calendar instance and date alias tables.

• Finding a Specific Date Alias Instance: SELECT dai.actual_date FROM igs_ca_da_inst dai, igs_ca_inst_all ci, igs_ca_da da WHERE dai.cal_type = ci.cal_type AND dai.ci_sequence_number = ci.ci_sequence_number AND dai.dt_alias = da.dt_alias AND dai.sequence_number = da.sequence_number AND ci.cal_type = 'SEMESTER' AND ci.alias = 'FALL-2023' AND da.dt_alias = 'ADD_DROP_DEADLINE';
• Listing All Dates for a Calendar: Reports generating a full academic calendar would join IGS_CA_DA_INST to IGS_CA_DA to get both the alias name and its concrete date for a given CAL_TYPE and CI_SEQUENCE_NUMBER.

Related Objects

IGS_CA_DA_INST sits at the center of a relational network, primarily defined by its foreign key relationships. It is a child of the calendar instance (IGS_CA_INST_ALL) and date alias definition (IGS_CA_DA) tables. Crucially, it is referenced as a parent by numerous other tables, demonstrating its role in configuring due dates and deadlines across functional areas:

• Admissions (IGS_AD_*): IGS_AD_PECRS_OFOP_DT uses it to define offer period dates.
• Calendar Logic (IGS_CA_*): IGS_CA_DA_INST_OFST defines offsets between date instances, and IGS_CA_DA_INST_PAIR defines relationships between them.
• Fees (IGS_FI_*): IGS_FI_F_CAT_CA_INST references it multiple times to configure fee category start, end, and retroactive dates within a fee calendar.

This extensive referencing confirms its purpose as a master configuration point for date-driven business rules in the obsolete Student System.