Search Results inst_eps_code

Overview

IGS_PE_HZ_PARTIES_V is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite IGS (Student System) product family. It is documented as valid in both EBS 12.1.1 and 12.2.2. As its description states, the view is based on the person extension table, exposing party-level person data maintained by the Student System alongside a descriptive territory name for the recorded birth country.

The view belongs to the person extension layer of the Oracle Student System, which augments the base HZ_PARTIES registry with institution-specific attributes. Because it joins party extension records to FND_TERRITORIES_VL, it allows users to resolve the BIRTH_COUNTRY code into a human-readable meaning without an additional lookup. It is typically consumed for reporting and integration purposes, where a denormalized, read-only projection of student and person data is preferable to querying the base table directly. The inclusion of INST_EPS_CODE — the identifier referenced in the user's search — makes the view relevant for external payment or electronic disbursement integration scenarios involving institutions.

Underlying Base Objects

The documented view definition selects from two objects:

• IGS_PE_HZ_PARTIES (PHP) — the person extension table that supplies the majority of the columns, including ROWID and PARTY_ID.
• FND_TERRITORIES_VL (TER) — the territories lookup view joined via an outer join (PHP.BIRTH_COUNTRY = TER.TERRITORY_CODE(+)) to resolve TERRITORY_SHORT_NAME as the MEANING alias mapped to BIRTH_COUNTRY_DESC.

The join is an outer join, so parties with a null or unmatched BIRTH_COUNTRY are still returned, with a null territory description. No additional base objects are documented for this view in the ETRM metadata, and the referenced base objects list is recorded as none documented; the authoritative source for lineage is therefore the view text itself.

Key Columns

The view exposes the following categories of columns:

• Identity and audit: ROW_ID, PARTY_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Demographic and status: BIRTH_CITY, BIRTH_COUNTRY, BIRTH_COUNTRY_DESC (derived), DECEASED_IND, ARCHIVE_EXCLUSION_IND, ARCHIVE_DT, PURGE_EXCLUSION_IND, PURGE_DT, ORACLE_USERNAME.
• Qualification and service: PROOF_OF_INS, PROOF_OF_IMMU, LEVEL_OF_QUAL, MILITARY_SERVICE_REG, VETERAN, FELONY_CONVICTED_FLAG.
• Institution attributes: INSTITUTION_CD, INST_EPS_CODE, INST_PRIORITY_CD, INST_ORG_IND, INST_PHONE_COUNTRY_CODE, INST_PHONE_AREA_CODE, INST_PHONE_NUMBER, SEC_SCHOOL_LOCATION_ID.
• Organization-unit attributes: OI_LOCAL_INSTITUTION_IND, OI_OS_IND, OI_GOVT_INSTITUTION_CD, OI_INST_CONTROL_TYPE, OI_INSTITUTION_TYPE, OI_INSTITUTION_STATUS, OU_START_DT, OU_END_DT, OU_MEMBER_TYPE, OU_ORG_STATUS, OU_ORG_TYPE, OSS_ORG_UNIT_CD.
• Academic and funding: ADV_STUDIES_CLASSES, HONORS_CLASSES, CLASS_SIZE, PERCENT_PLAN_HIGHER_EDU, FUND_AUTHORIZATION, PE_INFO_VERIFY_TIME.

INST_EPS_CODE is the institution-level EPS code carried from the person extension table and is commonly used to associate a party with a payment or electronic processing system record.

Common Use Cases and Queries

Typical use cases include reporting on student institution and demographic attributes, extracting party records for downstream integration, and resolving birth country descriptions for display. A representative query filtering on the searched attribute follows:

• Retrieve parties for a specific institution EPS code:

  SELECT party_id, institution_cd, inst_eps_code, birth_country_desc
  FROM   apps.igs_pe_hz_parties_v
  WHERE  inst_eps_code = :p_eps_code;

• List institution contact details for active parties:

  SELECT party_id, institution_cd, inst_phone_country_code,
         inst_phone_area_code, inst_phone_number
  FROM   apps.igs_pe_hz_parties_v;

• Report deceased or purge-excluded persons:

  SELECT party_id, deceased_ind, purge_exclusion_ind
  FROM   apps.igs_pe_hz_parties_v
  WHERE  deceased_ind = 'Y';

Because the view is read-only and owned by APPS, queries should be issued from an APPS or reporting responsibility with appropriate grants. No DML should be directed at the view; updates to the underlying IGS_PE_HZ_PARTIES table should be performed through the supported Student System APIs.