Results for “effective_end_dt_alias”

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

Overview

IGS_RE_S_RES_CAL_CON is a configuration table within the Oracle E-Business Suite Student System (IGS) product family. As its description states, the entity stores information describing the System Research Calendar Configuration, meaning it holds the controlling parameters that govern how research-related academic calendars are defined and applied across an institution's student records. In EBS 12.1.1 and 12.2.2 this object resides in the IGS schema and is fully validated.

Heuristically, the foreign-key structure — two references from date-alias columns back to the IGS_CA_DA calendar date/alias table — indicates a Data Vault link classification. This is a modeling suggestion: the table behaves as an associative record binding configuration surrogates to date semantic aliases rather than acting as a standalone hub or descriptive satellite.

Key Information Stored

The physical schema (ETRM 12.1.1) documents eight columns. The most operationally significant are:

• S_CONTROL_NUM — the single-column surrogate primary key (IGS_RE_S_RES_CAL_CON_PK) and also the unique business-key candidate (IGS_RE_S_RES_CAL_CON_U1). It identifies each research calendar configuration record.
• EFFECTIVE_STRT_DT_ALIAS — a foreign-key reference to IGS_CA_DA defining the alias used for the configuration's effective start date.
• EFFECTIVE_END_DT_ALIAS — a foreign-key reference to IGS_CA_DA defining the alias for the effective end date.
• CREATED_BY / CREATION_DATE — WHO columns capturing the creating user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — WHO columns recording the most recent modifier and modification timestamp.
• LAST_UPDATE_LOGIN — the login session associated with the last update, used for audit and concurrency diagnostics.

No descriptive name or free-text column is documented, so the effective date aliases together with S_CONTROL_NUM constitute the meaningful business content of each row.

Common Use Cases and Queries

Administrators and developers consult this table when troubleshooting research calendar behavior, verifying which date aliases are bound to a configuration, or auditing changes made through the Standard Date Alias and configuration setup forms. Typical reporting extracts the effective date aliases and joins them to IGS_CA_DA to resolve the alias meaning.

• Configuration lookup: SELECT S_CONTROL_NUM, EFFECTIVE_STRT_DT_ALIAS, EFFECTIVE_END_DT_ALIAS FROM IGS.IGS_RE_S_RES_CAL_CON WHERE S_CONTROL_NUM = :p_control_num;
• Resolving aliases: join both alias columns to IGS_CA_DA to retrieve the underlying date descriptors for each configuration record.
• Audit reporting: query on LAST_UPDATE_DATE and LAST_UPDATED_BY to enumerate recently modified research calendar configurations.

Because the table is small configuration data, queries are inexpensive and are usually embedded in validation logic or setup verification scripts rather than bulk reporting.

Related Objects

The FK relationships named in the ETRM metadata identify IGS_CA_DA as the principal referenced object, reached through two distinct alias columns:

• IGS_CA_DA — joined via IGS_RE_S_RES_CAL_CON.EFFECTIVE_STRT_DT_ALIAS.
• IGS_CA_DA — joined via IGS_RE_S_RES_CAL_CON.EFFECTIVE_END_DT_ALIAS.

These references make IGS_CA_DA the primary dependent lookup table for alias resolution. Other IGS research calendar and configuration tables that consume S_CONTROL_NUM as a reference key are potential dependents, though such child relationships are not enumerated in the supplied metadata. Implementers should confirm any additional references through the data dictionary before extending joins.