Results for “igf_gr_person_v”

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

Overview

IGF_GR_PERSON_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product family. It exposes a consolidated, report-friendly projection of person (party) information drawn primarily from the Financial Aid base record table IGF_AP_FA_BASE_REC and joined to Oracle's Trading Community Architecture (TCA) and Student System person entities. The view's purpose is to present the identifying attributes of a financial aid applicant or recipient — person name, person number, surname, given names, middle name, birth date, and Social Security Number — alongside the Financial Aid base record keys (ROW_ID, BASE_ID) and calendar/sequence context (CI_CAL_TYPE, CI_SEQUENCE_NUMBER). Because it flattens data that would otherwise require joining several normalized tables, it is commonly used in concurrent-program extracts, inbound/outbound interfaces, OAF-based inquiry pages, and ad-hoc reporting where a single denormalized person row is preferred. The object is documented as VIEW type with VALID status in the ETRM 12.2.2 metadata.

Underlying Base Objects

The view's SQL text identifies the following base objects:

• IGF_AP_FA_BASE_REC (aliased FA) — the driving Financial Aid base record table; supplies ROW_ID, BASE_ID, PERSON_ID, CI_CAL_TYPE, CI_SEQUENCE_NUMBER, and the standard WHO audit columns.
• HZ_PARTIES (aliased P) — the TCA party master, providing PERSON_NUMBER, PERSON_NAME, and the name components (last, first, middle).
• HZ_PERSON_PROFILES (aliased PP) — outer-joined for DATE_OF_BIRTH, constrained by the effective-dating predicate SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE).
• IGS_PE_ALT_PERS_ID (aliased API) — outer-joined alternate person identifiers; effective-dated with NVL(start_dt, SYSDATE) and NVL(end_dt, SYSDATE).
• IGS_PE_PERSON_ID_TYP (aliased PIT) — person identifier type lookup, filtered to S_PERSON_ID_TYPE = 'SSN' so only the Social Security Number identifier is surfaced.

The ETRM metadata records no documented referenced base objects, so the join definition above is taken directly from the supplied view SQL and is authoritative.

Key Columns

• ROW_ID, BASE_ID — Financial Aid base record identifiers carried through from IGF_AP_FA_BASE_REC.
• PERSON_ID — party identifier; equated to HZ_PARTIES.PARTY_ID and to PE_PERSON_ID in the alternate-ID join.
• PERSON_NUMBER — the party number assigned in TCA.
• PERSON_NAME — the formatted party name (the column most directly matching the search term "person_name").
• SURNAME, GIVEN_NAMES, MIDDLE_NAME — surname, first-name, and middle-name components for name-splitting requirements.
• BIRTH_DT — date of birth from the effective person profile.
• CI_CAL_TYPE, CI_SEQUENCE_NUMBER — calendar type and sequence identifying the Financial Aid period/context.
• SSN — the Social Security Number alternate identifier, restricted to identifier type 'SSN' and currently effective.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include applicant name lookups, financial aid extracts keyed by person, and integration payloads requiring SSN plus name. Sample query:

SELECT person_id,
       person_number,
       person_name,
       surname,
       given_names,
       birth_dt,
       ssn
  FROM apps.igf_gr_person_v
 WHERE person_name LIKE :p_name
 ORDER BY surname, given_names;

Because HZ_PERSON_PROFILES and IGS_PE_ALT_PERS_ID are outer-joined, BIRTH_DT and SSN may return NULL for persons lacking a current profile row or a currently effective SSN identifier; queries relying on SSN should account for this. Access is read-only and governed by the APPS schema's grants and any Financial Aid security profiles applied at the responsibility level.