Search Results census_dt_alias

Overview

IGS.IGS_GE_S_GEN_CAL_CON is a control table within the Oracle E-Business Suite Student Systems (IGS) schema. It stores the mapping between an academic period configuration record and the date aliases that define two significant calendaring milestones: the teaching period census date and the course completion cutoff date. The table is classified as belonging to the IGS General Calendar domain, and its single-row-per-control-number structure makes it a lightweight reference object consumed by calendar and enrollment processing logic.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is best modeled as a link table. It resolves two role-playing references to the date alias dimension (IGS_CA_DA) — one for census and one for course completion cutoff — against an internal sequence key. Both foreign keys target the same parent, IGS_CA_DA, distinguished only by column role, which is the classic signature of a link entity rather than a hub or satellite.

Key Information Stored

The table comprises eight documented columns. The most significant are:

• S_CONTROL_NUM — NUMBER; the internal sequence number. This is the surrogate primary key, enforced by unique index IGS_GE_S_GEN_CAL_CON_U1, which is the sole business-key candidate documented for this table.
• CENSUS_DT_ALIAS — VARCHAR2(10); the date alias representing the teaching period census. Indexed non-uniquely by IGS_GE_S_GEN_CAL_CON_N1 and carrying a foreign key reference to IGS_CA_DA.
• CRS_COMPLETION_CUTOFF_DT_ALIAS — VARCHAR2(10); the date alias representing the cutoff date for course completion within an academic period. Indexed non-uniquely by IGS_GE_S_GEN_CAL_CON_N2 and also referencing IGS_CA_DA.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns that provide audit lineage for each control row.

The two alias columns are the operational payload; they parameterize which calendar-derived dates the system treats as census and completion cutoff for the associated control record.

Common Use Cases and Queries

Because users frequently search on census_dt_alias, the most common access path is a filtered lookup by that column, which is well served by the non-unique index IGS_GE_S_GEN_CAL_CON_N1. A typical query pattern is:

• Retrieve the control record and its paired cutoff alias for a given census alias: SELECT s_control_num, census_dt_alias, crs_completion_cutoff_dt_alias FROM igs.igs_ge_s_gen_cal_con WHERE census_dt_alias = :alias;
• Resolve the actual calendar date behind an alias by joining to IGS_CA_DA on the alias value.
• Audit recently maintained control rows using LAST_UPDATE_DATE for troubleshooting calendar-driven enrollment or completion processing.
• Report all periods sharing a common completion cutoff alias to validate cutoff consistency across terms.

Typical integration scenarios include institutional reporting on census dates for regulatory returns, reconciliation of date alias configuration against the IGS_CA_DA master, and data migration validation when control records are loaded between environments.

Related Objects

The most significant related objects are derived from the documented dependency and foreign key data:

• IGS.IGS_CA_DA — the date alias master, referenced twice: via CENSUS_DT_ALIAS and CRS_COMPLETION_CUTOFF_DT_ALIAS. This is the primary lookup parent for both role-playing keys.
• APPS.IGS_GE_S_GEN_CAL_CON — the APPS-layer synonym or view through which application code and reports typically access this table.

The table does not itself reference any object other than the date alias entity, and no other documented database object references it beyond the APPS synonym. Consequently, the join surface is narrow: nearly all reporting and resolution logic flows outward to IGS_CA_DA, making that parent table the essential companion object for any query against IGS_GE_S_GEN_CAL_CON.