Search Results alternate_identifier

Overview

IGF_AP_SCHOOL_OPEID_V is a reporting view owned by the APPS schema within the IGF (Financial Aid) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold distinct OPE ID codes together with their descriptions. An OPE ID (Office of Postsecondary Education Identification) number is the identifier the U.S. Department of Education assigns to a postsecondary institution, and in a financial aid context it is essential for identifying the school associated with a student, award, or disbursement record.

The view consolidates institution alternate identifiers maintained against organization records in Oracle's trading community model and joins them to a financial aid lookup that supplies a user-facing description. Because the view filters to active parties and a single alternate ID type, it presents a clean, de-duplicated list of valid OPE ID values. This makes it suitable for LOV (list of values) population, reference validation, and reporting rather than as a transactional store. The status is VALID in the data dictionary.

Underlying Base Objects

The view text references the following objects:

• HZ_PARTIES — the party master; only records with STATUS = 'A' (active) are retained.
• IGS_PE_HZ_PARTIES — the student system link between a party and an organization unit, via OSS_ORG_UNIT_CD.
• IGS_OR_ORG_ALT_IDS — organization alternate identifiers, supplying ORG_ALTERNATE_ID and the alternate ID type.
• IGS_OR_ORG_ALT_IDTYP — the alternate ID type definition, supplying SYSTEM_ID_TYPE.
• IGF_LOOKUPS_VIEW — the financial aid lookup view, supplying MEANING for the OPE ID lookup code.

Joins are established between the alternate IDs and the party/organization link, between that link and HZ_PARTIES, and between the alternate ID type of the alternate IDs and the type definition. A date predicate enforces currency: SYSDATE must fall between START_DATE and NVL(END_DATE, SYSDATE), so only currently effective identifiers appear. The lookup join is constrained to LOOKUP_TYPE = 'IGF_AP_SCHOOL_OPEID', LOOKUP_CODE equal to the alternate ID, and ENABLED_FLAG = 'Y'. The result is grouped by alternate ID, system ID type, and meaning, which produces the distinct set described in the documentation.

Key Columns

• ALTERNATE_IDENTIFIER — derived from OLI.ORG_ALTERNATE_ID. This is the OPE ID value itself.
• SYSTEM_ID_TYPE — derived from OLT.SYSTEM_ID_TYPE and hard-filtered to 'OPE_ID_NUM'. Every row carries this literal value; it confirms the identifier is an OPE ID number.
• MEANING — the description of the OPE ID from IGF_LOOKUPS_VIEW (LKUP.MEANING), typically the institution or school name shown to users.

Because the view exposes only these three columns, it is a narrow reference source rather than a wide reporting entity. Consumers requiring additional school attributes must join back to the base tables using the alternate identifier.

Common Use Cases and Queries

The principal use is building a validated list of OPE IDs and their descriptions for display or data entry. A typical retrieval is:

• SELECT alternate_identifier, meaning FROM igf_ap_school_opeid_v ORDER BY meaning;
• SELECT meaning FROM igf_ap_school_opeid_v WHERE alternate_identifier = :ope_id;
• SELECT DISTINCT system_id_type FROM igf_ap_school_opeid_v; — returns the single value OPE_ID_NUM, useful for confirming the type qualifier when a user searches on "system_id_type".

Typical scenarios include resolving a school name from a stored OPE ID during financial aid reconciliation, populating a school selection LOV, validating imported student or disbursement data, and filtering an institution list by description for reporting. Since the view already applies active-status and effective-date logic, queries against it return only currently valid schools, removing the need to replicate those predicates in calling code.