Search Results igs_ps_unit_lgcy_pkg




Overview
Explore in AI Chat

Overview

IGS_PS_UNIT_LGCY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Student Systems (IGS) product family and specifically within the Students/Programs of Study (PS) module. Its name indicates a "legacy" unit-processing package: it encapsulates the procedural logic required to create and maintain the sub-entities that constitute a unit of study (course) offering in the institution's academic structure. Units in Oracle Student Systems are the deliverable teaching components of a program; each unit carries versioned definitions, teaching responsibilities, grading schemes, discipline associations, scheduling patterns, occurrence configurations, and physical delivery details such as building and room references.

The package is part of a layered architecture. It depends upon IGS_PS_GENERIC_PUB for shared generic-unit processing utilities and is itself referenced by IGS_PS_CREATE_GENERIC_PKG, IGS_PS_GENERIC_PVT, IGS_PS_UNIT_LGCY_PVT, and its own specification, confirming that it functions as a building block invoked primarily by higher-level public and private APIs rather than directly by end users. The documented API classification is OTHER, meaning it is an internal supporting package rather than a formally published external integration API.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions, all oriented toward constructing the dependent records of a unit version:

  • CREATE_UNIT_VERSION — creates a version record for a unit, establishing the effective-dated definition of the unit offering.
  • CREATE_TEACH_RESP — creates teaching responsibility records, linking staff or organisational units to the teaching of a unit version.
  • CREATE_UNIT_DISCIP — associates one or more academic disciplines with the unit.
  • CREATE_UNIT_GRD_SCH — creates the unit-level grading scheme association, defining how results are assessed and recorded.
  • CREATE_UNIT_SECTION — creates unit section records, the subdivisions of a unit used for delivery and enrolment.
  • CREATE_USEC_GRD_SCH — creates grading scheme associations at the unit section level.
  • CREATE_USEC_OCCUR — creates section occurrence records, representing scheduled instances of a section.
  • CREATE_UNIT_REF_CODE — creates unit reference code records, attaching institutional reference data to a unit.
  • CREATE_USO_INS — creates unit section occurrence instructor records, assigning instructors to occurrence events.
  • VALIDATE_UNIT_DTLS — validates unit detail data prior to insert or update, enforcing data integrity before persistence.

No parameter lists are reproduced here; each procedure's signature should be obtained from the package specification in the database.

Tables Accessed

The package reads and writes the core unit, section, and scheduling tables through APPS synonyms. These include IGS_PS_UNIT (master unit definition), IGS_PS_UNIT_DSCP (unit disciplines), IGS_PS_UNIT_GRD_SCHM (unit grading schemes), IGS_PS_TCH_RESP (teaching responsibilities), IGS_PS_UNITREQREF_CD and its sequence IGS_PS_UNITREQREF_CD_S (unit reference codes), IGS_PS_SCH_PAT_INT (scheduling pattern instances), IGS_PS_SCH_USEC_INT_ALL (section occurrence instances), IGS_PS_SCH_OCR_CFIG (occurrence configuration), and IGS_CA_INST_ALL (calendar instance data that provides the occurrence timeframes). Physical delivery information is drawn from IGS_AD_BUILDING_ALL and IGS_AD_ROOM_ALL. Reference and status values are validated against IGS_GE_REF_CD, IGS_GE_REF_CD_TYPE_ALL, and IGS_OR_STATUS. Together these tables represent the full unit-version, section, occurrence, and instructor data model.

Usage Notes

Because IGS_PS_UNIT_LGCY_PKG is referenced by IGS_PS_CREATE_GENERIC_PKG, IGS_PS_GENERIC_PVT, and IGS_PS_UNIT_LGCY_PVT, it is normally invoked indirectly. Student Systems forms and concurrent programs that create or maintain unit offerings call the higher-level generic APIs, which in turn delegate legacy-specific construction to this package. Custom extensions and data-migration scripts that must build unit sections, occurrences, or instructor assignments should prefer the published generic API layer over direct calls to this package. When direct calls are unavoidable, they should be wrapped in the standard transaction control and validation sequence: call VALIDATE_UNIT_DTLS prior to committing, honour the calendar instance and scheduling pattern data, and ensure referenced building, room, reference code, and status values already exist. Given its legacy designation, adopters upgrading between 12.1.1 and 12.2.2 should treat the package as internal and confirm signature stability against the deployed specification.