Search Results ev_form

Overview

IGS_PE_EV_FORM_STAT_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Student System / Student Records intelligence area, specifically the person "Exchange Visitor" (EV) form functionality used to track J-1 exchange visitor status records for students and scholars. The view surfaces the status history of an exchange visitor form (identified by EV_FORM_ID), capturing discrete status actions such as program start, program end, transfers, and terminations, together with their effective dates and associated reason codes.

Oracle classifies this object as a "supplementary view used to simplify forms coding." As the ETRM documentation explicitly warns, Oracle does not recommend querying or altering data through this view, because its structure may change dramatically in subsequent minor or major releases. This distinguishes it from the underlying base table, IGS_PE_EV_FORM_STAT, which is the sanctioned persistence object. The view nonetheless remains widely referenced in custom reports and data extracts because it conveniently resolves lookup meaning descriptions at query time, sparing developers from writing the lookup joins themselves.

Underlying Base Objects

The view is defined over the following documented objects: APPS.IGS_PE_EV_FORM_STAT (the primary base table storing exchange visitor form status records), and APPS.IGS_LOOKUP_VALUES (the generic Oracle lookup table used to resolve code-to-description pairs). The ETRM dependency list also notes an APPS.IG reference, indicating a lookup view or synonym associated with the IGS lookup framework. Each row in IGS_PE_EV_FORM_STAT corresponds to one status action taken against an exchange visitor form; the view joins these rows to lookup values so that ACTION_TYPE, TERMINATION_REASON, and END_PROGRAM_REASON codes are returned alongside their human-readable descriptions.

Because the view performs decode/join logic against IGS_LOOKUP_VALUES, it is a read-only presentation layer. No DML is permitted. The base table carries the standard Oracle "Who" audit columns, which are propagated unchanged into the view.

Key Columns

• ROW_ID (ROWID) — the physical row identifier of the underlying base-table row.
• EV_FORM_STAT_ID (NUMBER, 15) — the unique primary key for the status record; the primary join target for downstream queries.
• EV_FORM_ID (NUMBER, 15) — foreign key to the exchange visitor form for the student; the attribute that groups all status actions belonging to one form.
• ACTION_DATE (DATE) — the effective date on which the status action was taken.
• ACTION_TYPE / ACTION_TYPE_DESC — the coded action (for example program start, program end, termination) and its decoded lookup description (up to 80 characters).
• PRGM_START_DATE / PRGM_END_DATE (DATE) — the Exchange Visitor Program start and end dates applicable to the record.
• TERMINATION_REASON / TERMINATION_REASON_DESC — the coded and decoded reason for terminating the visitor's participation.
• END_PROGRAM_REASON / END_PROGRAM_REASON_DESC — the coded and decoded reason for the program ending normally.
• REMARKS (VARCHAR2, 500) — free-text commentary entered against the action.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle audit columns.

Common Use Cases and Queries

Typical usage includes regulatory reporting on exchange visitor activity, auditing the status history of an individual form, and building data extracts for SEVIS-related reporting. A common query retrieves the full action history for one form, ordered chronologically:

• SELECT ev_form_stat_id, ev_form_id, action_date, action_type, action_type_desc, termination_reason_desc, end_program_reason_desc FROM apps.igs_pe_ev_form_stat_v WHERE ev_form_id = :p_ev_form_id ORDER BY action_date;

Reports covering a date range for all active program participants may filter on the program dates and current status:

• SELECT ev_form_id, action_type_desc, prgm_start_date, prgm_end_date FROM apps.igs_pe_ev_form_stat_v WHERE action_date BETWEEN :p_from AND :p_to;

Because Oracle discourages direct reliance on this view, production code should generally join IGS_PE_EV_FORM_STAT to IGS_LOOKUP_VALUES explicitly, or use the decoded view for ad-hoc diagnostics only. Any customization built on this view should be reviewed at each EBS upgrade, since the view's column list and join predicates are subject to change without the compatibility guarantees that apply to base tables.