Search Results igsfv_exchange_visitors

Overview

The IGSFV_EXCHANGE_VISITORS view is a read-only reporting object in the Oracle E-Business Suite Student System (IGS) product. It presents information about persons entering an institution as exchange visitors, consolidating data from the exchange visitor form records maintained in the base tables. The view is owned by the APPS schema and is defined over IGS_PE_EV_FORM joined to HZ_PARTIES, giving both the regulatory exchange visitor form details and the party (person) identifier. Because the view is defined WITH READ ONLY, it is intended strictly for querying, reporting, and integration extraction rather than for data manipulation.

The view carries a notable characteristic: several columns are not delivered as raw lookup codes. Instead, the SELECT list substitutes literal descriptive expressions such as '_LA:PEV.FORM_STATUS:IGS_LOOKUP_VALUES:PE_SV_FM_STAT_TYPE:MEANING'. These pseudo-columns are resolved at runtime by the ETRM/Oracle EBS localization and lookup architecture, which translates the stored code value into its lookup meaning for the target language. The same mechanism applies to REPRINT_REASON, POSITION_CODE, SUBJECT_FIELD_CODE, MATRICULATION, and CATEGORY_CODE.

Underlying Base Objects

Although the ETRM 12.2.2 metadata records "referenced base objects: none documented," the view text supplied for 12.1.1/12.2.2 explicitly identifies two sources:

• IGS_PE_EV_FORM PEV — the primary driving table holding the exchange visitor form records, including the funded amounts, program dates, reason codes, and form identifiers.
• HZ_PARTIES HZP — the Trading Community Architecture party table, joined on PEV.PERSON_ID = HZP.PARTY_ID to supply PARTY_NUMBER and to guarantee the record resolves to a valid party.

The join is an equi-join on person/party identifier, and the view is exposed WITH READ ONLY. This structure means each row of IGSFV_EXCHANGE_VISITORS corresponds to one exchange visitor form instance for one party.

Key Columns

• PRINT_FORM — indicator of whether the form is flagged for printing.
• FORM_EFFECTIVE_DATE — the effective date of the exchange visitor form.
• _LA:FORM_STATUS — derived descriptive value for the form status, resolved from lookup type PE_SV_FM_STAT_TYPE.
• CREATE_REASON — the reason code recorded at creation of the exchange visitor form. This column is central to the user's search term create_reason; it captures why the form/record was created and is used in audit and reporting contexts.
• IS_VALID — validity flag for the record.
• Funding amount columns — PRGM_SPONSOR_AMT, GOVT_ORG1_AMT, GOVT_ORG1_CODE, GOVT_ORG2_AMT, GOVT_ORG2_CODE, INTL_ORG1_AMT, INTL_ORG1_CODE, INTL_ORG2_AMT, INTL_ORG2_CODE, EV_GOVT_AMT, BI_NATNL_COM_AMT, OTHER_GOVT_AMT, and PERSONAL_FUNDS_AMT — together describing the financial resources declared on the exchange visitor form.
• EV_FORM_NUMBER — the exchange visitor form number.
• PRGM_START_DATE / PRGM_END_DATE — the program period covered by the form.
• LAST_REPRINT_DATE, _LA:REPRINT_REASON, REPRINT_REMARKS — reprint history and its reason (lookup type PE_SV_REPRINT_REASON).
• _LA:POSITION_CODE / POSITION_REMARKS — the exchange visitor's position (lookup PE_SV_EV_POSITION).
• _LA:SUBJECT_FIELD_CODE — the subject/field of study (lookup PE_US_COURSE_SUBJECT).
• _LA:CATEGORY_CODE — the exchange visitor program category (lookup PE_SV_EV_PRG_CATEGORY).
• PARTY_NUMBER — the party number from HZ_PARTIES.
• PERSON_ID / EV_FORM_ID — identifiers for the person and the form record.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The view is typically queried for reporting on exchange visitor programme participants, financial resource declarations, and audit of form creation or reprint activity. A representative query filtering on the creation reason and listing funding totals is:

• SELECT ev_form_number, party_number, person_id, create_reason, prgm_start_date, prgm_end_date, personal_funds_amt, prgm_sponsor_amt FROM igsfv_exchange_visitors WHERE create_reason = :reason;
• SELECT party_number, ev_form_number, "_LA:FORM_STATUS" FROM igsfv_exchange_visitors WHERE is_valid = 'Y';

Because several columns are lookup-resolved expression columns, their aliases must be quoted in SQL, and consumers should reference them exactly as exposed. The view is suitable for BI Publisher reports, extracts, and inbound interface validation, but not for DML given its read-only definition.