Search Results igs_fi_f_cat_fee_lbl_v




Overview
Explore in AI Chat

Overview

IGS_FI_F_CAT_FEE_LBL_V is an Oracle E-Business Suite views owned by the APPS schema within the IGS (Student System) product family, where it is classified as a VALID database object. The view is a key component of the Oracle Student System financials sub-module, exposing the fee catalogue and fee liability configuration data used to drive student fee assessment, liability tracking, and calendar-based fee determination.

Functionally, the view presents the columns of the FEE_CAT_FEE_LIABILITY table together with several derived columns that resolve the change method type, rule sequence number, and the applicable start, end, and retroactive date aliases. These additional attributes are not stored directly on the base table in all cases; instead they are resolved dynamically through the IGS_FI_GEN_001.FINP_GET_FCFL_DAI API function. The view is therefore best understood as a denormalised, presentation-layer wrapper that simplifies consumption of Fee Category/Fee Liability configuration for reporting, integration, and downstream processing logic.

Underlying Base Objects

The view is defined primarily over the fee_cat_fee_liability table, referenced in the view text by the alias FCFL. It also joins to the fee type calendar instance source, aliased FTCI, to supply fallback values for S_CHG_METHOD_TYPE and RUL_SEQUENCE_NUMBER when the corresponding columns on FCFL are null. This is achieved through NVL(FCFL.S_CHG_METHOD_TYPE, FTCI.S_CHG_METHOD_TYPE) and NVL(FCFL.RUL_SEQUENCE_NUMBER, FTCI.RUL_SEQUENCE_NUMBER), establishing a precedence rule in which the fee-category-level value overrides the calendar-instance-level value.

Date alias resolution is delegated to the PL/SQL function IGS_FI_GEN_001.FINP_GET_FCFL_DAI, which accepts a date alias name, a sequence number name, and the composite key (FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE). No referenced base objects are separately documented in the ETRM metadata, so the join structure is inferred directly from the embedded view text.

Key Columns

The view exposes both persistent and derived columns. The principal columns are:

  • FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE — the composite key identifying a fee category, calendar type, calendar instance, and fee type combination.
  • FEE_LIABILITY_STATUS — the liability status of the fee category configuration.
  • START_DT_ALIAS — the start date alias, either taken from FCFL or resolved through FINP_GET_FCFL_DAI and truncated to ten characters.
  • START_DAI_SEQUENCE_NUMBER — the sequence number associated with the start date alias. Where the base column is null, the value is derived via FINP_GET_FCFL_DAI using the keys 'START_DT_ALIAS', 'START_DAI_SEQUENCE_NUMBER', and 'START_DAI_SEQUENCE_NUMBER'.
  • END_DT_ALIAS / END_DAI_SEQUENCE_NUMBER — the equivalent end-date alias and sequence number.
  • RETRO_DT_ALIAS / RETRO_DAI_SEQUENCE_NUMBER — the retroactive date alias and sequence number.
  • S_CHG_METHOD_TYPE — the change method type, with FCFL taking precedence over FTCI.
  • RUL_SEQUENCE_NUMBER — the rule sequence number, similarly resolved with FCFL precedence.

Common Use Cases and Queries

The view is typically queried when reporting on fee liability configuration, auditing date alias resolution, or integrating Student System fee data with external systems. Because the derived columns encapsulate logic held in FINP_GET_FCFL_DAI, the view avoids the need for callers to replicate that logic.

A representative query retrieving the start date alias and sequence number for a given fee category is:

  • SELECT fee_cat, fee_cal_type, fee_type, start_dt_alias, start_dai_sequence_number FROM apps.igs_fi_f_cat_fee_lbl_v WHERE fee_cat = :p_fee_cat;
  • SELECT fee_cat, fee_type, s_chg_method_type, rul_sequence_number FROM apps.igs_fi_f_cat_fee_lbl_v ORDER BY fee_cat, fee_cal_type;
  • SELECT fee_cat, start_dt_alias, end_dt_alias, retro_dt_alias FROM apps.igs_fi_f_cat_fee_lbl_v WHERE fee_liability_status = 'A';

In 12.1.1 and 12.2.2, the view behaves consistently, relying on APPS-level synonyms and grants for access. Because the derived columns call a PL/SQL function, performance may be affected on large result sets; filtering on FEE_CAT, FEE_CAL_TYPE, or FEE_TYPE before invoking alias resolution is recommended.