Search Results date_alias




Overview
Explore in AI Chat

Overview

The IGS_CA_DA_CONFIGS table is a core configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's Student Management product) module. It serves as the master repository for defining and managing System Date Types. These types represent specific, configurable date points within the academic calendar framework, such as "Term Start Date" or "Enrollment Deadline." The table's primary role is to provide a centralized definition for these date types, governing their validation, ownership, and relationship to calendar categories. A critical feature is its support for user-defined Date Aliases, which provide a shorthand reference for these system dates within forms and potentially other application components.

Key Information Stored

The table's structure is designed to fully define each System Date Type. The most significant columns include:

  • SYS_DATE_TYPE: The unique identifier and code for the system-defined date point (e.g., 'ENRL_DEADLINE').
  • DATE_ALIAS: A user-assigned, shorter alias (up to 10 characters) for the SYS_DATE_TYPE, enabling simplified reference in application logic and forms.
  • OWNER_MODULE_CODE: Denotes the functional module within IGS that owns and controls the date type.
  • VALIDATION_PROC: Stores the name of a database procedure responsible for validating date entries for this specific type.
  • ONE_PER_CAL_FLAG: A flag indicating whether only one instance of this date type is permitted per calendar instance.
  • RES_CAL_CAT1 and RES_CAL_CAT2: These columns restrict the calendar categories (e.g., 'ACADEMIC', 'ADMINISTRATIVE') to which the date type can be assigned.
  • DESCRIPTION: A textual description of the System Date Type's purpose.
The presence of a non-unique index (IGS_CA_DA_CONF_N1) on the DATE_ALIAS column confirms its importance as a key lookup field.

Common Use Cases and Queries

This table is primarily referenced for configuration lookups, validation, and reporting on academic calendar setups. A common use case is resolving a Date Alias to its full System Date Type within a form or report. For instance, an application form might capture a user-inputted alias, and a backend process would query this table to find the corresponding SYS_DATE_TYPE and its validation rules. A typical query pattern involves joining this configuration table with transactional tables that store actual date instances. For example, to list all configured date types with their aliases for a specific module, one might use: SELECT sys_date_type, date_alias, description, validation_proc FROM igs.igs_ca_da_configs WHERE owner_module_code = 'ENRL'; Another critical reporting use case is auditing which date types are restricted to specific calendar categories, using a query focused on RES_CAL_CAT1 and RES_CAL_CAT2.

Related Objects

The IGS_CA_DA_CONFIGS table is central to the Calendar Date Alias subsystem. It will have direct relationships with transactional tables that store concrete instances of these date types for specific academic calendars or terms. These related tables, while not named in the provided metadata, would typically have foreign keys referencing the SYS_DATE_TYPE column. The table's integrity is enforced by the unique primary key index IGS_CA_DA_CONF_PK on SYS_DATE_TYPE. Furthermore, the non-unique indexes on OWNER_MODULE_CODE (IGS_CA_DA_CONF_N2) and RES_CAL_CAT1 (IGS_CA_DA_CONF_N3) indicate performance-critical access paths for queries filtering by module ownership or primary calendar category, respectively.