Results for “birth_date”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_PE_INTL_DEPD_V is a valid Oracle E-Business Suite view owned by the APPS schema and registered under the IGS (Student System) product family. Its documented purpose is to expose "Person Dependent Relationship for International Form" data, meaning it presents the dependent relationships a person holds — specifically spouse and parent relationships — for consumption by international-related student forms and processes. The view is available in both Oracle EBS 12.1.1 and 12.2.2 environments.

The view functions as a denormalized reporting and integration layer. It joins person relationship records to person biographical details and to lookup-driven relationship descriptions, so that downstream forms, concurrent programs, or external interfaces can retrieve dependent information without manually reconstructing the join logic against the Trading Community Architecture (TCA) relationship tables. Because the view filters to active relationships only, it returns a clean, current set of dependent links suitable for display and validation.

Underlying Base Objects

The view is documented as selecting from three underlying sources:

  • HZ_RELATIONSHIPS (aliased PR) — the TCA relationships table that stores the core relationship rows, including subject party, object party, relationship code, and status.
  • IGS_PE_PERSON_BASE_V (aliased P) — the IGS person base view supplying person identifiers, full name, and birth date.
  • FND_LOOKUP_VALUES_VL (aliased L1) — the multilingual lookup view providing the translated meaning for the relationship code.

Joins are established as follows: PR.OBJECT_ID equals P.PERSON_ID, linking the dependent party to its person record; PR.RELATIONSHIP_CODE equals L1.LOOKUP_CODE, with L1.LOOKUP_TYPE restricted to 'PARTY_RELATIONS_TYPE' and L1.VIEW_APPLICATION_ID restricted to 222, tying each relationship to its descriptive lookup meaning. The view further constrains results so that RELATIONSHIP_CODE is limited to 'SPOUSE_OF' and 'PARENT_OF', and PR.STATUS equals 'A' for active relationships. The ETRM metadata records no additionally documented base objects beyond those embedded in the view text.

Key Columns

  • ROW_ID — the ROWID of the underlying HZ_RELATIONSHIPS row, useful for direct row addressing.
  • RELATIONSHIP_ID — the unique identifier of the relationship record.
  • SUBJECT_ID — the party on the subject side of the relationship (for example, the student).
  • RELATIONSHIP_CODE — the relationship type, limited to 'SPOUSE_OF' or 'PARENT_OF'.
  • RELATIONSHIP_DESC — the translated meaning of the relationship code sourced from the lookup.
  • OBJECT_ID — the party on the dependent side of the relationship; joined to the person base view.
  • FULL_NAME — the full name of the dependent person.
  • BIRTH_DATE — the dependent person's date of birth.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns reflecting who created and last modified the underlying relationship row.

Common Use Cases and Queries

The view is typically used when assembling dependent details for international student forms, verifying that a declared spouse or parent exists as an active relationship, or exporting dependent demographics for reporting. A representative query listing all dependents for a given subject is:

  • SELECT relationship_desc, full_name, birth_date FROM igs_pe_intl_depd_v WHERE subject_id = :p_subject_id;
  • SELECT object_id, full_name FROM igs_pe_intl_depd_v WHERE relationship_code = 'PARENT_OF' AND subject_id = :p_subject_id;
  • SELECT subject_id, COUNT(*) FROM igs_pe_intl_depd_v GROUP BY subject_id;

Because the view already enforces active status and restricts relationship types, queries against it avoid re-implementing those filters and return only the spouse and parent relationships relevant to international processing.