Results for “total_tariff”

6 results




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

Overview

The view IGS_HE_UT_PRS_CALCS_V belongs to the Oracle EBS Student System product family (IGS), which in release 12.1.1 and 12.2.2 is documented as obsolete/legacy and largely superseded by the Oracle Student System (OSS) and later Student Cloud offerings. Its documented purpose is to select persons together with the tariff calculation types for which the tariff calculation process has already been executed. In practice the view acts as a lightweight reporting and diagnostic layer over the tariff calculation staging tables, exposing the outcome of the calculation run alongside descriptive context.

The name itself signals its reporting role: UT denotes utility/UCAS tariff processing, PRS denotes persons, CALCS denotes the calculation records, and the _V suffix confirms a read-only database view rather than a physical table. The view is therefore typically consumed by concurrent program output, operational reports, or downstream interfaces that need to confirm which person/tariff combinations have been calculated.

Underlying Base Objects

The documented view text defines the view over two base tables joined on the tariff calculation type code:

  • IGS_HE_UT_PRS_CALCS (aliased UPC) — the person-level tariff calculation records. This table supplies the row identity, tariff calculation type code, person identifier, calculation date, and the standard EBS WHO columns (created/updated audit fields).
  • IGS_HE_UT_CALC_TYPE (aliased UCT) — the tariff calculation type lookup, which supplies the human-readable description.

The join predicate is UPC.TARIFF_CALC_TYPE_CD = UCT.TARIFF_CALC_TYPE_CD. Because the join is an inner join, only calculation records whose type code has a matching lookup row are returned. ETRM metadata records "not implemented in this database" for the sample environment and lists no additional referenced base objects, so the view has no documented dependency outside these two tables and the packaged function described below.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_HE_UT_PRS_CALCS row, useful for row-level identification and de-duplication.
  • TARIFF_CALC_TYPE_CD — the tariff calculation type code identifying which UCAS tariff calculation was run for the person.
  • PERSON_ID — the person identifier for whom the calculation was executed.
  • TARIFF_CALC_TYPE_DESC — the descriptive text for the calculation type, sourced from IGS_HE_UT_CALC_TYPE.
  • CALC_DATE — the date on which the tariff calculation was performed.
  • TOTAL_TARIFF — the calculated tariff value returned by the PL/SQL function IGS_HE_UCAS_TARIFF_PKG.TOTAL_INTERNAL_TARIFF, passed the calculation type code and person identifier. This is the column most relevant to users who searched for "total_tariff": it is the computed tariff amount produced on demand by the package, not a stored column on the base table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO audit columns inherited from IGS_HE_UT_PRS_CALCS.

Common Use Cases and Queries

The principal use case is confirming and reporting which persons have had tariff calculations run, and what total tariff each calculation produced. Because TOTAL_TARIFF invokes a packaged function per row, queries should be filtered aggressively to avoid unnecessary function execution on large person populations.

SELECT person_id,
       tariff_calc_type_cd,
       tariff_calc_type_desc,
       calc_date,
       total_tariff
FROM   igs_he_ut_prs_calcs_v
WHERE  person_id = :p_person_id
AND    tariff_calc_type_cd = :p_calc_type_cd;

For a listing of all calculation types already executed for a person:

SELECT tariff_calc_type_desc, calc_date, total_tariff
FROM   igs_he_ut_prs_calcs_v
WHERE  person_id = :p_person_id
ORDER  BY calc_date DESC;

Because the view is documented as obsolete, implementations still on 12.1.1 or 12.2.2 should treat it as a legacy artifact. Any new reporting should verify whether equivalent data is available from the current Student System product line, and total_tariff values should be validated against IGS_HE_UCAS_TARIFF_PKG logic, since the figure is derived rather than stored.