Results for “relationship_end_date”

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

Overview

IGSFV_FAMILY_RELATIONSHIPS is a read-only view within the IGS (Student System) product family of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. The view presents information about the family relationships of a person, exposing the association between a subject party and an object party along with the descriptive attributes maintained against that relationship. In the ETRM documentation the entity is classified under IGS - Student System (Obsolete), and the implementation note states that it is not implemented in the reference database. Consequently, sites upgrading or reviewing legacy student-system customizations should treat the object as historical rather than as a supported runtime component.

Functionally, the view serves reporting and integration purposes: it flattens the relationship records held across the Oracle Trading Community Architecture (TCA) relationship tables and the student-system extension table into a single, denormalized row per relationship. Users searching for the term relationship_start_date will find that this concept is surfaced by the RELATIONSHIP_START_DATE column, which is derived directly from the HZ_RELATIONSHIPS.START_DATE column.

Underlying Base Objects

The documented view text defines the object over four base tables using an inner-join pattern. The driving table is IGS_PE_HZ_REL (aliased PHR), the student-system extension that carries person-specific relationship attributes. It is joined to HZ_RELATIONSHIPS (aliased HZR) on both RELATIONSHIP_ID and DIRECTIONAL_FLAG, ensuring that the extension row matches the correct directional relationship record. Two instances of HZ_PARTIES (aliased HZP1 and HZP2) supply the party numbers: HZP1 is joined on HZR.SUBJECT_ID and HZP2 on HZR.OBJECT_ID. The view is declared WITH READ ONLY, so no DML is permitted. Although the ETRM metadata records no referenced base objects, the view text explicitly documents the TCA and IGS tables described above.

Key Columns

• RELATIONSHIP_START_DATE — the start date of the relationship, sourced from HZ_RELATIONSHIPS.START_DATE; this is the column retrieved by searches on relationship_start_date.
• RELATIONSHIP_END_DATE — the corresponding end date, sourced from HZ_RELATIONSHIPS.END_DATE.
• SUBJECT_ID_NUMBER and OBJECT_ID_NUMBER — the party numbers of the two parties linked by the relationship.
• "_LA:RELATIONSHIP_CODE" — a lookup-mapped relationship code, resolved against AR_LOOKUPS using the PARTY_RELATIONS_TYPE lookup type.
• PRIMARY, SECONDARY, JOINT_SALUTATION, NEXT_TO_KIN — flags and salutation data maintained in IGS_PE_HZ_REL.
• REPORTED_FACULTY, REPORTED_STAFF, REPORTED_STUDENT, REPORTED_ALUMNI — indicators recording the reporting context of the relationship.
• RELATIONSHIP_ID, DIRECTIONAL_FLAG — the identifying and directional keys linking the extension and TCA relationship rows.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical usage includes listing a person's relatives, identifying emergency or next-of-kin contacts, and reporting on relationship validity windows. Because the view is obsolete, queries should be restricted to historical or read-only reporting.

To retrieve current family relationships for a subject party, ordered by start date:

• SELECT subject_id_number, object_id_number, relationship_start_date, relationship_end_date FROM igsfv_family_relationships WHERE subject_id_number = :party_number AND (relationship_end_date IS NULL OR relationship_end_date > SYSDATE) ORDER BY relationship_start_date;

To count relationships reported in a student context during a given period:

• SELECT relationship_start_date, COUNT(*) FROM igsfv_family_relationships WHERE reported_student = 'Y' AND relationship_start_date BETWEEN :from_date AND :to_date GROUP BY relationship_start_date;