Search Results igs_as_unit_mode_pkg




Overview
Explore in AI Chat

Overview

IGS_AS_UNIT_MODE_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the Student System (IGS) product family. Its name and dependency footprint identify it as the underlying table-handling (TAPI-style) package for the IGS_AS_UNIT_MODE entity — the assessment unit mode definition, which controls how a unit's assessment is offered or delivered (for example, the mode of study or assessment under which a unit version is assessed). The package encapsulates all Data Manipulation Language (DML) and validation logic against the IGS_AS_UNIT_MODE table so that the base table is never touched directly by forms, concurrent programs, or custom extensions. In ETRM terms it is classified as an OTHER API, meaning it is a supporting internal API rather than a public, documented business API.

Key Procedures and Functions

The package body exposes eight documented procedures and functions:

  • INSERT_ROW — Performs the core insert of a new IGS_AS_UNIT_MODE record, including WHO column population through FND_GLOBAL.
  • UPDATE_ROW — Applies changes to an existing unit mode record.
  • DELETE_ROW — Removes a unit mode record, typically subject to referential and business validation via CHECK_CONSTRAINTS.
  • ADD_ROW — The user-facing add routine that orchestrates validation before delegating to INSERT_ROW.
  • LOCK_ROW — Obtains a row-level lock on the target unit mode record to preserve concurrency integrity during update or delete processing.
  • GET_PK_FOR_VALIDATION — Resolves the primary key needed by downstream validation logic, ensuring the correct record context is established before checks execute.
  • CHECK_CONSTRAINTS — Centralises business-rule and referential validation for the entity, raising errors via FND_MESSAGE and IGS_GE_MSG_STACK when constraints are violated.
  • BEFORE_DML — A pre-DML hook that enforces mandatory column defaults, validation state alignment, and audit attribute setup before the INSERT_ROW, UPDATE_ROW, or DELETE_ROW routines proceed.

Tables Accessed

The only table documented as referenced through APPS synonyms is IGS_AS_UNIT_MODE, the base entity table this package owns and maintains. All procedural logic in the package is anchored on that table; the remaining dependencies are other PL/SQL packages rather than tables, including IGS_AD_PS_APLINSTUNT_PKG, IGS_AS_ITEM_ASSESSOR_PKG, IGS_AS_UNIT_CLASS_PKG, IGS_FI_FEE_AS_RATE_PKG, IGS_FI_FTCI_ACCTS_PKG, IGS_PS_VAL_UM, and the shared infrastructure packages APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, and IGS_GE_MSG_STACK. These dependencies indicate that unit-mode maintenance has touch points with assessment item assessor assignment, unit classification, admission applicant-instance-unit data, fee assessment rates, and fee account derivation — the validation performed by CHECK_CONSTRAINTS and BEFORE_DML is therefore likely to consult those neighbouring packages rather than only the local table.

Usage Notes

This package is not referenced by any other database object according to the documented dependency report, but it itself references five or more peer packages. It is therefore invoked directly, not through an upstream wrapper. Typical invocation paths in 12.1.1 and 12.2.2 include:

  • Oracle Forms maintenance screens within the Student System assessment module that create, update, or delete unit mode setup records.
  • Concurrent programs or setup loaders that populate unit assessment mode data during implementation or data migration.
  • Custom PL/SQL extensions that call ADD_ROW, UPDATE_ROW, or DELETE_ROW to preserve WHO-column and validation integrity instead of issuing direct SQL against IGS_AS_UNIT_MODE.

Because the package is a private OTHER-classified API, direct calls should be treated as internal and subject to change between releases. Custom code should respect the BEFORE_DML and CHECK_CONSTRAINTS validation path — calling ADD_ROW, UPDATE_ROW, or DELETE_ROW rather than INSERT_ROW, UPDATE_ROW, or DELETE_ROW in isolation — to avoid bypassing business rules and leaving orphaned or inconsistent unit mode records.