Search Results member_profile_id

Overview

IGS_PE_FAMILY_DTLS_V is a view owned by the APPS schema within the IGS – Student System product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description explicitly identifies it as obsolete, meaning it is retained in the data dictionary primarily for backward compatibility and is no longer the recommended interface for new development or reporting. The view presents family and relationship details associated with a student or person, joining the family detail record to the member party, the relationship definition, person profile attributes, statistical detail flags, and several lookup-based decoded values.

From a functional standpoint, the view surfaces a denormalized, report-ready row for each family detail entry, exposing both the person who owns the family record and the family member related to that person. It brings in descriptive columns such as surname, given names, title, prefix, suffix, gender, marital status, e-mail address, and the joint salutation text, along with flags indicating whether the member is faculty, staff, alumni, or a current student. Because it is obsolete, Oracle support guidance generally treats it as deprecated; nevertheless, existing custom reports, extracts, and legacy integrations may still reference it, so an understanding of its structure remains useful during upgrades and remediation.

Underlying Base Objects

The view is defined over several base and lookup objects, as documented in the ETRM view text:

• IGS_PE_FAMILY_DTLS PFD – the primary family detail record; supplies FAMILY_DTL_ID, MEMBER_ID, JOINT_SALUTATION, PRIMARY, SECONDARY, and the faculty/staff/alumni/current-student flags.
• HZ_PARTIES HP – the member party; provides PARTY_NUMBER, PERSON_LAST_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_PRE_NAME_ADJUNCT, PERSON_NAME_SUFFIX, PERSON_TITLE, and EMAIL_ADDRESS.
• HZ_PARTIES HP1 – the subject (student) party; provides SUBJECT_ID and PERSON_NUMBER.
• HZ_RELATIONSHIPS HPR – the relationship record; supplies RELATIONSHIP_ID, RELATIONSHIP_TYPE, RELATIONSHIP_CODE, DIRECTIONAL_FLAG (exposed as RECIPROCAL), and START_DATE/END_DATE.
• HZ_PERSON_PROFILES PP1 and PP2 – person profile data; PP1 supplies GENDER, MARITAL_STATUS, and MEMBER_PROFILE_ID, while PP2 supplies PERSON_PROFILE_ID.
• IGS_PE_STAT_DETAILS SD2 – provides NEXT_TO_KIN (aliased DSP_NEXTTOKIN).
• IGS_PE_HZ_PARTIES PHP – provides DECEASED_IND.
• FND_LOOKUP_VALUES L1, L3, L4 and IGS_LOOKUPS_VIEW L5 – outer-joined lookup sources decoding sex, contact title, relationship type, and marital status respectively.

The joins anchor member and subject party records to the relationship and family detail rows, with lookup joins written as Oracle-style outer joins (marked with the (+) operator) so that missing lookup codes do not suppress the primary row.

Key Columns

• ROW_ID, FAMILY_DTL_ID – pseudocolumn and primary identifier for the family detail record.
• PERSON_ID, PERSON_NUMBER – the subject person’s party and party number (from HP1).
• MEMBER_ID, MEMBER_NUMBER – the family member’s party identifier and party number.
• SURNAME, GIVEN_NAMES, PERSON_MIDDLE_NAME, PRE_NAME_ADJUNCT, SUFFIX, TITLE – person name components for the member.
• JOINT_SALUTATION – the joint salutation text stored on the family detail record; this is the column most relevant to searches for "joint_salutation."
• RELATIONSHIP_TYPE_ID, RELATIONSHIP_TYPE, RELATIONSHIP_TYPE_MEANING, RELATIONSHIP_CODE, RECIPROCAL – relationship classification and decoded meaning.
• PRIMARY, SECONDARY, FACULTY, STAFF, ALUMNI, CURRENT_STUDENT – role indicators for the family member.
• SEX, SEX_MEANING, MARITAL_STATUS, MARITAL_STATUS_M – demographic attributes and their decoded meanings.
• EMAIL_ADDRESS, DECEASED, DSP_NEXTTOKIN, START_DATE, END_DATE – contact, status, next-of-kin, and relationship validity data.

Common Use Cases and Queries

Typical usage centers on student contact and family reporting, next-of-kin extracts, and lookups of a family member’s joint salutation or relationship details. A representative query filtered by joint salutation is:

• SELECT person_number, member_number, surname, given_names, joint_salutation, relationship_type_meaning FROM apps.igs_pe_family_dtls_v WHERE joint_salutation IS NOT NULL;
• SELECT person_id, member_id, relationship_type_meaning, primary, secondary FROM apps.igs_pe_family_dtls_v WHERE person_id = :person_id;
• SELECT member_number, surname, given_names, sex_meaning, marital_status_m FROM apps.igs_pe_family_dtls_v WHERE current_student = 'Y';

Because the object is documented as obsolete, any new report or integration should preferably be built against the current family and party relationship tables rather than this view; existing dependent objects should be reviewed prior to upgrade to 12.2.2.