Search Results igs_ps_unit_lgcy_pvt




Overview
Explore in AI Chat

Overview

The APPS.IGS_PS_UNIT_LGCY_PVT package body is a private PL/SQL API in the Oracle EBS Student System (IGS) product family. Its name follows the Oracle naming convention in which IGS_PS denotes the Student Systems "Prospective Student" or program/unit-of-study domain, and the _PVT suffix signals that the package is a private companion to a corresponding public API. The private designation means the package is not intended to be called directly by external consumers; instead, it encapsulates the low-level processing logic (validation, legacy data handling, and record-level processing) that is invoked by the public layer and by the legacy unit package IGS_PS_UNIT_LGCY_PKG.

The object carries the status VALID in the APPS schema and holds one documented program unit. In the broader IGS architecture, packages named with the LGCY token support migration or compatibility processing of legacy (pre-upgrade or externally sourced) academic unit data, ensuring that inherited records can be reconciled with the current Student System data model.

Key Procedures and Functions

The ETRM documentation records a single program unit for this package:

  • CREATE_UNIT — The principal entry point of the private body. It creates a unit (academic unit-of-study/offering) record based on the supplied legacy source data. As a private API, it is expected to be called by the public wrapper or companion package rather than by end-user code. The procedure encapsulates the insert and related validations needed to materialize the legacy unit into the IGS tables.

Because the metadata lists only this one procedure, no other entry points are documented. Customizations should avoid calling CREATE_UNIT directly, since private APIs carry no backward-compatibility guarantee across releases.

Tables Accessed

The dependency listing identifies PLITBLM (via a PUBLIC synonym) as the only table-level reference. PLITBLM is an Oracle-supplied PL/SQL internal dictionary table used by the PL/SQL engine; it is not an application data table belonging to IGS. This indicates that the package's documented data manipulation is not expressed through direct application-table references in the ETRM extract — the substantive inserts and validations are more likely performed indirectly through its dependencies, notably IGS_PS_UNIT_LGCY_PKG and IGS_PS_GENERIC_PUB, which carry the actual IGS table access.

Usage Notes

The package is a private member of the IGS API stack and is not referenced by any database object according to the metadata, confirming its internal role. It depends on standard Oracle EBS infrastructure packages — FND_API, FND_MESSAGE, FND_MSG_PUB, and FND_LOG — which provide the standard API return-status handling, message-stack management, and logging facilities required by EBS public/private API pairs. It also depends on IGS_PS_UNIT_LGCY_PVT (its own specification) and IGS_PS_UNIT_LGCY_PKG, its legacy processing companion.

Typical invocation occurs during legacy unit conversion or data migration routines, where the public legacy package calls into this private layer to perform the actual unit creation. Because ETRM lists it as referenced by two other packages, it functions purely as a subordinate implementation module. Developers supporting or troubleshooting legacy unit loads in EBS 12.1.1 or 12.2.2 should trace execution from the public API downward into this body, using FND log output for diagnostics. Direct modification is not recommended; any extension should be implemented in custom code that calls the supported public API instead.