Search Results igs_pe_relationships_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_PE_RELATIONSHIPS_PKG package body is a PL/SQL implementation within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that supports the Higher Education / Student Systems module, specifically the People (IGS_PE) product family. Its principal business function is to manage relationship data between parties registered in the Trading Community Architecture (TCA) model. In academic institutions using Oracle Student System, individuals such as students, faculty, applicants, and their associated contacts (guardians, emergency contacts, sponsors) must be linked through defined relationship types. This package encapsulates the logic required to create or update those party relationships and to replicate address and usage information across related party records.

The package is documented as VALID in the APPS schema and is classified under API classification OTHER. It acts as a wrapper layer that abstracts the underlying TCA public APIs, notably HZ_PARTY_V2PUB and HZ_RELATIONSHIP_V2PUB, thereby presenting a higher-level, institution-specific interface for relationship maintenance. It is not referenced by any database object, but it is referenced by six other packages, indicating that it functions as a shared service component invoked by higher-level IGS_PE processing routines.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions within this package body:

  • CREATUPDATE_PARTY_RELATIONSHIP — This routine serves as the primary entry point for creating or updating a relationship between two parties. It orchestrates the invocation of the underlying TCA relationship APIs, validates relationship type definitions, and manages the message stack (IGS_GE_MSG_STACK) and the FND message publishing framework (FND_MSG_PUB) to surface errors and warnings. It leverages the standard FND_API exception-handling model to ensure transactional consistency and error reporting.
  • COPY_ADDRESS_AND_USAGE — This routine supports the propagation of address and party site usage information from one party or site to another. It interacts with location, party site, and party site use entities to replicate address records and their associated usage classifications, ensuring that related parties share consistent address data where required by institutional policy.

Parameter lists are not documented in the supplied metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes to a range of TCA and IGS_PE tables accessed through APPS synonyms:

  • HZ_PARTIES and HZ_PARTY_NUMBER_S — the core party entity and its sequence for generating party numbers when new party records are involved in relationships.
  • HZ_RELATIONSHIP_TYPES — validates that the requested relationship conforms to a defined relationship type.
  • HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES — support the address and usage copy routine by providing the location, site, and site-use records that are duplicated across parties.
  • IGS_PE_HZ_PTY_SITES — an institution-specific intersection table linking IGS_PE person data to TCA party sites.
  • DUAL — used for simple PL/SQL expression evaluation.

The package additionally depends on views such as IGS_PE_PERSON_BASE_V, IGS_PE_PERSON, and IGS_PE_ADDR_V, and on utility packages including IGS_PE_HZ_REL_PKG, IGS_PE_PARTY_SITE_USE_PKG, IGS_PE_PERSON_ADDR_PKG, and IGS_PE_PERSON_PKG.

Usage Notes

IGS_PE_RELATIONSHIPS_PKG is typically invoked from higher-level IGS_PE packages, Oracle Forms within the Student System responsibility, or custom concurrent programs that process person and contact data. Because it is referenced by six other packages, it is generally not called directly by end users but rather as part of broader person registration, applicant processing, or contact maintenance flows. Developers extending Oracle Student System functionality should invoke the documented procedures rather than calling the underlying HZ public APIs directly, in order to preserve the validation, message-stack integration, and error handling that this package provides. As with all TCA-integrated APIs, callers should be aware of commit and rollback semantics defined by the FND_API transaction model.