Results for “igs_ca_stat”

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

Overview

The IGS_CA_STAT table resides in the IGS (Student System) product family, a module documented in the Oracle E-Business Suite 12.1.1 and 12.2.2 electronic technical reference manuals as obsolete. The table stores user-defined calendar statuses and, critically, defines the mapping between those user-defined values and the system-defined calendar statuses recognized by the application. Calendar statuses control the lifecycle state of an academic calendar instance — for example, whether a calendar is active, closed, or otherwise restricted — and therefore influence validation rules applied throughout the Student System when academic periods are processed.

The ETRM note "Not implemented in this database" indicates that the table is not instantiated in a standard EBS installation; it exists only where the legacy IGS Student System has been deployed. Practitioners encountering this object should confirm module licensing and installation status before relying on it. In modeling terms, the heuristic Data Vault classification mined from the foreign-key structure is hub-leaning: the table behaves like a reference hub, holding a durable, uniquely keyed set of calendar status codes that other entities reference. This classification is a suggestion for analytical modeling rather than a statement of physical design.

Key Information Stored

The documented physical schema contains nine columns owned by the IGS schema:

• CAL_STATUS — the primary key column, serving as the business key. It is enforced by the unique index IGS_CA_STAT_U1 and is the column referenced by foreign keys in dependent tables.
• DESCRIPTION — the user-facing description of the calendar status, used for display and reporting.
• S_CAL_STATUS — the system-defined calendar status to which the user-defined status maps. This mapping column is the functional core of the table, since it translates installation-specific vocabulary into the values the application logic understands.
• CLOSED_IND — a flag indicating whether the status represents a closed or inactive calendar condition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified each row, when, and through which login session.

The primary key constraint is IGS_CA_STAT_PK, and the business-key candidate is CAL_STATUS, confirmed by the unique index IGS_CA_STAT_U1 on the same column. Because no separate surrogate column is documented, CAL_STATUS acts as both the business key and the physical key.

Common Use Cases and Queries

Typical usage centers on resolving user-defined statuses into system values for validation and reporting:

• Listing all defined statuses with their system mappings:
  SELECT cal_status, description, s_cal_status, closed_ind FROM igs_ca_stat;
• Identifying open versus closed statuses for filtering calendar instances:
  SELECT cal_status, description FROM igs_ca_stat WHERE closed_ind = 'N';
• Joining to calendar instances to report the status of each academic calendar:
  SELECT i.calendar_id, i.cal_status, s.description FROM igs_ca_inst_all i, igs_ca_stat s WHERE i.cal_status = s.cal_status;
• Auditing recently modified status definitions using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the module is obsolete, these queries are most relevant to historical data extraction, migration assessment, and documentation of legacy configurations.

Related Objects

The most significant dependent object is IGS_CA_INST_ALL, the calendar instance table, which references IGS_CA_STAT through the column IGS_CA_INST_ALL.CAL_STATUS joined to IGS_CA_STAT.CAL_STATUS. This relationship means every calendar instance carries a status that must resolve against this reference table. Beyond this documented foreign key, the table's role as a reference hub implies dependencies from validation logic and concurrent programs within the Student System that interpret calendar status codes. Administrators and analysts working with legacy IGS data should treat IGS_CA_STAT as the authoritative lookup for calendar status vocabulary and join it whenever calendar instance status must be rendered or filtered.