Search Results igs_pr_class_std_pkg




Overview
Explore in AI Chat

Overview

IGS_PR_CLASS_STD_PKG is an Oracle Applications (APPS) PL/SQL package belonging to the Oracle Student System (formerly Oracle Student Systems, now part of Oracle E-Business Suite releases 12.1.1 and 12.2.2). The IGS prefix identifies it as a Student System object, and the PR component associates it with the Prospect/Recruitment functional area. The CLASS_STD designation indicates that the package manages "class standing" reference data — the codes and descriptions used to categorize an applicant's or student's academic standing (for example, freshman, sophomore, junior, senior, or equivalent classifications used in admissions and progression evaluation).

The package is documented in the ETRM as having an API classification of OTHER, meaning that while it is a stored database object, it is not designated as a formally supported open interface or public API. It is primarily an internal data-maintenance package, providing the standard row-level DML operations used by other Student System components to create, update, lock, and validate records in the associated class-standing tables. Its status is VALID, confirming that it is a compiled and active object in the APPS schema.

Key Procedures and Functions

The ETRM metadata documents seven procedures/functions within the package. Their names follow the conventional Oracle Forms and Table-API style:

  • INSERT_ROW — Inserts a new class-standing record into the base table. This is the primary creation routine used when a new classification code is defined.
  • UPDATE_ROW — Modifies an existing class-standing record, writing changes to the base table.
  • LOCK_ROW — Acquires a row-level lock on a class-standing record, typically used to prevent concurrent modification before an update.
  • ADD_ROW — Combines the logic of creating a record and its associated descriptive row, commonly inserting into both the base table and its _S (translation/descriptive) counterpart.
  • GET_PK_FOR_VALIDATION — Retrieves the primary key of a class-standing record for validation purposes, allowing callers to verify existence and identity.
  • GET_UK_FOR_VALIDATION — Retrieves the unique key for validation, supporting duplicate detection and referential checks.
  • BEFORE_DML — A pre-DML trigger routine that enforces standard WHO-column population and validation rules prior to insert, update, or delete operations.

No parameter lists are documented in the ETRM metadata, and none are inferred here.

Tables Accessed

The package references the following tables through APPS synonyms:

  • IGS_PR_CLASS_STD — The base table holding class-standing codes, descriptions, and related attributes. This is the primary target of INSERT_ROW, UPDATE_ROW, and LOCK_ROW.
  • IGS_PR_CLASS_STD_S — The supplementary/translation table for IGS_PR_CLASS_STD, storing descriptive or translated text linked to the base record. It is populated by ADD_ROW and maintained alongside the base row.
  • DUAL — The standard Oracle single-row dummy table, used for routine value retrieval and validation queries that do not require a physical table.

Usage Notes

IGS_PR_CLASS_STD_PKG is referenced by seven other packages, including IGS_AS_GPC_CLS_STNDG_PKG, IGS_EN_SPA_TERMS_PKG, IGS_EN_STDNT_PS_ATT_PKG, IGS_FI_FEE_AS_RATE_PKG, IGS_PR_CSS_CLASS_STD_PKG, IGS_PR_RU_APPL_PKG, and IGS_PS_CREATE_GENERIC_PKG. This dependency footprint indicates that class-standing maintenance is invoked indirectly from admissions processing, enrollment term handling, attendance processing, fee assessment, and prospect/application creation flows.

Because the package is classified as OTHER rather than as a supported API, customers and integrators should treat it as an internal object. Direct invocation from custom code is possible but unsupported; the preferred approach is to maintain class-standing definitions through the corresponding Oracle EBS Forms or concurrent programs, which call these procedures on the user's behalf. When extending or troubleshooting, the BEFORE_DML routine should be reviewed to confirm WHO-column and validation behavior, and validation routines should be used to ensure referential integrity before inserting or updating rows in IGS_PR_CLASS_STD.