Search Results igs_pr_ou_unit_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_PR_OU_UNIT_PKG package is a database-tier PL/SQL component within the Oracle E-Business Suite (EBS) release 12.1.1 and 12.2.2, residing in the APPS schema. It belongs to the Oracle Student System / Student Records (IGS) product family, which manages academic structures, program enrollments, and unit (course/module) offerings. The package encapsulates the persistence and validation logic for the IGS_PR_OU_UNIT entity, which associates an academic unit with an organizational unit (OU) offering context — a relationship central to defining where and how a unit is delivered within an institution.

In the ETRM documentation the package is classified as an OTHER API object, meaning it is not exposed as a formal public API but is instead invoked internally by related packages and forms. Its design follows the standard Oracle Forms-generated table handler pattern, providing the canonical DML verbs and constraint-checking logic needed to keep the underlying table consistent. The package is documented as VALID, confirming that its compiled specification and body exist in the target environment.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions that constitute the package's table-handler interface:

  • INSERT_ROW — Inserts a new record into the underlying unit/OU offering table.
  • UPDATE_ROW — Applies changes to an existing row based on its primary key.
  • DELETE_ROW — Removes a row from the table.
  • ADD_ROW — Adds a row to the in-memory record group; typically used in conjunction with Forms block processing before an actual insert.
  • LOCK_ROW — Acquires a row-level lock to enforce concurrency control during update operations.
  • GET_PK_FOR_VALIDATION — Retrieves the primary key values needed to validate the current record against the database.
  • GET_FK_IGS_PR_RU_OU — Returns the foreign key value linking the row to the related registered-unit/OU entity.
  • GET_FK_IGS_PS_UNIT — Returns the foreign key value linking the row to the Academic Unit definition.
  • CHECK_CONSTRAINTS — Performs business and referential-integrity checks before committing DML, ensuring the OU/Unit association is valid.
  • BEFORE_DML — A pre-DML hook invoked before insert, update, or delete to apply auditing, populate WHO columns, or enforce preconditions.

Parameter lists are not enumerated in the metadata; the descriptions above reflect documented purpose only.

Tables Accessed

The package operates on a single documented base table, referenced through an APPS synonym:

  • IGS_PR_OU_UNIT_ALL — The multi-org (ALL) table that stores the organizational unit to academic unit associations. The package reads from it during validation and foreign-key lookups and writes to it during insert, update, and delete operations.

Referential dependencies are enforced against the parent entities represented by the foreign-key lookups GET_FK_IGS_PR_RU_OU (registered-unit/OU) and GET_FK_IGS_PS_UNIT (unit definition), while constraint validation in CHECK_CONSTRAINTS safeguards these relationships.

Usage Notes

IGS_PR_OU_UNIT_PKG is not intended for direct invocation by external integrations. The ETRM dependency report shows that it is referenced by four other packages — IGS_PR_GEN_004, IGS_PR_GEN_006, IGS_PR_RU_OU_PKG, and IGS_PS_UNIT_PKG — indicating that it is called recursively within the student records package suite, most commonly from Forms-driven maintenance of unit offerings. Its procedural signature mirrors Oracle Forms table handlers, so it is typically triggered when a user inserts, updates, or deletes a unit/OU association through an EBS form or via a concurrent program that programmatically populates the same entity. In the dependency graph, the package itself references SYS.STANDARD, confirming that it uses only core PL/SQL built-ins and does not depend on external database packages. Custom code should prefer the higher-level packages (e.g., IGS_PR_RU_OU_PKG) rather than calling this handler directly, thereby ensuring all validation and auditing rules remain intact.