Search Results end_dai_sequence_number




Overview
Explore in AI Chat

Overview

APPS.IGS_FI_F_CAT_FEE_LBL_V is a financials view within the Oracle E-Business Suite (EBS) Student System (IGS) schema, specifically belonging to the Fees and Charges (IGS_FI) functional area. It exposes a consolidated, label-resolved representation of fee category configuration for a given fee calendar type, fee calendar instance, and fee type combination. Its principal role is to present student fee configuration data in a form suitable for reporting, concurrent processing, and integration with downstream fee calculation and billing logic.

The view is particularly significant because it resolves aliases and sequencing attributes for date indicators — start, end, and retroactive — by invoking the database function IGS_FI_GEN_001.finp_get_fcfl_dai. This function derives the applicable Date Alias Instance (DAI) attributes when they are not explicitly stored on the underlying configuration record. As a result, the view provides a complete, self-sufficient picture of fee labelling and scheduling semantics without requiring callers to implement their own resolution logic.

The name IGS_FI_F_CAT_FEE_LBL_V indicates its purpose: a Fees (F) Calendar (CAT) Fee (FEE) Label (LBL) View (V). It is a read-only object; no DML should be issued against it.

Underlying Base Objects

The ETRM metadata for this object documents no explicitly referenced base objects, classifying the referenced base object list as empty. However, the view text itself reveals its dependencies. The primary base object is the fee calendar fee liability table (aliased fcfl), which supplies fee category, fee calendar type, fee calendar instance sequence number, fee type, fee liability status, change method type, rule sequence number, payment hierarchy rank, currency derivation inputs, and audit columns. A secondary source, aliased ftci (the fee type calendar instance table), contributes fallback values for s_chg_method_type, rul_sequence_number, payment_hierarchy_rank, and scope through NVL expressions.

In addition, the view depends on the PL/SQL function IGS_FI_GEN_001.finp_get_fcfl_dai, which is called three times to resolve start, end, and retroactive date alias and DAI sequence values. It also calls IGS_FI_GEN_001.finp_get_currency to obtain the applicable currency code for each fee configuration row. These dependencies mean the view's performance is influenced by the efficiency of those functions, and any change to their signatures or behaviour can affect view results.

Key Columns

  • FEE_CAT, fee_cal_type, fee_ci_sequence_number, FEE_TYPE — the composite key identifying the fee category, calendar type, calendar instance, and fee type.
  • start_dt_alias, start_dai_sequence_number — resolved start date alias and its sequence number. The NVL fallback invokes finp_get_fcfl_dai with 'START_DT_ALIAS' and 'START_DAI_SEQUENCE_NUMBER'.
  • end_dt_alias, end_dai_sequence_number — end date alias and its sequence number, resolved via the same function using the 'END_DT_ALIAS' and 'END_DAI_SEQUENCE_NUMBER' parameters.
  • retro_dt_alias, retro_dai_sequence_number — retroactive date alias and its sequence number, resolved using 'RETRO_DT_ALIAS' and 'RETRO_DAI_SEQUENCE_NUMBER'.
  • s_chg_method_type, rul_sequence_number, payment_hierarchy_rank — change method, rule sequence, and payment hierarchy, each falling back to the ftci source when the fcfl value is null.
  • currency_cd — the currency code derived through finp_get_currency and truncated to 15 characters.
  • SCOPE — sourced from the ftci object, indicating the scope of the fee configuration.
  • created_by, creation_date, last_updated_by, last_update_date, last_update_login — standard audit columns for change tracking.

Common Use Cases and Queries

A typical application of this view is to report fee configuration with fully resolved date aliases, particularly when auditing which date alias and sequence number governs a fee's start, end, or retroactive application — the exact concern raised by the search term start_dai_sequence_number.

Sample query to list resolved date indicator data for a fee:

  • SELECT fee_cat, fee_cal_type, fee_ci_sequence_number, fee_type, start_dt_alias, start_dai_sequence_number, end_dt_alias, end_dai_sequence_number FROM apps.igs_fi_f_cat_fee_lbl_v WHERE fee_cal_type = :p_cal_type AND fee_ci_sequence_number = :p_seq;

This view is also useful for validating that fallback resolution logic produces the expected aliases when the stored fcfl values are null, and for populating integration payloads where currency, payment hierarchy, and change method must accompany the fee definition.