Results for “owner_module_code”

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

Overview

IGS_CA_DA_CONFIGS is a configuration table within the IGS (Student System) product family of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It resides in the IGS schema and holds the seeded system date types together with the control information that governs how each date type behaves during calendar and date validation. In practice, this table acts as the master reference for the date-type definitions used by the institution's academic calendar engine, including the rules that determine whether a date type is restricted to a single calendar, how it is validated, and how it is aliased on user-facing forms.

From a Data Vault modeling perspective, the mined classification suggests this table is hub-leaning. Its narrow, stable business key (SYS_DATE_TYPE) and its role as the anchor referenced by dependent rule tables are characteristic of a hub, with descriptive attributes such as DESCRIPTION and validation controls behaving as satellite-style attributes attached to that key.

Key Information Stored

The table is documented with 13 physical columns. The most significant are outlined below.

• SYS_DATE_TYPE — the business key and the column forming the unique index IGS_CA_DA_CONF_PK. It identifies each seeded system date type.
• DESCRIPTION — the human-readable name or meaning of the date type, used in lookups and reporting.
• OWNER_MODULE_CODE — the owning product or module code, indicating which component owns and maintains the date type.
• VALIDATION_PROC — the validation procedure invoked when the date type is processed, allowing institution-specific validation logic.
• ONE_PER_CAL_FLAG — a flag controlling whether the date type may occur only once per calendar.
• RES_CAL_CAT1 and RES_CAL_CAT2 — calendar category attributes that classify or restrict the date type to specific calendar categories.
• DATE_ALIAS — the alias used to present the date type in the user interface.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing who created and last modified the row and when.

The surrogate primary key is IGS_CA_DA_CONF_PK. The documented unique index IGS_CA_DA_CONF_PK is defined on SYS_DATE_TYPE, making that column the business-key candidate. All other columns are descriptive or audit attributes.

Common Use Cases and Queries

Typical uses center on lookup and validation: retrieving the description and alias for a date type, checking which module owns a given type, and determining whether a date type is single-per-calendar. Administrators also review the validation procedure bound to a type. A common query pattern follows:

SELECT c.sys_date_type, c.description, c.owner_module_code,
       c.one_per_cal_flag, c.date_alias
FROM   igs.igs_ca_da_configs c
WHERE  c.sys_date_type = :p_date_type;

Reporting scenarios include listing all seeded date types by owning module, joining to the override rules table to inspect the constraints applied to each type, and auditing configuration changes through the CREATED_BY and LAST_UPDATED_BY columns.

Related Objects

The principal dependent object is IGS_CA_DA_OVD_RULES, which references this table through the foreign key column SYS_DATE_TYPE, joining IGS_CA_DA_OVD_RULES.SYS_DATE_TYPE to IGS_CA_DA_CONFIGS.SYS_DATE_TYPE. This is the documented foreign-key relationship and the most significant dependency. Broader integration with the IGS calendar and date-validation infrastructure is implied by columns such as OWNER_MODULE_CODE, RES_CAL_CAT1, RES_CAL_CAT2, and VALIDATION_PROC, which tie the configuration into calendar category and validation processing. Analysts should treat IGS_CA_DA_OVD_RULES as the primary join target when tracing override behavior, and rely on the audit columns for change tracking.