Search Results igs_pe_ev_form_stat_v




Overview

IGS_PE_EV_FORM_STAT_V is an Oracle E-Business Suite database view owned by the APPS schema and delivered as part of the IGS - Student System product family. It is a reporting and integration convenience object that surfaces the contents of the IGS_PE_EV_FORM_STAT entity together with decoded lookup meanings, so that consumers do not have to join to the lookup tables themselves. The view presents the status history of a person's event or evaluation form, recording each action taken against the form, the date of the action, and the reasons associated with program termination or completion.

The most frequently referenced derived column, ACTION_TYPE_DESC, is produced by joining the base table's ACTION_TYPE code to IGS_LOOKUP_VALUES using the lookup type PE_SV_EV_ACTION_TYPE. This makes the view particularly valuable wherever a human-readable interpretation of the recorded action is required, such as in concurrent reports, OAF pages, or inbound/outbound interface extracts.

Underlying Base Objects

The view is defined over four objects. The driving table is IGS_PE_EV_FORM_STAT, aliased PV, which supplies the primary key EV_FORM_STAT_ID, the foreign key EV_FORM_ID, and the transactional attributes. The remaining three are self-joins against IGS_LOOKUP_VALUES, aliased L1, L2 and L3, each keyed by a distinct lookup type.

The ACTION_TYPE join is an inner join, so a row is only returned when a matching lookup value exists. The TERMINATION_REASON and END_PROGRAM_REASON joins use Oracle's outer join syntax (+) against both the code and the lookup type, so records lacking a termination or end-program reason still appear, with their corresponding description columns returned as NULL.

Key Columns

  • ROW_ID - the ROWID of the base table row, provided for updatable-view and tooling purposes.
  • EV_FORM_STAT_ID - primary key of the status record.
  • EV_FORM_ID - identifies the parent event form to which the status belongs.
  • ACTION_DATE - the date on which the action was recorded.
  • ACTION_TYPE / ACTION_TYPE_DESC - the action code and its decoded meaning from PE_SV_EV_ACTION_TYPE.
  • PRGM_START_DATE / PRGM_END_DATE - program period boundaries carried on the status record.
  • TERMINATION_REASON / TERMINATION_REASON_DESC - code and decoded meaning from PE_SV_EV_TERM_REASON.
  • END_PROGRAM_REASON / END_PROGRAM_REASON_DESC - code and decoded meaning from PE_SV_EV_PRG_END_REASON.
  • REMARKS - free-text commentary on the status change.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN - standard audit columns.

Common Use Cases and Queries

This view is typically used to report the action history for a form without embedding lookup joins, and to expose status changes through interfaces where descriptive text is required. Because it includes both the coded and decoded values, it supports validation and translation scenarios equally.

To retrieve the full action history for a form:

  • SELECT ev_form_stat_id, action_date, action_type_desc, termination_reason_desc, end_program_reason_desc, remarks FROM igs_pe_ev_form_stat_v WHERE ev_form_id = :p_form_id ORDER BY action_date;

To count actions by type for a program period:

  • SELECT action_type_desc, COUNT(*) FROM igs_pe_ev_form_stat_v WHERE action_date BETWEEN :p_from AND :p_to GROUP BY action_type_desc ORDER BY 2 DESC;

Because the view already performs the lookup resolution, joins to IGS_LOOKUP_VALUES on the description columns are unnecessary and should be avoided to prevent redundant joins and duplicate rows.