Results for “igs_ps_grp_fee_trg”

46 results




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

Overview

IGS_PS_GRP_FEE_TRG is a Student System (IGS) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores program group based fee triggers, records that determine whether a program group based fee applies for a specific fee type during fee assessment processing. Each row associates a combination of fee category, fee calendar, fee type, and course group with an effective trigger, enabling the fee assessment engine to raise the correct charge when a student's program group and course enrollment match the stored criteria.

The ETRM metadata classifies this object heuristically as a link under Data Vault modeling conventions. This is a modeling suggestion rather than a physical constraint: the table's composite key draws together references to fee definitions and course/program groups, which is the characteristic pattern of a link table joining multiple business entities. It carries no descriptive attribute of its own beyond audit and effective-dating columns, reinforcing its role as an associative relationship rather than a hub or satellite.

Key Information Stored

The physical schema documents 16 columns. The most significant are:

  • FEE_CAT — Fee category, the top-level classification of the charge being assessed.
  • FEE_CAL_TYPE — Fee calendar type identifying the calendar under which the fee is defined.
  • FEE_CI_SEQUENCE_NUMBER — Calendar instance sequence number, pinning the trigger to a specific calendar instance.
  • FEE_TYPE — The fee type for which the program group based trigger applies.
  • COURSE_GROUP_CD — Course group code that qualifies the trigger; this is the program group dimension referenced in the table description.
  • CREATE_DT — Creation date, forming part of the composite key and supporting versioning of trigger definitions.

These six columns constitute the primary key, IGS_PS_GRP_FEE_TRG_PK, and are also the columns of the unique index IGS_PS_GRP_FEE_TRG_U1, meaning there is no separate single-column surrogate key — the business key is the primary key.

The remaining documented columns are audit and concurrency fields: LOGICAL_DELETE_DT, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. LOGICAL_DELETE_DT is particularly important for querying, since rows are logically retired rather than physically removed.

Common Use Cases and Queries

The primary use case is fee assessment and fee setup validation. Administrators maintain triggers here so that students in a given program or course group are charged the appropriate fee type. Reporting queries typically join to fee label definitions and course group definitions.

  • Listing active triggers for a fee type and calendar instance, filtering on LOGICAL_DELETE_DT IS NULL.
  • Auditing who created or last changed a trigger, using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
  • Diagnosing missing fee charges by confirming whether a trigger exists for the student's course group.

A representative pattern: SELECT t.fee_cat, t.fee_cal_type, t.fee_ci_sequence_number, t.fee_type, t.course_group_cd FROM igs_ps_grp_fee_trg t WHERE t.logical_delete_dt IS NULL AND t.fee_cal_type = :cal AND t.fee_ci_sequence_number = :seq;. Because the table is keyed on fee definition plus course group, point lookups are efficient when all key columns are supplied.

Related Objects

The FK metadata identifies two direct parent references, both essential for joining:

  • IGS_PS_GRP_ALL — joined on COURSE_GROUP_CD; supplies the program/course group definition.
  • IGS_FI_F_CAT_FEE_LBL_ALL — joined on FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and FEE_TYPE; supplies the fee label and fee definition context.

Beyond these, fee assessment processing in IGS reads this table alongside the broader fee calendar and fee type configuration, and the standard concurrent programs and APIs that drive fee calculation depend on the trigger rows defined here. Any change to a trigger record therefore directly affects whether students are charged the associated fee, making controlled maintenance through the application layer preferable to direct DML.