Search Results igs_ad_cal_conf

Overview

The IGS_AD_CAL_CONF table is a configuration entity within the Oracle E-Business Suite, specifically designed for the now-obsolete IGS (Student System) module. Its primary role was to centralize the mapping of critical admissions process dates to specific calendar date aliases. By storing these aliases, the table provided a flexible and maintainable mechanism for the admissions subsystem to reference key milestone dates—such as application deadlines, offer response cut-offs, and period start dates—without hard-coding specific calendar entries. This abstraction allowed administrative calendars to be updated independently while maintaining the integrity of admissions workflow logic. The provided metadata explicitly notes that this table was "Not implemented in this database," indicating it may have been part of a planned but unfulfilled data model or a legacy object from an earlier version.

Key Information Stored

The table's structure is defined by a primary key, S_CONTROL_NUM, and a series of foreign key columns linking to calendar date aliases. The core data elements are the date alias references for distinct admissions events. Key columns include ADM_APPL_DUE_DT_ALIAS for the application due date, ADM_APPL_OFFER_RESP_DT_ALIAS for the applicant's offer response deadline, and ADM_APPL_COURSE_STRT_DT_ALIAS for the course commencement date. Other columns manage dates for specific process components, such as ADM_APPL_ENCMB_CHK_DT_ALIAS for encumbrance checks and ADM_APPL_CHNG_OF_PREF_DT_ALIAS for preference change deadlines. The INQ_CAL_TYPE column, a foreign key to IGS_CA_TYPE, likely designated the specific calendar type (e.g., Admissions, Academic) used for inquiry periods, providing context for the associated date aliases.

Common Use Cases and Queries

In a functional environment, this table would be queried to retrieve the current date aliases driving admissions automation. A typical use case would involve a batch process or application form logic determining if the current date is past a critical milestone. A sample query to fetch all configured date aliases for a given control number would be: SELECT adm_appl_due_dt_alias, adm_appl_offer_resp_dt_alias FROM igs_ad_cal_conf WHERE s_control_num = :1;. For reporting, a join to the IGS_CA_DA (Date Alias) table would be essential to translate the alias into an actual calendar date: SELECT cda.alias_val, cda.description FROM igs_ad_cal_conf conf, igs_ca_da cda WHERE conf.adm_appl_due_dt_alias = cda.alias_val AND conf.s_control_num = :1;. This enabled dynamic reporting on admissions timelines and deadline adherence.

Related Objects

As indicated by its foreign keys, IGS_AD_CAL_CONF has a strong dependency on the calendar architecture of the Student System. Its primary relationships are with the IGS_CA_DA (Date Alias) table, from which it draws the specific alias values for each admissions date, and the IGS_CA_TYPE (Calendar Type) table for the inquiry calendar reference. The table IGS_AD_CAL_CONF itself is the parent in these relationships. Given its configuration nature, it was likely referenced by various admissions processing packages and forms to govern deadline enforcement and period calculations. The existence of a primary key constraint, IGS_AD_CAL_CONF_PK, suggests it was designed as a controlled, singleton-style configuration table, typically containing a single record or a limited set controlling different admission cycles.