Search Results igs_ps_ver_pkg




Overview
Explore in AI Chat

Overview

IGS_PS_VER_HIST_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Student System (IGS) product family, specifically the version-history mechanism used by the Program of Study / Program Versioning (IGS_PS_VER) components. Its role is to persist and maintain historical records of versioned academic program data. Where the primary program-version entity (IGS_PS_VER) holds current definitional data, IGS_PS_VER_HIST_ALL retains the audit trail of changes to those versions across their lifecycle. IGS_PS_VER_HIST_PKG encapsulates the insert, update, lock, delete, and pre-DML validation logic required to maintain that history safely and consistently.

Because entities in the Student System are strongly versioned and carry effective dates, direct DML against history tables is not advisable. Instead, this package provides the sanctioned API surface used by higher-level program-version processing to write history rows. The package is classified as OTHER in the ETRM metadata, indicating that it is an internal supporting package rather than a public, business-facing API, though it remains a documented and valid database object.

Key Procedures and Functions

The package exposes eight documented procedures and functions:

  • INSERT_ROW — inserts a new history record into the underlying history table, supplying the version attributes captured at the point of change.
  • ADD_ROW — an alternate row-addition entry point, typically used to add a history row from a higher-level processing routine.
  • UPDATE_ROW — updates an existing history row when a correction or adjustment to the stored history is required.
  • DELETE_ROW — removes a history row, used when history entries must be purged or reversed.
  • LOCK_ROW — acquires a row-level lock on the target history row to serialize concurrent modifications and prevent lost updates.
  • GET_PK_FOR_VALIDATION — resolves or returns the primary key used for validation, enabling callers to confirm that the row they intend to act upon is correctly identified.
  • CHECK_CONSTRAINTS — performs data-integrity checks on the values being written, enforcing mandatory-column, foreign-key, and business-rule constraints before DML is committed.
  • BEFORE_DML — a preparatory routine invoked prior to the insert, update, or delete operation to apply standard preprocessing.

No parameter lists are documented in the ETRM metadata, so signatures are not reproduced here.

Tables Accessed

The package references the table IGS_PS_VER_HIST_ALL through an APPS synonym. This is the history (all-organization) table for versioned program-of-study data. The package reads and writes this table to store successive versions, satisfy validation lookups, and support locking and deletion. Dependency metadata also shows references to the SYS and STANDARD packages, which reflects only the standard PL/SQL runtime environment and does not indicate additional application table access.

Usage Notes

According to the dependency information, IGS_PS_VER_HIST_PKG is referenced by two other packages: IGS_PS_VER_PKG, the primary program-version package, and IGS_PS_GEN_002. This confirms that the history package is invoked indirectly through program-version processing rather than being called directly from a form or concurrent program.

In practice, the package is expected to be called by the program-version and related generation routines whenever a program version is created, amended, or superseded, ensuring that IGS_PS_VER_HIST_ALL remains synchronized with the live version entity. Custom code should avoid issuing direct DML against the history table and should instead invoke the documented procedures so that validation, locking, and pre-DML processing are honored. Because the object status is VALID and it resides in the APPS schema, it is available to any code running with APPS privileges in both EBS 12.1.1 and 12.2.2.