Search Results igs_modules

Overview

The view APPS.IGS_CA_DA_CONFIGS_V belongs to the Oracle E-Business Suite (EBS) Student System / Student Information management product family, where the IGS prefix denotes objects owned by the Student System schema. In the context of EBS 12.1.1 and 12.2.2, this view exposes configuration records that govern how system date types are defined and validated within the calendaring subsystem. It is a denormalized, presentation-oriented view that joins configuration data to Oracle EBS lookup definitions so that consumers see descriptive meanings rather than raw, uninterpreted codes.

The view is particularly relevant to users searching on igs_modules, because one of its join predicates explicitly filters lookup values where LOOKUP_TYPE = 'IGS_MODULES'. This lookup type enumerates the modules of the Student System that may "own" a given date configuration, enabling the view to translate the stored OWNER_MODULE_CODE into a human-readable module description. The view therefore serves as a reporting and integration surface over date-configuration metadata, allowing concurrent programs, Oracle Reports, Oracle Forms LOVs, and custom integrations to resolve codes to meanings without embedding lookup logic themselves.

Because the view is defined in the APPS schema, it is subject to standard EBS multi-language and security-group conventions: lookup resolution is constrained by USERENV('LANG') for the caller's session language, by VIEW_APPLICATION_ID = 8405, and by SECURITY_GROUP_ID = 0.

Underlying Base Objects

The documented view metadata for 12.2.2 lists no formally recorded base objects; the authoritative source is the view SQL text. That text references four objects:

• IGS_CA_DA_CONFIGS CAC — the driving table holding one row per date-type configuration, including the owner module, validation procedure, and calendar category references.
• FND_LOOKUP_VALUES L1 — the standard Oracle Application Object Library lookup view, joined on OWNER_MODULE_CODE = LOOKUP_CODE with LOOKUP_TYPE = 'IGS_MODULES', VIEW_APPLICATION_ID = 8405, SECURITY_GROUP_ID = 0, and language filtering.
• IGS_LOOKUP_VALUES LK2 — the Student System lookup view, joined on RES_CAL_CAT1 with LOOKUP_TYPE = 'CAL_CAT' to resolve the primary resource calendar category.
• IGS_LOOKUP_VALUES LK3 — the same lookup view, outer-joined on RES_CAL_CAT2 and LOOKUP_TYPE = 'CAL_CAT', permitting configurations with no secondary category.

Consequently, the view is a four-way join whose primary key behavior is governed by IGS_CA_DA_CONFIGS, with the ROWID of that table carried through as ROWID.

Key Columns

• ROWID — identifier of the underlying configuration row, useful for direct updates or row-based navigation.
• SYS_DATE_TYPE / DESCRIPTION / DATE_ALIAS — the configured system date type, its description, and an alternate alias.
• OWNER_MODULE_CODE — the Student System module that owns the configuration; resolved to L1.MEANING via the IGS_MODULES lookup.
• VALIDATION_PROC — the PL/SQL validation routine invoked when the date type is processed.
• ONE_PER_CAL_FLAG — flag indicating whether the date type may appear only once per calendar.
• RES_CAL_CAT1 / LK2.MEANING and RES_CAL_CAT2 / LK3.MEANING — required and optional resource calendar categories with their resolved meanings.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating configuration coverage per module, listing validation procedures, and feeding calendaring setup reports. A representative query filters by owner module:

• SELECT owner_module_code, meaning, sys_date_type, description, validation_proc FROM apps.igs_ca_da_configs_v WHERE owner_module_code = :module_code;
• SELECT sys_date_type, res_cal_cat1, lk2.meaning, res_cal_cat2 FROM apps.igs_ca_da_configs_v WHERE one_per_cal_flag = 'Y';
• SELECT meaning AS module, COUNT(*) FROM apps.igs_ca_da_configs_v GROUP BY meaning ORDER BY module;

These patterns support audit of module-owned date configurations and dependency checks on the CAL_CAT lookup values referenced by each record.