Results for “assignment_status_code”

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

Overview

IGS_FI_WAV_STD_PGMS is a transactional table within the IGS (Student System) product family of Oracle E-Business Suite, holding the records that map individual students to the fee waiver programs for which they have been enrolled or approved. In EBS terms, it functions as the operational intersection between a student/person record and a specific waiver program definition during a given fee calendar period. The application uses this table to determine which waivers apply to a student before fee assessment and to drive calculations that reduce or eliminate chargeable amounts.

From a Data Vault modeling perspective, the structure suggests this is a link entity rather than a hub or satellite. It does not merely describe an attribute of a single business key; instead, it resolves the many-to-many relationships between the student/party, the waiver program definition (via FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and WAIVER_NAME), and the assignment context. The surrogate primary key listed under IGS_FI_WAV_STD_PGMS_PK is the column WAIVER_STUDENT_ID, while a separate unique index (IGS_FI_WAV_STD_PGMS_U1) on FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, WAIVER_NAME, and PERSON_ID enforces the business rule that a given person cannot receive the same waiver under the same fee calendar type and sequence more than once.

Key Information Stored

The table carries twelve columns in the documented 12.1.1 schema. Its most significant columns are:

• WAIVER_STUDENT_ID — the surrogate primary key (IGS_FI_WAV_STD_PGMS_PK) uniquely identifying each waiver-to-student assignment row.
• PERSON_ID — foreign key to HZ_PARTIES, identifying the student or party receiving the waiver.
• FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, WAIVER_NAME — a composite business reference to the waiver program definition in IGS_FI_WAIVER_PGMS. Together they form part of the business-key candidate captured in the unique index.
• ASSIGNMENT_STATUS_CODE — the current lifecycle state of the assignment (for example, whether the waiver is active, approved, or cancelled).

The remaining columns are standard EBS audit columns: OBJECT_VERSION_NUMBER for optimistic concurrency, and CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for row-level tracking. Note the deliberate distinction: WAIVER_STUDENT_ID is a synthesized surrogate identifier, whereas the U1 index columns represent the natural business key candidates.

Common Use Cases and Queries

Reporting and processing scenarios typically resolve a student to their applicable waivers, verify eligibility against the program definition, or reconcile assessed fee adjustments. A frequent pattern joins this table to HZ_PARTIES to obtain the student identity:

• List all waiver programs assigned to a student, filtering by status and calendar.
• Identify students enrolled in a specific waiver program for a fee calendar, using the U1 columns.
• Reconcile waiver records against program definitions for audit or fee recalculation.

A representative query filters by person and active status:

SELECT w.WAIVER_STUDENT_ID, w.FEE_CAL_TYPE, w.WAIVER_NAME, w.ASSIGNMENT_STATUS_CODE
FROM IGS.IGS_FI_WAV_STD_PGMS w
WHERE w.PERSON_ID = :person_id
AND w.ASSIGNMENT_STATUS_CODE = 'ACTIVE';

Because WAIVER_NAME and the calendar columns are required for the join to the program table, they should always accompany PERSON_ID when constructing eligibility reports.

Related Objects

The following objects are most relevant based on the documented foreign keys and schema relationships:

• HZ_PARTIES — referenced via PERSON_ID; supplies the student/party identity.
• IGS_FI_WAIVER_PGMS — referenced via FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and WAIVER_NAME; holds the waiver program definitions.
• IGS_FI_WAV_STD_PGMS_PK / IGS_FI_WAV_STD_PGMS_U1 — the primary key and unique index supporting access paths and business-rule enforcement.

These relationships confirm that the table operates at the intersection of party and fee-waiver program data within the IGS fee module.