Results for “form_effective_date”

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

Overview

The view IGSBV_EXCHANGE_VISITORS belongs to the IGS — Student System product family, a module that is now flagged as obsolete in Oracle E-Business Suite. It exposes information about persons entering an institution as exchange visitors, a classification used primarily for regulatory reporting of foreign nationals participating in sponsored academic or cultural exchange programs. The view is a read-only, denormalized reporting construct: its defining text terminates with the clause WITH READ ONLY, meaning no DML operations are permitted against it. Its purpose is to present the exchange visitor form data stored in the base table in a form directly consumable by reports, concurrent programs, and integration extracts.

Notably, the ETRM metadata records that the view is not implemented in this database. In Oracle EBS 12.1.1 and 12.2.2 environments where the IGS product has been superseded or never installed, the view will not exist. Consumers should therefore verify its presence before referencing it in custom code.

Underlying Base Objects

The view is defined over a single base object: IGS_PE_EV_FORM, aliased as PEV. No additional joins or referenced base objects are documented in the ETRM metadata. The view text is a straightforward projection of columns from that table, with several columns transformed through lookup substitution expressions.

The lookup pattern used is characteristic of Oracle EBS descriptive-flexfield and lookup rendering. Each expression follows the form:

• '_LA:PEV.FORM_STATUS:IGS_LOOKUP_VALUES:PE_SV_FM_STAT_TYPE:MEANING'

This instructs the reporting layer to resolve the stored code against the IGS lookup type (for example PE_SV_FM_STAT_TYPE) and return the human-readable MEANING value. Because the base object is IGS_PE_EV_FORM and there is no join, the view is effectively a one-to-one projection with lookup decoration, not an aggregation or union-based construct.

Key Columns

The column list covers several functional groupings:

• Form identity and status: PRINT_FORM, FORM_EFFECTIVE_DATE, and the lookup-derived _LA:FORM_STATUS. These describe the printed exchange visitor form and its lifecycle status.
• Create reason: CREATE_REASON is exposed directly as a stored column. This is the column most commonly targeted by searches such as the one that produced this reference, and it records why the exchange visitor form record was created.
• Financial sponsorship amounts: PROGRAM_SPONSOR_AMOUNT, GOVERNMENT_ORG1_AMOUNT, GOVERNMENT_ORG2_AMOUNT, INTERNATIONAL_ORG1_AMOUNT, INTERNATIONAL_ORG2_AMOUNT, EXCHANGE_VISITOR_GOVT_AMOUNT, BI_NATIONAL_COMMISION_AMOUNT, OTHER_GOVERNMENT_AMOUNT, and PERSONAL_FUNDS_AMOUNT. These capture the funding sources declared on the form.
• Program dates: PROGRAM_START_DATE, PROGRAM_END_DATE, INIT_PRGM_START_DATE, and LAST_REPRINT_DATE.
• Reprint and remarks: the lookup-derived _LA:REPRINT_REASON plus REPRINT_REMARKS.
• Categorical attributes: lookup-derived _LA:POSITION_CODE, _LA:SUBJECT_FIELD_CODE, _LA:MATRICULATION, and _LA:CATEGORY_CODE, each accompanied by a free-text remarks column.
• Identity and audit: EV_FORM_ID, PERSON_ID, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and IS_VALID.

Common Use Cases and Queries

Typical usage involves extracting exchange visitor records for regulatory or institutional reporting, filtering on validity, program dates, or the create reason. A representative query retrieving active visitors with their form status and create reason is:

• SELECT person_id, exchange_visitor_form_number, form_effective_date, create_reason, program_start_date, program_end_date FROM igsbv_exchange_visitors WHERE is_valid = 'Y' AND program_start_date >= :start_date ORDER BY program_start_date;

The CREATE_REASON column is frequently used to segment records by the origin of the form, for example to distinguish initial submissions from reinstatements or corrections. Because the view is read-only and unimplemented in some environments, any dependent customization should guard against its absence, and where the base table IGS_PE_EV_FORM is available, equivalent extracts may be constructed directly against it if the view is unavailable.