Results for “igsbv_cal_prd_evnt_typ_configs”

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

Overview

The IGSBV_CAL_PRD_EVNT_TYP_CONFIGS view is a Student System (IGS) database object that exposes the seeded system date types used for date type configurations within the Academic Calendar and Period/Event Type setup. The IGS product family falls under the Oracle Student System, which is designated as obsolete in current Oracle EBS documentation, meaning it is retained for backward compatibility with legacy implementations but is no longer actively enhanced.

The view's central purpose is to present the seeded (system-defined) date-type configurations that drive calendar period and event type processing. Each row represents a system date type together with its validation procedure, calendar frequency constraints, and descriptive alias information. The view is annotated as read-only (WITH READ ONLY), confirming that it functions strictly as a reporting and inquiry surface rather than a maintenance interface. The column of interest to users searching for "system_date_type_desc" — SYSTEM_DATE_TYPE_DESC — is the user-facing description of each system date type and is derived from the DA.DESCRIPTION column of the underlying configuration table. The view also embeds Oracle EBS label-substitution tokens (the "_LA:" prefixed columns), which resolve lookup meanings at runtime through the IGS_LOOKUP_VALUES and IGS_MODULES lookup infrastructure.

Underlying Base Objects

The view is defined over a single base table: IGS_CA_DA_CONFIGS, aliased as DA in the view text. No other base objects are documented in the ETRM metadata beyond the lookup sources referenced by the label-substitution expressions. Specifically, the "_LA:" expressions reference IGS_LOOKUP_VALUES (joined against lookup types IGS_MODULES and CAL_CAT) to translate coded values into descriptive meanings. The base table IGS_CA_DA_CONFIGS stores calendar date-alias configurations, including both seeded system date types and any user-defined configurations. Because the view is restricted to seeded system date type configurations, it effectively acts as a filtered presentation layer over the configuration table. No database implementation is documented for this view in the ETRM record, which indicates the view may not exist in every environment and should be validated against the target database before use.

Key Columns

• SYSTEM_DATE_TYPE — The internal code identifying the seeded system date type.
• _LA:OWNER_MODULE — The owning module, resolved to its descriptive meaning via IGS_LOOKUP_VALUES/IGS_MODULES.
• VALIDATION_PROCEDURE — The stored procedure that validates dates created against this date type.
• ONE_PER_CAL_FLAG — Indicates whether the date type is restricted to one occurrence per calendar.
• _LA:RESTRICTED_CAL_CATEGORY and _LA:ALTERNATE_CAL_CATEGORY — Calendar category restrictions and alternates, resolved through the CAL_CAT lookup type.
• DATE_ALIAS — The alias assigned to the date within calendar processing.
• SYSTEM_DATE_TYPE_DESC — The descriptive text for the system date type, mapped from the base table's DESCRIPTION column; this is the column referenced by users searching for "system_date_type_desc".
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns recording who created and last modified each configuration row, and when.

Common Use Cases and Queries

This view is typically queried to review which system date types are seeded, what validation logic they invoke, and which calendar categories they are restricted to. Typical usage includes calendar setup analysis, migration verification, and troubleshooting date-type behavior in period and event type configuration. A representative query follows:

SELECT system_date_type,
       system_date_type_desc,
       validation_procedure,
       one_per_cal_flag,
       date_alias
FROM   igsbv_cal_prd_evnt_typ_configs
ORDER  BY system_date_type;

Because the view is read-only and may not be implemented in all databases, environments should confirm its existence in ALL_VIEWS before relying on it in custom reports or integrations. Where it is unavailable, the equivalent result can be obtained by querying IGS_CA_DA_CONFIGS directly and resolving the lookup meanings through IGS_LOOKUP_VALUES.