Results for “rel_end_date”

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

Overview

The view IGS_PE_HZ_REL_V belongs to the IGS (Student System) product family, an obsolete module within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents a consolidated, denormalized representation of relationship data linking parties (persons) within the Trading Community Architecture (TCA), exposing both the student-system–specific relationship attributes and the corresponding person name and relationship-type descriptive information. The view is intended primarily for reporting and integration scenarios in which consumers need a single queryable object that surfaces a party's relationship to another party, together with attributes such as whether the related individual is the "next of kin." The view name itself reflects this design intent: it merges the IGS relationship table with the TCA HZ_RELATIONSHIPS base table so that descriptive fields (for example, relationship-type meaning and person name) are available without additional joins.

Underlying Base Objects

Per the documented metadata, the view is defined as a join between IGS_PE_HZ_REL and HZ_RELATIONSHIPS. The IGS table supplies the student-system relationship attributes, while HZ_RELATIONSHIPS supplies the core TCA relationship definition. Within the view text, three aliases are used:

• PR — the primary row source (the IGS relationship record), providing PARTY_ID, RELATIONSHIP_ID, SUBJECT_ID, OBJECT_ID, directional flags, dates, and descriptive columns.
• PE — the extended relationship attributes source, providing NEXT_TO_KIN, PRIMARY, SECONDARY, JOINT_SALUTATION, and the representative flags REP_FACULTY, REP_STAFF, REP_STUDENT, and REP_ALUMNI.
• HZP — the TCA party source, providing PARTY_NUMBER, PERSON_NAME (as FULL_NAME), the prefix components, and the name-part columns.

A lookup source, aliased L1, is also referenced to resolve RELATIONSHIP_TYPE into a human-readable meaning (MEANING). The documentation lists no separate referenced base objects beyond these, and the object is noted as not implemented in the documented database instance — meaning the definition exists in ETRM metadata but the compiled view may not be present in the target environment.

Key Columns

• ROW_ID — the row identifier of the underlying IGS relationship record.
• PARTY_ID, SUBJECT_ID, OBJECT_ID — the TCA identifiers for the owning party and the two related parties.
• OBJECT_ID_NUMBER — the TCA party number of the object party.
• PARTY_RELATIONSHIP_TYPE / PARTY_RELATIONSHIP_TYP_MEANING — the relationship type code and its decoded meaning.
• DIRECTIONAL_FLAG — indicates whether the relationship is directional.
• FULL_NAME, PREFIX, FIRST_NAME — person name elements for the related party.
• NEXT_TO_KIN — the flag indicating the related person is designated as next of kin; this is the column most commonly sought when users search the term "next_to_kin."
• PRIMARY, SECONDARY, JOINT_SALUTATION — contact and salutation attributes.
• REP_FACULTY, REP_STAFF, REP_STUDENT, REP_ALUMNI — flags denoting the representative capacity of the related person.
• START_DATE, END_DATE, STATUS, COMMENTS, CONTENT_SOURCE_TYPE — validity, status, and descriptive fields.
• Standard ATTRIBUTE1–ATTRIBUTE20, GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20, and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER).

Common Use Cases and Queries

Typical usages include reporting on emergency contacts and next-of-kin designations for students or applicants, generating relationship listings for constituent management, and feeding integration extracts that require both relationship metadata and person names. A representative query that retrieves next-of-kin relationships for a given party would resemble:

• SELECT party_id, object_id, object_id_number, full_name, next_to_kin, party_relationship_typ_meaning, start_date, end_date
• FROM igs_pe_hz_rel_v
• WHERE next_to_kin = 'Y'
• AND TRUNC(SYSDATE) BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE + 1);

Additional scenarios filter on REP_STUDENT = 'Y' for guardian or parental relationships, or select all active relationships by joining PARTY_ID to HZ_PARTIES. Because the product is obsolete, implementations on 12.1.1 and 12.2.2 should verify view availability before relying on it, as the metadata indicates it is not implemented in every database.