Search Results fee_category




Overview
Explore in AI Chat

Overview

IGS_FI_F_TYP_CA_INST_V is a VALID Oracle E-Business Suite database view owned by the APPS schema within the IGS (Student System) product family. It is documented in ETRM 12.2.2 and is available in both the 12.1.1 and 12.2.2 releases. Its stated purpose is to consolidate the Fee Calendar Instance tables — specifically FEE_TYPE_CAL_INSTANCE, FEE_CAT_CAL_INSTANCE, and FEE_CAT_FEE_LIABILITY — into a single, uniformly shaped result set. This structure enables a common context block in the Oracle Forms screen FINF2860, where users maintain fee type, fee category, and fee liability calendar instance data within one form. For reporting and integration purposes the view provides a normalized projection of fee calendar configuration that can be queried without navigating three separate base tables. Because the view exposes the fee calendar type, sequence number, and the fee type or fee category discriminator, it functions as a lightweight reference for fee calendar setup validation, data migration checks, and operational reporting on Student System fee configuration.

Underlying Base Objects

Three IGS base tables are referenced in the view definition, combined via UNION (not UNION ALL):

In each branch the columns not applicable to that source are projected as NULL literals, preserving a common nine-column shape. The first branch selects NULL for FEE_CATEGORY, the second selects NULL for FEE_TYPE, and the third populates both FEE_TYPE and FEE_CATEGORY from FEE_CAT_FEE_LBL. All three branches carry the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). No other referenced base objects are documented in the ETRM metadata. The UNION de-duplicates identical rows across branches, which is significant when interpreting result counts.

Key Columns

  • FEE_CAL_TYPE — the fee calendar type, the primary grouping attribute of a fee calendar instance.
  • FEE_CI_SEQUENCE_NUMBER — the calendar instance sequence, identifying a specific instance of the fee calendar type.
  • FEE_TYPE — populated from fee type calendar instance and fee liability rows; NULL on pure fee category calendar instance rows.
  • FEE_CATEGORY — populated from fee category calendar instance and fee liability rows; aliased from the FEE_CAT column in the source tables and NULL on pure fee type rows.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard audit columns inherited from each source table.

A row where both FEE_TYPE and FEE_CATEGORY are populated originates from IGS_FI_F_CAT_FEE_LBL and represents a liability relationship; a row with only FEE_TYPE originates from IGS_FI_F_TYP_CA_INST; a row with only FEE_CATEGORY originates from IGS_FI_F_CAT_CA_INST.

Common Use Cases and Queries

Typical uses include validating that fee calendar instances exist for a given fee calendar type, driving LOV-style queries in custom forms or concurrent programs, and reconciling fee type, fee category, and liability configuration across the three base tables. The following example lists all instance rows for a specific fee calendar type with an explicit row-type indicator:

  • SELECT fee_cal_type, fee_ci_sequence_number, fee_type, fee_category, CASE WHEN fee_type IS NOT NULL AND fee_category IS NOT NULL THEN 'LIABILITY' WHEN fee_type IS NOT NULL THEN 'FEE_TYPE' ELSE 'FEE_CATEGORY' END row_source FROM igs_fi_f_typ_ca_inst_v WHERE fee_cal_type = :p_cal_type ORDER BY fee_ci_sequence_number;
  • To isolate configuration for a specific fee category: SELECT fee_cal_type, fee_ci_sequence_number, fee_type FROM igs_fi_f_typ_ca_inst_v WHERE fee_category = :p_fee_cat;
  • To audit recent maintenance on fee liability rows: SELECT fee_cal_type, fee_ci_sequence_number, fee_type, fee_category, last_updated_by, last_update_date FROM igs_fi_f_typ_ca_inst_v WHERE fee_type IS NOT NULL AND fee_category IS NOT NULL AND last_update_date > SYSDATE - 30;

Because the view is a UNION over three tables, queries should always include a predicate on FEE_CAL_TYPE or a discriminator column to constrain the result set; unrestricted full scans can be costly. The view is read-only and should not be the target of DML.