Search Results igs_or_inst_imp_003_pkg




Overview
Explore in AI Chat

Overview

IGS_OR_INST_IMP_003_PKG is a PL/SQL package in the APPS schema belonging to the Oracle Student System (formerly Oracle iLearning / Oracle Higher Education), specifically the Institution/Organization (IGS_OR) module of Oracle EBS Release 12.1.1 and 12.2.2. The package is an inbound interface processing routine, as indicated both by the "IMP" segment of its name and by its membership in the IGS_OR_INST_IMP_xxx series. Its business function is to load, validate, and transform institution-related data delivered through the interface staging tables (those bearing the *_INT suffix) into the production Oracle HRMS/Trading Community Architecture (TCA) model — principally HZ_PARTIES and its dependent entity tables.

The package occupies the final stage of an institution import flow: source data is written into staging interface tables, and this package processes those staging records into the operational institution record, handling addresses, contacts, statistics, and notes in discrete procedural units so that partial success or failure can be isolated to a specific data domain. The package status is documented as VALID in the ETRM repository.

Key Procedures and Functions

No public parameter signatures are exposed in the ETRM metadata; the procedures are documented by name and purpose only.

Tables Accessed

The package reads its four staging interface tables — IGS_OR_INST_NTS_INT, IGS_OR_INST_STAT_INT, IGS_OR_ADR_INT, IGS_OR_ADRUSGE_INT, and IGS_OR_INST_CON_INT — and writes to the TCA base tables HZ_PARTIES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS. It references FND_LOOKUP_VALUES for code validation, FND_TERRITORIES and HZ_PHONE_COUNTRY_CODES for geographic and dialing validation, and IGS_PE_PERSON for person matching when resolving institution contacts. All object references are via APPS synonyms.

Usage Notes

IGS_OR_INST_IMP_003_PKG is an internal worker package rather than an end-user API. The ETRM dependency record shows it is referenced by the package IGS_OR_INST_IMP_001, which is the presumed orchestrating driver that sequences the domain-specific processing procedures. It is therefore invoked indirectly, typically from a concurrent program manager job launched through the institution import concurrent program chain, and is not normally called directly from Oracle Forms. Customizations should avoid modifying the package body; instead, extensions should be implemented as wrapper code invoked after the standard import job completes. Because processing mutates shared TCA tables, imports should be run within a controlled transaction and error rows should be monitored through the interface tables before reruns.