Search Results get_fk_igs_en_spa_terms




Overview
Explore in AI Chat

Overview

IGS_EN_PLAN_UNITS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that encapsulates the transactional logic for the IGS_EN_PLAN_UNITS entity within the Oracle Student System (formerly Oracle iLearning/Student Systems) product family. Planned units represent the enrollment-level record of study for a student, associating a person, a course, and a unit offering option (UOO) with a specific term and calendar configuration. The package functions as a table-handling API (OTHER classification in ETRM), providing a controlled programmatic interface for inserting, locking, updating, and deleting rows in the underlying IGS_EN_PLAN_UNITS table while enforcing the referential integrity and validation rules defined by the application.

Because planned units are tightly coupled to term definitions and student enrollment records, the package also exposes validation helpers that resolve primary and foreign key values at runtime. This design allows calling code — typically Oracle Forms-based enrollment screens and internal Student System packages — to perform consistent key lookups rather than embedding hard-coded queries, thereby centralizing data integrity logic.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

  • INSERT_ROW — Creates a new planned units record, accepting the full set of column values including person, course, unit offering option, term calendar type, term sequence number, and various flags such as the no-assessment indicator, core indicator, and cart error flag. It also returns the ROWID of the newly created row.
  • LOCK_ROW — Acquires a row-level lock against an existing planned units record, keyed by ROWID and the identifying column values, to support optimistic concurrency control during multi-user enrollment activity.
  • UPDATE_ROW — Modifies an existing planned units row, taking the ROWID plus updated column values and a mode parameter.
  • ADD_ROW — Inserts a planned units record and returns the generated ROWID, functioning as an alternative entry point to INSERT_ROW for callers that need the surrogate key on insert.
  • DELETE_ROW — Removes a planned units record from the table.
  • GET_PK_FOR_VALIDATION — Resolves or verifies the primary key of a planned units row for validation purposes, typically used before performing an update or delete.
  • GET_FK_IGS_EN_STDNT_PS_ATT — Validates the foreign key relationship to the IGS_EN_STDNT_PS_ATT table, confirming that the referenced student program attempt record exists.
  • GET_FK_IGS_EN_SPA_TERMS — Validates the foreign key relationship to the IGS_EN_SPA_TERMS table. This is the procedure most commonly referenced by searches for get_fk_igs_en_spa_terms, as it verifies that the term and calendar sequence combination supplied for a planned unit corresponds to a valid student program attempt term.
  • BEFORE_DML — A centralized pre-DML routine that applies standard auditing and derived column values prior to insert, update, or delete operations.
  • BEFORE_INSERT_UPDATE — Performs the specific pre-processing required only on insert and update actions, such as setting creation and modification metadata.

Tables Accessed

The package operates against two documented tables through APPS synonyms:

  • IGS_EN_PLAN_UNITS — The primary table managed by the package. All insert, update, delete, and lock operations target this table, which stores the planned unit records for student enrollments.
  • IGS_EN_SPA_TERMS — Accessed by GET_FK_IGS_EN_SPA_TERMS to validate that the term calendar type and sequence number supplied for a planned unit reference a valid student program attempt term. This ensures planned units cannot be created against invalid or non-existent term definitions.

Usage Notes

IGS_EN_PLAN_UNITS_PKG is referenced by seven other packages within the Student System, indicating that it is an embedded component of the enrollment processing chain rather than a standalone user interface object. It is typically invoked from Oracle Forms enrollment and planned unit maintenance screens, from concurrent programs that bulk-process student study plans, and from custom extensions or interfaces that need to create or modify planned unit records programmatically.

In Oracle EBS 12.1.1 and 12.2.2, callers should invoke the procedures rather than performing direct DML on IGS_EN_PLAN_UNITS, because the package's BEFORE_DML and BEFORE_INSERT_UPDATE logic maintains mandatory audit and derivation columns. When validating a term reference, GET_FK_IGS_EN_SPA_TERMS should be called before insert or update to avoid constraint violations. The package is not documented as a public API in the strict sense, so customizations should account for the possibility of signature changes across patch levels.