Results for “fee_liability_status”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_FI_F_CAT_F_LBL_H_ALL table is a core historical entity within the Oracle E-Business Suite Student System (IGS) product family, residing in the IGS schema. It records the history of changes to a fee category fee liability, capturing the audit trail of how fee liability assignments evolved across fee calendars, fee categories, and fee types. During upgrade or audit review at both 12.1.1 and 12.2.2, the table is reported as VALID with 19 columns in the documented ETRM 12.1.1 physical schema.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure identifies this object as standalone. This suggests that the table functions primarily as a self-contained record set rather than participating in a network of dependent hubs and links. In practice, the table behaves like a satellite-style history store: it maintains multiple version rows per business entity, delimited by validity dates, without enforcing downstream dependent relationships.

Key Information Stored

The surrogate primary key is IGS_FI_F_CAT_F_LBL_H_PK, composed of FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE, and HIST_START_DT. The unique index IGS_FI_F_CAT_F_LBL_H_ALL_U1 carries the identical composite column list, confirming the business-key candidate that distinguishes each historical version.

• FEE_CAT — the fee category identifier for which liability history is tracked.
• FEE_CAL_TYPE — the fee calendar type scoping the liability record.
• FEE_CI_SEQUENCE_NUMBER — the calendar instance sequence number bound to the fee calendar.
• FEE_TYPE — the fee type to which the liability applies.
• HIST_START_DT / HIST_END_DT — validity window for each historical version.
• HIST_WHO — the database user or process credited with the change.
• FEE_LIABILITY_STATUS — the liability state captured within that version window.
• START_DT_ALIAS, START_DAI_SEQUENCE_NUMBER — aliasing metadata for the start-date reference.
• S_CHG_METHOD_TYPE, RUL_SEQUENCE_NUMBER — change method and rule linkage.
• PAYMENT_HIERARCHY_RANK — rank governing payment hierarchy behavior.
• ORG_ID — operating unit / multi-org security discriminator.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include reporting on liability changes over time, reconstructing the liability state effective on a given date, auditing who altered a liability and when, and reconciling historical records against current liability tables.

Point-in-time query example:

• SELECT fee_cat, fee_type, fee_liability_status, payment_hierarchy_rank FROM igs_fi_f_cat_f_lbl_h_all WHERE fee_cal_type = :cal AND fee_ci_sequence_number = :seq AND hist_start_dt <= :as_of AND (hist_end_dt IS NULL OR hist_end_dt > :as_of);

Audit-trail query example:

• SELECT hist_start_dt, hist_end_dt, hist_who, fee_liability_status FROM igs_fi_f_cat_f_lbl_h_all WHERE fee_cat = :cat AND fee_type = :type ORDER BY hist_start_dt DESC;

Because ORG_ID is present, multi-org secured reporting should always filter by the appropriate operating unit.

Related Objects

The metadata documents no explicit foreign keys, consistent with its standalone classification. Functional relationships can nonetheless be inferred from the column semantics shared with the core fee liability hierarchy:

• IGS_FI_F_CAT_F_LABELS — likely the current/active counterpart whose changes this history table records; joins on FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE.
• IGS_FI_FEE_CATEGORIES / fee category base tables — source of FEE_CAT validation.
• IGS_FI_FEE_CALENDARS and calendar instance tables — source of FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER.
• IGS_FI_FEE_TYPES — source of FEE_TYPE.
• IGS_FI_F_CAT_F_LBL_H_PK — the primary key constraint object itself, referenced in constraint-driven validation.

The object is typically accessed through the IGS Student System fee configuration and liability maintenance screens, PL/SQL history-maintenance routines, and concurrent reporting programs.