Search Results igs_fi_parties_v




Overview
Explore in AI Chat

Overview

IGS_FI_PARTIES_V is a reporting and integration view in the Oracle E-Business Suite IGS (Student System) product family. It consolidates party records of type PERSON and ORGANIZATION alongside their associated person-level context, exposing a single denormalized result set for downstream consumers. The view is documented as belonging to IGS — Student System (Obsolete), and its ETRM entry records that it is "Not implemented in this database," so in many environments the object will not be present or will exist only where the legacy student modules were deployed. The documentation spans ETRM 12.2.2, and the object is equally relevant to 12.1.1 installations carrying the same obsolete IGS code. Its principal role is to present a unified read-only projection over the Oracle Trading Community Architecture (TCA) party model (HZ_PARTIES and HZ_PERSON_PROFILES) enriched with IGS-specific person data.

Underlying Base Objects

Although the ETRM metadata records no formally documented base objects, the view text identifies the tables and views joined in its definition. The driving table is HZ_PARTIES, aliased P, restricted to party types PERSON and ORGANIZATION and excluding parties whose STATUS is 'M' (merged) or 'D' (deceased/disabled per TCA coding). It is outer-joined to IGS_PE_HZ_PARTIES (PD), HZ_PERSON_PROFILES (PP), IGS_PE_PERSON_ID_TYPE_V (PIT), and FND_LOOKUP_VALUES_VL (L1). All joins to the IGS and profile objects use the Oracle outer-join (+) syntax, so a party row survives even if no matching person profile, IGS context, or lookup value exists.

Notable join predicates include the gender lookup constrained to LOOKUP_TYPE = 'HZ_GENDER', VIEW_APPLICATION_ID = 222, and SECURITY_GROUP_ID = 0, and the person profile restricted to CONTENT_SOURCE_TYPE = 'USER_ENTERED' with SYSDATE between its effective start and end dates (the end date defaulting to SYSDATE). The selection also invokes IGS_EN_GEN_003.ENRP_GET_ENCMBRD_IND to derive an encumbrance indicator for each party.

Key Columns

The view exposes identifiers, person attributes, lookup meanings, and audit columns:

Common Use Cases and Queries

Typical consumption is read-only reporting, student data extracts, and integration payloads that need a flattened party-plus-person record. A representative query follows:

  • Retrieve active persons and organizations — SELECT PARTY_ID, PARTY_TYPE, FULL_NAME, SEX_MEANING, BIRTH_DT FROM IGS_FI_PARTIES_V WHERE PARTY_TYPE = 'PERSON';
  • Filter for encumbered parties — SELECT PERSON_NUMBER, FULL_NAME FROM IGS_FI_PARTIES_V WHERE ENCUMBERED_IND = 'Y';
  • Extract for integration — select PERSON_ID, API_PERSON_ID, and audit columns to stage records for downstream systems, joining back to HZ_PARTIES for any attributes not projected here.

Because the object is documented as obsolete and not implemented, consumers should confirm its existence in the target instance before relying on it, and prefer supported TCA views where the student-specific context is not required.