Search Results reported_alumni




Overview
Explore in AI Chat

Overview

IGSFV_FAMILY_RELATIONSHIPS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGSFV_FAMILY_RELATIONSHIPS and reported with a status of VALID. It belongs to the Student System (IGS) product family and exposes information about the family relationships of a person. Each row represents a relationship between two people: a subject person and an object person, linked by a relationship code and bounded by optional start and end dates.

The view is intended for reporting and integration rather than transactional entry. Because it is a BIS view, it is optimized for read-only consumption by external reporting tools, extracts, and analytics workloads, and should not be treated as a maintenance surface for the underlying relationship data. In the context of Oracle EBS 12.1.1 and 12.2.2, the view provides a stable, denormalized projection that shields downstream consumers from the physical layout of the constituent base tables.

Underlying Base Objects

The ETRM metadata for this view does not document any referenced base objects. No base tables are listed, which means the dependency information available in the repository is incomplete or the view source is resolved at runtime through the compiled definition stored in the data dictionary. In practice, family relationship data in the Student System is maintained through the relationship and person entities of the IGS schema, including the relationship definitions and the person records that resolve to the ID numbers exposed as SUBJECT_ID_NUMBER and OBJECT_ID_NUMBER.

Because no base objects are documented, anyone performing impact analysis or tuning should inspect the view definition directly using the data dictionary, for example by querying ALL_VIEWS or DBMS_METADATA.GET_DDL for the APPS.IGSFV_FAMILY_RELATIONSHIPS view. This will reveal the exact join path and the physical tables from which each projected column is derived.

Key Columns

  • SUBJECT_ID_NUMBER (VARCHAR2, 30) — unique identification number of the subject person in the relationship.
  • OBJECT_ID_NUMBER (VARCHAR2, 30) — unique identification number of the object person in the relationship.
  • _LA:RELATIONSHIP_CODE (CHAR, 65) — relationship code; the translated or language-attribute form of the relationship type.
  • RELATIONSHIP_START_DATE / RELATIONSHIP_END_DATE (DATE) — the effective period during which the relationship is valid.
  • PRIMARY / SECONDARY (VARCHAR2) — indicators identifying whether the relationship is primary or secondary.
  • JOINT_SALUTATION (VARCHAR2, 1000) — salutation used during letter generation, typically for addressing related parties jointly.
  • NEXT_TO_KIN (VARCHAR2) — identifies the next of kin for the subject person.
  • REPORTED_STUDENT (VARCHAR2) — student information for the relation as reported by the related person. This is the column referenced by the search term "reported_student". Parallel columns REPORTED_FACULTY, REPORTED_STAFF, and REPORTED_ALUMNI capture the corresponding faculty, staff, and alumni affiliations.
  • RELATIONSHIP_ID (NUMBER, 15) — unique identifier for the relationship record.
  • DIRECTIONAL_FLAG (VARCHAR2) — F for a forward relationship (such as parent-to-child or headquarters-to-branch) and B for a backward relationship.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include dependent and next-of-kin reporting, admissions and enrolment correspondence, letter generation using JOINT_SALUTATION, and analytics on family linkages within the institution. The REPORTED_STUDENT column is commonly filtered to identify relationships in which the related person is reported as a student.

Sample query returning student-reported family relationships:

  • SELECT SUBJECT_ID_NUMBER, OBJECT_ID_NUMBER, _LA:RELATIONSHIP_CODE, RELATIONSHIP_START_DATE, RELATIONSHIP_END_DATE, REPORTED_STUDENT FROM APPS.IGSFV_FAMILY_RELATIONSHIPS WHERE REPORTED_STUDENT IS NOT NULL;
  • Filter for active relationships by restricting RELATIONSHIP_END_DATE to NULL or a future date, and constrain the DIRECTIONAL_FLAG to F or B depending on whether forward or backward traversal is required.
  • Join SUBJECT_ID_NUMBER and OBJECT_ID_NUMBER to person or student entities when richer biographical detail is needed beyond what the view exposes.