Results for “igs_fi_elm_range_rt”

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

Overview

IGS_FI_ELM_RANGE_RT is a transactional table in the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores charge rate information that applies to a defined range of charge elements, allowing the fee engine to calculate amounts that vary according to the position of an element within a range rather than applying a single flat rate. In practical terms, it defines the pricing tiers used when a fee is assessed against a scalable quantity such as credit hours, units, or other range-bearing attributes.

The table resides in the IGS schema and carries a documented primary key, IGS_FI_ELM_RANGE_RT_PK, on the ERR_ID column, supported by the unique index IGS_FI_ELM_RANGE_RT_U1. The documented physical schema contains 19 columns. Because the table is keyed by a surrogate identifier and holds descriptive rate attributes together with a foreign key to the charge-as-rate parent, the ETRM metadata's data vault classification heuristic describes it as satellite-leaning — a modeling suggestion that positions it as a descriptive child table hanging off a rate-defining parent rather than as an independent hub or a pure association link.

Key Information Stored

The most significant columns fall into three groups: identity, range definition, and audit control.

• ERR_ID — the surrogate primary key, uniquely identifying each range-rate row. This is also the single documented business-key candidate via the unique index IGS_FI_ELM_RANGE_RT_U1.
• FEE_TYPE — foreign key to IGS_FI_FEE_AS_RATE; identifies the charge-as-rate definition that owns this range detail.
• FEE_CAL_TYPE — the fee calendar type under which the rate is valid, typically a term-based calendar.
• FEE_CI_SEQUENCE_NUMBER — the calendar instance sequence, tying the range to a specific term or period.
• S_RELATION_TYPE — the student relation type (for example, a residency or cohort classification) against which the rate applies.
• RANGE_NUMBER — the ordinal position of this row within the range of charge elements.
• RATE_NUMBER — the rate identifier associated with the range entry.
• FEE_CAT — the fee category to which the element belongs.
• LOGICAL_DELETE_DT — soft-delete marker; rows are logically removed rather than physically purged.
• CREATE_DT — the effective creation date of the range record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-columns for auditing authorship and change history.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context columns captured when the row is populated or updated by a batch process.

Common Use Cases and Queries

Range-rate data is used principally for fee assessment, billing, and audit reporting. A frequent pattern joins the child rows back to their parent rate definition to reconstruct the full pricing rule for a given term and relation type:

• Retrieve all range entries for a charge-as-rate definition:
  SELECT err.range_number, err.rate_number, err.fee_cat, err.create_dt FROM igs.igs_fi_elm_range_rt err WHERE err.fee_type = :fee_type AND err.fee_cal_type = :cal_type AND err.fee_ci_sequence_number = :seq AND err.s_relation_type = :rel_type ORDER BY err.range_number;
• Join to the parent rate table to display the description of the owning rate:
  SELECT err.range_number, err.rate_number, r.description FROM igs.igs_fi_elm_range_rt err, igs.igs_fi_fee_as_rate r WHERE r.fee_type = err.fee_type AND r.fee_cal_type = err.fee_cal_type AND r.fee_ci_sequence_number = err.fee_ci_sequence_number AND r.s_relation_type = err.s_relation_type AND r.rate_number = err.rate_number;
• Identify active (non-deleted) range rows for reporting or reconciliation:
  SELECT * FROM igs.igs_fi_elm_range_rt WHERE logical_delete_dt IS NULL;
• Trace batch-loaded records by concurrent request for load audits:
  SELECT * FROM igs.igs_fi_elm_range_rt WHERE request_id = :request_id ORDER BY creation_date;

Typical reporting scenarios include fee structure validation prior to term activation, reconciliation of assessed charges against configured range tiers, and troubleshooting of assessment errors caused by gaps or overlaps in range definitions.

Related Objects

The most significant related objects, based on the documented foreign key relationship and typical IGS fee-modeling dependencies, are:

• IGS_FI_FEE_AS_RATE — the primary parent table. Joined on FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, S_RELATION_TYPE, and RATE_NUMBER; this is the sole documented foreign key target for IGS_FI_ELM_RANGE_RT.
• IGS_FI_ELM_RANGE_RT_PK — the primary key constraint enforcing uniqueness of ERR_ID.
• IGS_FI_ELM_RANGE_RT_U1 — the unique index on ERR_ID providing the documented business-key candidate.
• Fee calendar and calendar instance definitions (IGS_CA_* tables) referenced through FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER for term validation.
• Student relation type reference data used to validate S_RELATION_TYPE values.
• Fee category reference data used to validate FEE_CAT.
• Fee assessment and charge calculation routines that consume range rates during student fee computation.

Because range definition is inseparable from the rate it modifies, any query against this table should be prepared to join back to IGS_FI_FEE_AS_RATE using the full composite key rather than FEE_TYPE alone.