Search Results igs_ca_da_configs_v

Overview

The view IGS_CA_DA_CONFIGS_V is a reporting and integration object within the Oracle E-Business Suite IGS — Student System product family, which is documented as obsolete in Release 12.1.1 and 12.2.2. Its stated purpose is to "pickup seeded system date types." In practical terms, the view exposes the configuration rows for system date types defined in IGS_CA_DA_CONFIGS, enriched with decoded lookup meanings derived from Oracle Application Object Library and IGS lookup tables.

The seeded system date types are the date categories used by the IGS calendar subsystem (the "CA" prefix denotes Calendar). These configurations drive validation procedures, calendar eligibility, and date aliasing. Because the view joins lookup definitions rather than requiring the caller to resolve codes manually, it is suited to reporting on calendar date-type setup, to integration extracts, and to diagnostic queries that verify that legitimate date types are seeded and correctly categorized.

Note that the ETRM implementation/DBA data records this view as not implemented in this database; the definition below is the documented source text, which should be validated against the target instance before reliance.

Underlying Base Objects

The documented view is defined over four base objects:

• IGS_CA_DA_CONFIGS — alias CAC; the primary configuration table holding system date type definitions.
• FND_LOOKUP_VALUES — alias L1; resolves OWNER_MODULE_CODE to a module meaning where LOOKUP_TYPE = 'IGS_MODULES', VIEW_APPLICATION_ID = 8405, SECURITY_GROUP_ID = 0, and LANGUAGE = USERENV('LANG').
• IGS_LOOKUP_VALUES — alias LK2; a mandatory join resolving RES_CAL_CAT1 against LOOKUP_TYPE = 'CAL_CAT'.
• IGS_LOOKUP_VALUES — alias LK3; an outer join resolving RES_CAL_CAT2 against LOOKUP_TYPE = 'CAL_CAT'.

The view therefore sits directly on top of the date-configuration table and performs three lookup decodes. Base objects other than these are not documented. The CAL_CAT (calendar category) lookup is the pivot for the user's search term "cal_cat."

Key Columns

• ROW_ID — the row identifier carried from IGS_CA_DA_CONFIGS.ROWID.
• SYS_DATE_TYPE — the system date type code, the primary business key.
• DESCRIPTION — descriptive text for the date type.
• OWNER_MODULE_CODE / OWNER_MODULE_DESC — the owning module and its decoded meaning from IGS_MODULES.
• VALIDATION_PROC — the validation procedure invoked for the date type.
• ONE_PER_CAL_FLAG — flag controlling whether the type may appear only once per calendar (for example, a single start date).
• RES_CAL_CAT1 / CAL_CAT1_DESC — the mandatory first restricted calendar category and its decoded CAL_CAT meaning.
• RES_CAL_CAT2 / CAL_CAT2_DESC — the optional second restricted calendar category and its decoded meaning.
• DATE_ALIAS — the alias used to reference the date type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing seeded date types, confirming calendar-category assignment, and feeding integration extracts.

• List all configured date types with categories:

  SELECT sys_date_type, description, res_cal_cat1, cal_cat1_desc,
         res_cal_cat2, cal_cat2_desc, date_alias
  FROM   igs_ca_da_configs_v
  ORDER  BY sys_date_type;

• Find date types restricted to a specific calendar category:

  SELECT sys_date_type, cal_cat1_desc
  FROM   igs_ca_da_configs_v
  WHERE  res_cal_cat1 = :cal_cat;

• Identify validation-procedure-driven types:

  SELECT sys_date_type, validation_proc, one_per_cal_flag
  FROM   igs_ca_da_configs_v
  WHERE  validation_proc IS NOT NULL;

Because the join to LK2 is mandatory, only date types with a valid CAL_CAT entry for RES_CAL_CAT1 are returned; RES_CAL_CAT2 is optional due to the outer join. Queries filtering on cal_cat values should therefore expect complete coverage of category 1 but possible nulls in category 2.