Search Results s_chg_method_type




Overview
Explore in AI Chat

Overview

IGS_FI_F_CAT_F_LBL_H is an APPS-owned, VALID database view within the IGS (Student System) product family of Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. The view exposes historical fee liability and charge method configuration data maintained by the Student Financials module, specifically the historical records governing fee categories and their associated fee liability labelling rules. Its name follows the IGS naming convention: FI denotes Financials, F_CAT_F_LBL identifies the fee category/fee liability entity, and the trailing H indicates a history-enabled (_H) variant surface.

Functionally, the view presents the current-row projection of the underlying _ALL history table, applying Oracle's Multi-Org (Operating Unit) security predicate so that a session retrieves only rows matching the operating unit in its CLIENT_INFO context. It is principally used in reporting, concurrent programs, and integration extracts where historical fee liability configuration must be queried under the caller's organizational context. The user search term payment_hierarchy_rank corresponds directly to the PAYMENT_HIERARCHY_RANK column exposed by this view, which orders or prioritizes fee liability rows within the payment allocation hierarchy.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view definition itself explicitly selects from a single base object: IGS_FI_F_CAT_F_LBL_H_ALL. This is the history-enabled, Multi-Org (_ALL) table that stores dated fee category/fee liability label records for every organization. The view is therefore a security-filtered, column-aliased projection over that table rather than a join or aggregate.

The view text aliases ROWID as ROW_ID, exposes each business column directly, and appends the Organization ID (ORG_ID) plus the standard WHO columns. Critically, it does not perform any date-effective filtering on HIST_START_DT and HIST_END_DT; those columns are simply returned so that callers can apply their own effective-date logic. The only transformation applied is the Multi-Org security predicate, which resolves ORG_ID by decoding the first ten characters of the USERENV('CLIENT_INFO') session value, defaulting to -99 when no operating unit is set.

Key Columns

  • PAYMENT_HIERARCHY_RANK — The rank or priority assigned to a fee liability rule within the payment allocation hierarchy; central to the user's query and to determining the order in which a student's payments are applied against outstanding fee liabilities.
  • FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE — The fee category, calendar type, calendar instance sequence, and fee type that jointly identify the fee configuration to which the liability label rule belongs.
  • FEE_LIABILITY_STATUS — Indicates the fee liability status associated with the labelled configuration.
  • S_CHG_METHOD_TYPE — The system charge method type governing how the fee is charged.
  • START_DT_ALIAS, START_DAI_SEQUENCE_NUMBER, RUL_SEQUENCE_NUMBER — The start date alias, its sequence number, and the rule sequence number that scope the rule definition.
  • HIST_START_DT, HIST_END_DT, HIST_WHO — History/effective-dating columns recording when the row became and ceased to be effective and who created the version.
  • ORG_ID — Operating unit identifier used by the Multi-Org security predicate.
  • ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard row identifier and audit columns.

Common Use Cases and Queries

The primary use case is retrieving the payment hierarchy ranking for fee liability rules within a specific fee category and calendar context, typically for reconciliation, configuration review, or extract feeds consumed by downstream charging engines.

To list all liability rules for a fee category ordered by their payment hierarchy rank:

  • SELECT fee_cat, fee_type, payment_hierarchy_rank, fee_liability_status, s_chg_method_type
  • FROM apps.igs_fi_f_cat_f_lbl_h
  • WHERE fee_cat = :p_fee_cat
  • AND fee_cal_type = :p_cal_type
  • ORDER BY payment_hierarchy_rank;

To isolate the version effective on a given date, callers must apply explicit history filtering, since the view returns all history rows:

  • SELECT fee_cat, payment_hierarchy_rank, hist_start_dt, hist_end_dt
  • FROM apps.igs_fi_f_cat_f_lbl_h
  • WHERE TRUNC(:p_effective_date) BETWEEN hist_start_dt AND NVL(hist_end_dt, TRUNC(:p_effective_date))
  • ORDER BY payment_hierarchy_rank;

Because the Multi-Org predicate is embedded in the view, sessions must initialize CLIENT_INFO (or use MO_GLOBAL/ORG context APIs) before querying, otherwise the predicate resolves to -99 and returns only rows with an ORG_ID of -99.