Search Results get_fk_igs_ps_course




Overview

IGS_PR_STDNT_PR_PS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Student System (IGS) product family. Its name indicates that it supports the entity IGS_PR_STDNT_PR_PS, which holds the association between a student (person) and the courses recorded against a student program or progression record. The package provides the standard Oracle Forms-style transactional API layer for that entity, combining row-level insert, lock, and delete operations with validation helpers and foreign-key lookup routines. It is a server-side implementation package rather than a functional business API; it exposes the routines that Oracle Forms, concurrent programs, and dependent PL/SQL units call to maintain and validate rows in the underlying table. The header comment (IGSQI16S.pls) and version stamp place the package within the standard generated-API lineage used throughout the IGS schema.

Key Procedures and Functions

  • INSERT_ROW — Creates a new row in the student/course association table, accepting the person identifier, the course code and sequence number, and the associated course code, together with a mode flag.
  • LOCK_ROW — Re-queries and locks an existing row by its rowid and key columns, used by Forms to detect concurrent updates before committing changes.
  • DELETE_ROW — Removes an existing row identified by its rowid, with a mode parameter.
  • GET_PK_FOR_VALIDATION — A Boolean function that validates whether the supplied primary key values (person, course code, sequence number, and course code) resolve to an existing record.
  • GET_FK_IGS_PS_COURSE — The procedure a user searched for. It resolves the foreign-key relationship to the IGS_PS_COURSE entity, taking a course code. It is the validation/lookup handler that confirms the referenced course exists for the row being processed, and is typically invoked during row validation in the owning form.
  • GET_FK_IGS_PR_STDNT_PR_OU — Resolves the foreign-key relationship back to the student program/organizational unit context, keyed by person, course code, and sequence number.
  • CHECK_CONSTRAINTS — Performs column-level constraint validation, accepting a column name and value so the caller can validate individual attributes on demand.
  • BEFORE_DML — The pre-DML hook that applies audit-column defaults (creation date, created by, last update date, last updated by, last update login) and coordinates validation before insert, update, or delete activity.

Tables Accessed

The package operates on the base table IGS_PR_STDNT_PR_PS, accessed through its APPS synonym. This table stores the student-to-course rows maintained by the API. The foreign-key procedures additionally depend on the referenced entities — IGS_PS_COURSE (through GET_FK_IGS_PS_COURSE) and the student program/OU context (through GET_FK_IGS_PR_STDNT_PR_OU) — reading them to confirm that key values supplied for a row are valid before DML completes.

Usage Notes

This package is invoked indirectly rather than directly by end users. Oracle Forms that maintain the student/course relationship call INSERT_ROW, LOCK_ROW, DELETE_ROW, and CHECK_CONSTRAINTS as part of their block-level DML processing, with BEFORE_DML applied automatically to stamp audit columns. GET_FK_IGS_PS_COURSE and GET_FK_IGS_PR_STDNT_PR_OU are exercised during foreign-key validation, for example when an operator enters or changes a course code. Because the package is referenced by four other packages, dependent PL/SQL units in the IGS schema also call these routines. Custom code should observe the same sequence: validate the key via GET_PK_FOR_VALIDATION and the foreign keys, then perform the DML, allowing BEFORE_DML and CHECK_CONSTRAINTS to enforce integrity. As an internal generated-style API, it carries no formal public API classification beyond OTHER, and is not a business-facing interface in its own right.