Search Results upper_range

Overview

IGS_FI_ELM_RANGE_H is an Oracle E-Business Suite view owned by the APPS schema in the IGS (Student System) product family. It exposes historical (denormalized "History" or "_H") records for element range definitions used by the Student Financials fee calculation engine. In ETRM terminology, an "element range" defines the tiered sliding-scale boundaries — such as a lower and upper income or amount threshold — that drive how a fee or charge is computed for a student or sponsor. The "_H" suffix indicates the view presents dated, versioned rows that record the state of a range definition across validity periods rather than only the current active configuration.

The view is defined purely as a filtered projection over the base table IGS_FI_ELM_RANGE_H_ALL. Its purpose in reporting and integration is to supply the range history while enforcing Multi-Org (Operating Unit) security, so that only rows belonging to the caller's organization context are returned. Calls to USERENV('CLIENT_INFO') extract the first ten characters (the ORG_ID supplied by the client session) and compare it to the ORG_ID column, applying an NVL(-99) default when neither value exists. This is a standard Oracle EBS org-strip pattern and means the view returns only rows matching the session's operating unit or rows with no org assigned. The view is documented as VALID and is intended for querying and reporting, not for direct DML.

Underlying Base Objects

The only documented base object is the table IGS_FI_ELM_RANGE_H_ALL, owned by APPS. The view performs a one-to-one column projection, renaming the table's ROWID to ROW_ID and passing the remaining attributes through unchanged. No joins to other tables are present in the view text; all enrichment, such as resolving fee calendar types or relationship types to descriptive names, must be performed by the consuming query. Because the ETRM metadata documents a single base table, foreign-key relationships are not exposed as view columns and must be derived from the base table's own constraints and the surrounding IGS_FI_ELM_* module tables.

Key Columns

• ROW_ID — The base table ROWID, usable as a unique row identifier for updates or de-duplication.
• FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — Together identify the fee and its calendar instance the range applies to.
• LOWER_RANGE and UPPER_RANGE — The tier boundaries. UPPER_RANGE is the specific column involved in the user's "upper_range" search and defines the ceiling of an element range tier.
• S_RELATION_TYPE — The student relationship type the range applies to (for example, self, spouse, or sponsor).
• RANGE_NUMBER — Sequence that orders the tiers within a given fee definition.
• FEE_CAT — The fee category grouping the range under.
• S_CHG_METHOD_TYPE — The charge method applied at that tier.
• HIST_START_DT, HIST_END_DT, HIST_WHO — Effective date window and the user who created the historical version.
• ORG_ID — The operating unit used by the row-level org security predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns for the record.

Common Use Cases and Queries

Typical use is reconciling fee calculations by inspecting the historical tier boundaries that were active on a given date, or auditing changes to an upper range over time. The org-security predicate ensures results are constrained to the current operating unit automatically.

Sample query listing historical upper ranges for a fee:

• SELECT range_number, lower_range, upper_range, s_relation_type, hist_start_dt, hist_end_dt FROM igs_fi_elm_range_h WHERE fee_type = :fee_type AND fee_cal_type = :cal_type AND fee_ci_sequence_number = :seq ORDER BY range_number, hist_start_dt;
• SELECT fee_type, fee_cat, upper_range, last_updated_by, last_update_date FROM igs_fi_elm_range_h WHERE hist_start_dt <= :as_of_date AND (hist_end_dt IS NULL OR hist_end_dt >= :as_of_date);
• SELECT range_number, upper_range, COUNT(*) FROM igs_fi_elm_range_h GROUP BY range_number, upper_range HAVING COUNT(*) > 1;

Because the view is a thin projection, queries should join back to the base IGS_FI_ELM_RANGE_H_ALL when columns outside the org-stripped projection or DML are required; the view itself is read-only and best reserved for reporting and historical analysis.