Search Results igs_he_fte_cal_prd




Overview
Explore in AI Chat

Overview

IGS_HE_FTE_CAL_PRD is a transactional setup table within the IGS (Student System) product schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its documented purpose is to store Full-Time Equivalent (FTE) calculation setup data. In the Oracle Student System, FTE calculations are used to determine the proportion of a student's enrolment that equates to a full-time load, which in turn drives funding, reporting, and statutory returns for higher-education institutions. This table therefore acts as the configuration anchor that binds an FTE calculation period to the teaching calendar period against which FTE is evaluated.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is hub-leaning. In Data Vault terms, it functions as a hub because it holds a durable, descriptive business key — the combination of FTE_CAL_TYPE and FTE_SEQUENCE_NUM — that is referenced by at least one dependent table. The classification is a modelling suggestion rather than a declarative attribute of the EBS dictionary.

Key Information Stored

The table is owned by the IGS schema and, in the documented ETRM 12.1.1 physical schema, contains nine columns. The most significant are:

  • FTE_CAL_TYPE — the FTE calendar type identifier. Part of the composite primary key and the principal business-key component.
  • FTE_SEQUENCE_NUM — the sequence number that qualifies the FTE calendar type, allowing multiple FTE calculation periods per calendar type. Also part of the composite primary key.
  • TEACH_CAL_TYPE — the teaching calendar type to which the FTE calculation period is linked.
  • TEACH_SEQUENCE_NUM — the sequence number qualifying the associated teaching calendar period.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording the last modification user, timestamp, and login session.

The surrogate primary key is enforced by the constraint IGS_HE_FTE_CAL_PRD_PK on (FTE_CAL_TYPE, FTE_SEQUENCE_NUM). A unique index, IGS_HE_FTE_CAL_PRD_U1, is defined on the same two columns, making this pair the documented business-key candidate. The remaining columns are audit and cross-reference attributes rather than key components.

Common Use Cases and Queries

Typical usage centres on identifying which FTE calculation setup applies to a given calendar period and on joining that setup to the properties defined downstream. A representative query lists all configured FTE calculation periods and their teaching calendar linkage:

  • SELECT fte_cal_type, fte_sequence_num, teach_cal_type, teach_sequence_num FROM igs.igs_he_fte_cal_prd;
  • SELECT p.fte_cal_type, p.fte_sequence_num, r.* FROM igs.igs_he_fte_cal_prd p, igs.igs_he_fte_proprt r WHERE p.fte_cal_type = r.fte_cal_type AND p.fte_sequence_num = r.fte_sequence_num;

Reporting scenarios include validating that every FTE calculation period has an associated teaching period, auditing setup changes using LAST_UPDATE_DATE, and driving FTE load calculations for statutory returns by resolving the correct FTE calendar period for an academic year. Because the table is setup rather than transactional data, query volumes are low and joins are typically driven from the child property table.

Related Objects

The documented foreign-key relationship places IGS_HE_FTE_CAL_PRD as the parent of the FTE property table:

  • IGS_HE_FTE_PROPRT — references this table via IGS_HE_FTE_PROPRT.FTE_CAL_TYPE and IGS_HE_FTE_PROPRT.FTE_SEQUENCE_NUM, holding the property values that apply to each FTE calculation period. This is the primary dependent object.
  • IGS_HE_FTE_CAL_PRD_PK — the primary key constraint over (FTE_CAL_TYPE, FTE_SEQUENCE_NUM).
  • IGS_HE_FTE_CAL_PRD_U1 — the unique index supporting the business-key candidate on the same columns.

Teaching calendar tables in the IGS schema (referenced logically through TEACH_CAL_TYPE and TEACH_SEQUENCE_NUM) and any FTE calculation or reporting processes that resolve periods by calendar type and sequence number are also significant consumers of this setup data.