Search Results igs_as_us_ai_group_pkg




Overview
Explore in AI Chat

Overview

IGS_AS_US_AI_GROUP_PKG is an Oracle Application Object Library (APPS) PL/SQL package that belongs to the Student Systems product family within Oracle E-Business Suite. The prefix "IGS" designates the Student System (formerly Oracle Student System, now part of Oracle Student Management / Higher Education), and the "AS_US_AI_GROUP" component identifies the package as the maintenance layer for the "Unit Set AI (Academic Interest / Attempt) Group" entity. In practice, this package encapsulates the Create, Read, Update, Delete (CRUD) and concurrency logic for a specific student academic grouping table, allowing other EBS components to manipulate those records without embedding direct SQL against the base tables.

Under the ETRM metadata for release 12.1.1, the package is owned by APPS and classified as an API of type OTHER rather than a fully documented public API. It exposes nine documented procedures and functions, which follow the standard Oracle Forms-generated package pattern (row locking, insert, update, delete, and validation helpers). Because the object is marked VALID and resident in the APPS schema, it is intended for internal consumption by the Student System forms, concurrent programs, and dependent PL/SQL packages rather than as a formally published integration interface.

Key Procedures and Functions

The nine documented entry points cover the full lifecycle of an AI Group record and its key validation:

  • INSERT_ROW — Inserts a new AI Group row into the underlying table, populating mandatory columns and system-derived attributes.
  • ADD_ROW — Provides an alternative additive insert path, typically used when a row must be created with default or partially derived values.
  • UPDATE_ROW — Applies changes to an existing AI Group record, preserving the primary key.
  • DELETE_ROW — Removes an AI Group record from the table.
  • LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) to enforce optimistic concurrency control before update or delete.
  • BEFORE_DML — A pre-DML hook that executes standard WHO-column and validation processing prior to insert, update, or delete.
  • GET_PK_FOR_VALIDATION — Returns the primary key value needed to validate a record against its defining context.
  • GET_UK_FOR_VALIDATION — Returns the unique-key value used for duplicate and referential validation.
  • GET_UFK_IGS_PS_UNIT_OFR_OPT — Resolves the user foreign key linking the AI Group to a Unit Offering Option (IGS_PS_UNIT_OFR_OPT), enabling cross-entity validation.

These signatures are not published in the ETRM extract; only their purposes are documented, and no parameter lists should be assumed.

Tables Accessed

The package reads and writes two documented tables accessed through APPS synonyms:

  • IGS_AS_US_AI_GROUP — The base transactional table holding AI Group records. All insert, update, delete, and lock operations target this table.
  • IGS_AS_US_AI_GROUP_S — The associated "_S" (secondary/supplementary) table that stores additional or translated attributes for the same entity, maintained in step with the base row.

Dependency data also shows the package referencing SYS.STANDARD, the standard PL/SQL package, confirming normal procedural execution. The user foreign key resolution toward IGS_PS_UNIT_OFR_OPT indicates that AI Group rows are logically tied to unit offering options in the Program/Unit Set structure.

Usage Notes

IGS_AS_US_AI_GROUP_PKG is referenced by five other APPS packages and forms: IGS_AS_SUA_AI_GROUP_PKG, IGS_PS_CREATE_GENERIC_PKG, IGS_PS_GEN_001, IGS_PS_UNITASS_ITEM_PKG, and IGS_PS_UNIT_OFR_OPT_PKG (in addition to self-reference). This dependency chain confirms the package is invoked automatically during unit offering creation, generic program generation, and unit assessment item processing — not manually by end users. Typical callers include the Student System maintenance forms for AI Groups and the Program/Unit Set generation concurrent programs, which call the insert/update/delete routines after the BEFORE_DML and LOCK_ROW steps. Customizations or interfaces should invoke these procedures within the same APPS context and honor the lock-before-update convention; because the package is classified as OTHER rather than a formal public API, Oracle does not guarantee its signature across patches, and direct SQL against IGS_AS_US_AI_GROUP should be avoided in favor of the packaged routines.