Results for “calc_date”

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

Overview

The IGS_HE_UT_PRS_CALCS table resides in the IGS schema, which is the database owner for the Oracle E-Business Suite Student System (Higher Education) product family. Its documented purpose is to hold summary-level details of tariff calculations for a person. In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as a persistent store for the aggregate results of utility or tariff computation processes applied to an individual, complementing the more granular detail rows maintained elsewhere in the module. It therefore sits at the intersection of student financial processing and person (party) reference data.

From a dimensional modeling perspective, the foreign key structure suggests a satellite-leaning classification. The table is keyed to a parent business entity and appears to store descriptive or measured attributes—here, calculation summary outcomes—rather than acting as a pure hub or link. This classification is heuristic and should be treated as a modeling suggestion rather than a definitive Data Vault design.

Key Information Stored

The table is documented with eight physical columns. The most significant are:

• TARIFF_CALC_TYPE_CD — Code identifying the tariff calculation type. Part of the composite primary key and a foreign key to IGS_HE_UT_CALC_TYPE.
• PERSON_ID — Identifier of the person (party) for whom the calculation summary applies. Part of the composite primary key and a foreign key to HZ_PARTIES.
• CALC_DATE — Date on which the tariff calculation was performed, supporting time-based reporting and recalculation logic.
• CREATED_BY, CREATION_DATE — Standard audit columns capturing who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login under which it occurred.

The surrogate-style identifier is the primary key constraint IGS_HE_UT_PRS_CALCS_PK, defined over the composite of TARIFF_CALC_TYPE_CD and PERSON_ID. Because this constraint is implemented as a unique index over natural business columns rather than a single generated sequence, it also serves as the business-key candidate. The two-column uniqueness ensures one summary row per person per calculation type.

Common Use Cases and Queries

Typical scenarios include retrieving a person's consolidated tariff position, validating whether a calculation has already been run for a given type, and reporting across calculation types. A representative query joins to HZ_PARTIES to resolve the person's identity:

• Fetching all summaries for a person: SELECT tariff_calc_type_cd, calc_date FROM igs_he_ut_prs_calcs WHERE person_id = :p_person_id;
• Resolving calculation descriptions by joining IGS_HE_UT_CALC_TYPE on tariff_calc_type_cd.
• Auditing recent activity using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Reconciling summaries against detail rows in IGS_HE_UT_PRS_DTLS for the same person and calculation type.

Related Objects

• HZ_PARTIES — referenced via IGS_HE_UT_PRS_CALCS.PERSON_ID; supplies party identity.
• IGS_HE_UT_CALC_TYPE — referenced via TARIFF_CALC_TYPE_CD; defines valid calculation types.
• IGS_HE_UT_PRS_DTLS — detail table referencing this summary via TARIFF_CALC_TYPE_CD and PERSON_ID.
• IGS_HE_UT_PRS_CALCS_PK — the unique index enforcing the composite business key.