Search Results get_fk_igs_ps_ver

Overview

IGS_PS_CATEGORISE_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, documented in ETRM for release 12.1.1 and applicable to 12.2.2. It belongs to the Oracle Student System (formerly Oracle iLearning/Student System, product family "IGS") and exposes the transactional API for the IGS_PS_CATEGORISE_ALL entity, which stores the categorisation of course versions within the student system's course catalogue. Categorisation associates a course code and version with a course category, providing the classification structure used by admissions, enrolment, curriculum and reporting processes.

The package is declared AUTHID CURRENT_USER, so executing privileges follow the invoking schema rather than the package owner. It is classified under API classification OTHER, meaning it is a generated-style table handler API rather than a business flow API, and it is referenced by three other packages, confirming its role as a dependent validation utility. The unit carries the header marker IGSPI09S.pls, version 115.4, last shipped 2002/11/29, which indicates a long-stable interface retained through the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• INSERT_ROW — Inserts a categorisation row for a course code, version number and course category, returning the ROWID. It accepts a mode flag (default 'R') and an ORG_ID for multi-org handling.
• LOCK_ROW — Acquires a row-level lock on an existing categorisation record, keyed by ROWID together with course code, version number and course category, to support optimistic concurrency control.
• DELETE_ROW — Deletes a categorisation row identified by ROWID.
• GET_PK_FOR_VALIDATION — Boolean function validating that the supplied primary key (course code, version number, course category) exists. Typical of generated APIs, it is used by foreign-key validation triggers and by callers needing existence checks before DML.
• GET_FK_IGS_PS_CAT — Foreign-key validation procedure resolving the IGS_PS_CAT (course category) reference for a given course category code.
• GET_FK_IGS_PS_VER — Foreign-key validation procedure that resolves the IGS_PS_VER (course version) reference for a supplied course code and version number. This is the routine attached to the "get_fk_igs_ps_ver" search term and is the mechanism by which the categorisation table enforces its relationship to the course version entity.
• CHECK_CONSTRAINTS — Validates column-level constraints, optionally scoped to a named column and value.
• BEFORE_DML — Central pre-DML handler invoked before insert, update or delete. It receives the action code and the full column set — course code, version number, course category, who-columns, dates and ORG_ID — and applies WHO column defaults and cross-field validation consistently across the API.

Tables Accessed

The documented table is IGS_PS_CATEGORISE_ALL, reached through an APPS synonym. This is the single base table the package maintains: INSERT_ROW, LOCK_ROW and DELETE_ROW operate directly on it, while GET_PK_FOR_VALIDATION and CHECK_CONSTRAINTS verify its keys and constraints. The _ALL suffix designates a multi-org (partitioned by ORG_ID) table, which explains the ORG_ID parameter threaded through INSERT_ROW and BEFORE_DML. The two GET_FK procedures reference the parent entities IGS_PS_CAT and IGS_PS_VER rather than writing to them; they exist so that foreign-key values flowing into IGS_PS_CATEGORISE_ALL are resolved and validated against those parent tables.

Usage Notes

The package is invoked indirectly rather than by end users. Oracle Forms built on the IGS_PS_CATEGORISE_ALL block call INSERT_ROW, LOCK_ROW, DELETE_ROW and CHECK_CONSTRAINTS through the standard generated form-to-API pattern, while BEFORE_DML executes automatically as the pre-DML trigger body. GET_FK_IGS_PS_CAT and GET_FK_IGS_PS_VER are called by the foreign-key validation logic attached to the category and course version items, and GET_PK_FOR_VALIDATION supports primary-key validation in dependent forms. The three packages that reference IGS_PS_CATEGORISE_PKG do so for existence and FK checks before performing their own DML. Custom code should call the per-row procedures rather than issuing direct DML against IGS_PS_CATEGORISE_ALL, so that WHO columns, ORG_ID defaulting and constraint checks are applied. Standard practice is to set the FND_GLOBAL context (user, responsibility, org) before invocation; because the package is AUTHID CURRENT_USER, grants on the underlying objects must be in place for the calling schema. No concurrent program is documented as a direct entry point.