Search Results igs_or_unit_hist_pkg

Overview

The APPS.IGS_OR_UNIT_HIST_PKG package is an Oracle E-Business Suite database object classified under the OTHER API category within the Oracle Student System (OSS) product family. The IGS_OR_ prefix identifies the package as belonging to the Oracle student records / academic offerings domain, and UNIT_HIST indicates that its business scope is the management of unit history records—chronological records tracking changes to academic organizational units over time. In the context of Oracle EBS 12.1.1 and 12.2.2, this package functions as the low-level Data Manipulation Language (DML) layer that maintains and preserves historical versions of the IGS_OR_UNIT_HIST_ALL entity, ensuring that an institution retains an auditable trail of changes to its organizational units.

The package holds a VALID status in the APPS schema. Its dependency graph is narrow and self-contained: it references only the SYS-owned STANDARD package and is itself referenced by IGS_OR_GEN_001 and by its own package body. The documented structure shows eight procedures or functions, all of which relate to row-level operations and constraint management.

Key Procedures and Functions

The eight documented routines cover the full DML lifecycle for a single entity row:

• INSERT_ROW — Inserts a new unit history record into the underlying table.
• UPDATE_ROW — Modifies an existing unit history record's attributes.
• ADD_ROW — Provides a higher-level entry point for creating a row, typically wrapping validation and insert logic.
• DELETE_ROW — Removes a unit history record.
• LOCK_ROW — Acquires a row-level lock to support concurrency control and prevent simultaneous modification of the same record.
• GET_PK_FOR_VALIDATION — Retrieves the primary key of a record in order to support validation logic.
• CHECK_CONSTRAINTS — Verifies that database constraints and business validation rules are satisfied before a DML operation proceeds.
• BEFORE_DML — Serves as the pre-processing hook that executes preparatory checks immediately prior to insert, update, or delete activity.

This procedural set is a classic pattern for a generated or framework-driven ETRM package, where each method corresponds to a discrete step in the row-processing flow. No parameter lists are documented, and none should be assumed beyond what is shown.

Tables Accessed

The single documented table accessed via an APPS synonym is IGS_OR_UNIT_HIST_ALL. This table stores the historical (dated) records for organizational units, and the _ALL suffix typically denotes a multi-organization or multi-tenant aware table. The package reads and writes this table through the routines above, with GET_PK_FOR_VALIDATION and CHECK_CONSTRAINTS performing the read-oriented verification, and INSERT_ROW, UPDATE_ROW, ADD_ROW, and DELETE_ROW performing the write operations. The tight coupling to a single table confirms the package's role as a dedicated maintenance API for unit history.

Usage Notes

Given its classification as an OTHER API and its dependency on the IGS_OR_GEN_001 object, this package is typically invoked indirectly by higher-level student system code, Oracle Forms screens, or concurrent programs that maintain organizational unit structures, rather than being called directly by end users. Customizations and extensions should call the documented procedures rather than issuing direct SQL against IGS_OR_UNIT_HIST_ALL, so that CHECK_CONSTRAINTS, BEFORE_DML, and LOCK_ROW execute and preserve data integrity. Because the package graph is shallow, it is stable and low-risk across both 12.1.1 and 12.2.2 releases, and it should be treated as internal plumbing that enforces the historical accuracy of unit records.