Search Results igs_as_untas_pattern_pkg




Overview
Explore in AI Chat

Overview

IGS_AS_UNTAS_PATTERN_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Student Systems (IGS) product family, specifically the Assessment (IGS_AS) module. The package encapsulates the database logic required to maintain the IGS_AS_UNTAS_PATTERN_ALL entity, which stores the association between teaching units (identified by unit code, version number, calendar type, and calendar instance sequence number) and assessment patterns (identified by assessment pattern ID and code). This association defines which assessment pattern applies to a given unit offering within a specific academic period, along with supporting attributes such as location, unit class, unit mode, and a default-pattern indicator.

The package follows the standard Oracle EBS generated-API pattern: row-level DML operations are wrapped in procedures that also perform primary key, unique key, and foreign key validation, constraint checking, and a before-DML hook. This design allows both the Oracle Forms-based user interface and external or custom code to maintain the underlying table through a controlled interface rather than issuing direct DML.

Key Procedures and Functions

  • INSERT_ROW — Inserts a new association row, accepting the full set of unit/pattern attributes plus an organization ID, and returning the ROWID of the new row.
  • LOCK_ROW — Acquires a row-level lock on an existing record for the supplied key values, supporting concurrency control during updates.
  • UPDATE_ROW — Modifies an existing association row identified by its ROWID and key columns.
  • ADD_ROW — Convenience wrapper that conditionally inserts or updates based on whether the row already exists.
  • DELETE_ROW — Removes the association row identified by its key.
  • GET_PK_FOR_VALIDATION — Validates and resolves the primary key of the entity.
  • GET_UK_FOR_VALIDATION — Validates the unique key constraint for the table.
  • GET_FK_IGS_AD_LOCATION — Foreign key validation against the location entity (IGS_AD_LOCATION).
  • GET_FK_IGS_AS_UNIT_CLASS — Foreign key validation against the unit class entity referenced by X_UNIT_CLASS. This is the routine returned when searching for "get_fk_igs_as_unit_class", which confirms a supplied unit class value exists before the pattern association is committed.
  • GET_FK_IGS_AS_UNIT_MODE — Foreign key validation for the unit mode attribute.
  • GET_FK_IGS_PS_UNIT_OFR_PAT — Foreign key validation linking the row to the unit offering pattern entity.
  • CHECK_CONSTRAINTS — Central validation routine that invokes the PK, UK, and FK checks before DML is performed.
  • BEFORE_DML — Pre-DML trigger-style hook that executes standard housekeeping (such as WHO column population) prior to insert or update.

Tables Accessed

The package operates on the APPS synonym IGS_AS_UNTAS_PATTERN_ALL, which is the core table holding unit-to-assessment-pattern associations. Reads, inserts, updates, and deletes against this table are performed through the row-level procedures. Foreign key validation routines reference related IGS entities (location, unit class, unit mode, and unit offering pattern), consulted to confirm referential integrity before the association row is written.

Usage Notes

IGS_AS_UNTAS_PATTERN_PKG is typically invoked from the Assessment module's Oracle Forms screens when an administrator defines or maintains unit assessment patterns. The Forms trigger code calls LOCK_ROW, then INSERT_ROW, UPDATE_ROW, ADD_ROW, or DELETE_ROW as appropriate, relying on CHECK_CONSTRAINTS and the GET_FK_* routines to surface validation errors interactively. The package is also referenced by two other APPS packages, indicating reuse by higher-level assessment processing logic. Custom integrations that need to create unit-pattern associations programmatically should call ADD_ROW or INSERT_ROW with X_MODE set correctly, rather than inserting directly into IGS_AS_UNTAS_PATTERN_ALL, to preserve multitenancy (X_ORG_ID) and validation behaviour. Because the header indicates a 2005 file version, the package remains stable across EBS 12.1.1 and 12.2.2 with no functional difference at the API level.