Search Results pe_sv_intl_org

Overview

IGS_PE_EV_FORM_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema. It presents the entity "SEVIS Ev Form" as used by the Student Systems / People Enterprise components of Oracle Student System, exposing a single denormalized row per SEVIS evidence form record. The view combines transactional columns from the base table IGS_PE_EV_FORM with translated meanings from the IGS_LOOKUP_VALUES lookup table and party information from HZ_PARTIES. Its principal purpose is to supply reporting, concurrent program, and integration consumers with fully described (code plus description) SEVIS form data without requiring callers to write the repeated outer-join and lookup logic themselves.

The naming prefix IGS_PE denotes the People Enterprise module, while EV_FORM refers to the evidence/SEVIS form artifact. Because the view resolves descriptive columns such as form status, government agency names, international organization names, reprint reason, position, subject field, and matriculation, it is a convenient source for extract programs, letter generation, and BI Publisher data templates.

Underlying Base Objects

The view is defined over eleven referenced objects:

• IGS_PE_EV_FORM PV — the driving base table holding the SEVIS evidence form transaction records.
• IGS_LOOKUP_VALUES L1 through L10 — up to ten aliased instances of the lookup values table, each resolved against a distinct lookup type to provide the descriptive "meaning" columns.
• HZ_PARTIES HP — the Trading Community Architecture party table, joined to supply the SEVIS school party name.

Joins are performed on lookup codes with the lookup type constrained. Form status is an inner join against type PE_SV_FM_STAT_TYPE. Government agency codes join with outer (+) semantics against PE_US_GVT_AGENCY, and international organization codes join with outer (+) semantics against PE_SV_INTL_ORG — the lookup type that corresponds directly to the user's search term pe_sv_intl_org. Because those joins are outer joins, a form with an unknown or missing international organization code still returns a row, with a null description.

Key Columns

• ev_form_id, person_id, ev_form_number — primary identifiers for the form and the person to whom it relates.
• form_status, form_status_desc — status code and decoded meaning from PE_SV_FM_STAT_TYPE.
• govt_org1_code/amt/desc, govt_org2_code/amt/desc — US government agency funding sources and amounts, decoded from PE_US_GVT_AGENCY.
• intl_org1_code/amt/desc, intl_org2_code/amt/desc — international organization funding sources and amounts, decoded from PE_SV_INTL_ORG.
• prgm_sponsor_amt, ev_govt_amt, bi_natnl_com_amt, other_govt_amt, personal_funds_amt — the funding breakdown used on the SEVIS form.
• prgm_start_date, prgm_end_date, init_prgm_start_date — program period data.
• position_code/desc/remarks, subject_field_code/desc/remarks, matriculation/desc — decoded academic attributes.
• reprint_reason/desc, last_reprint_date, reprint_remarks — reprint tracking information.
• sevis_school_identifier, sevis_school — SEVIS school identifier and the resolved party name from HZ_PARTIES.
• NO_SHOW_FLAG, is_valid, category_code/desc, remarks — validity and categorization attributes.

Common Use Cases and Queries

Typical scenarios include extracting SEVIS evidence form data for a person, listing forms by funding source, and reconciling international organization contributions. A representative query filtered on the international organization lookup is:

SELECT ev_form_number, person_id, form_status_desc, intl_org1_code, intl_org1_desc, intl_org1_amt, intl_org2_code, intl_org2_desc, intl_org2_amt FROM apps.igs_pe_ev_form_v WHERE intl_org1_code = :org_code OR intl_org2_code = :org_code ORDER BY person_id;

To report by status and program period:

SELECT ev_form_number, person_id, form_status_desc, prgm_start_date, prgm_end_date, sevis_school FROM apps.igs_pe_ev_form_v WHERE form_status = :status AND prgm_start_date BETWEEN :from_date AND :to_date;

Because the international and government joins are outer joins, callers should test for null descriptions when validating lookup data, and should restrict by person_id or date range to avoid full scans against IGS_PE_EV_FORM.