Search Results igs_ps_course_pkg




Overview
Explore in AI Chat

Overview

IGS_PS_COURSE_PKG is a PL/SQL package in the APPS schema that encapsulates the core database logic associated with the IGS_PS_COURSE entity in Oracle E-Business Suite. In the Oracle Student System (formerly Oracle iLearning/Student Administration) data model, the IGS product set covers the academic structure — programs, courses, versions, and offerings. IGS_PS_COURSE represents the course catalogue record itself, and the package body exists to centralize the DML and validation logic applied to that table so that multiple calling modules share a single, consistent implementation.

The package is classified as OTHER in the ETRM documentation, meaning it is a table-handler style package rather than a true public business API. It provides the row-level insert, lock, delete, and constraint-checking operations that a TCA-style table handler would typically expose, together with a BEFORE_DML hook that allows dependent logic to be applied before a row is committed. The body is documented as VALID in both 12.1.1 and 12.2.2, and it is not referenced by any other database object, confirming its role as a server-side utility rather than a dependency of other compiled code.

Key Procedures and Functions

Six procedures and functions are documented for this package:

  • INSERT_ROW — Performs the insertion of a new course record into IGS_PS_COURSE, populating the mandatory columns and standard WHO columns from the session context.
  • LOCK_ROW — Obtains a row-level lock on an existing course record, typically selecting the row with FOR UPDATE semantics to serialize concurrent modification.
  • DELETE_ROW — Removes a course record from IGS_PS_COURSE, subject to the integrity rules enforced by the package.
  • GET_PK_FOR_VALIDATION — Returns the primary key values needed to validate a course row, allowing callers to confirm existence and identity before performing dependent operations.
  • CHECK_CONSTRAINTS — Evaluates the business and referential constraints that must hold for the course record, raising errors via the message stack when the data is invalid.
  • BEFORE_DML — A pre-DML hook that applies defaulting, derivation, and cross-entity validation immediately before an insert, update, or delete is executed.

The precise parameter lists are not reproduced in the ETRM extract and should be confirmed against the live package specification in the target instance.

Tables Accessed

The only documented table referenced through APPS synonyms is IGS_PS_COURSE. This is the course catalogue base table and is the exclusive subject of the insert, lock, delete, and constraint operations described above. All reads and writes performed by the package body are directed at this table, with supporting logic supplied by the many dependent packages listed in the dependency metadata.

Usage Notes

The package body depends on a broad set of sibling packages, including IGS_PS_VER_PKG and IGS_PS_RU_PKG (course version and rules), IGS_PE_COURSE_EXCL_PKG (exclusions), IGS_PR_OU_PS_PKG and IGS_PR_STDNT_PR_PS_PKG (organizational unit and program relationships), IGS_FI_FEE_AS_PKG and IGS_PS_FEE_TRG_PKG (fee triggers), and the student application and enrolment packages such as IGS_AD_PS_APPL_PKG, IGS_AD_PS_APPL_INST_PKG, IGS_EN_STDNT_PS_ATT_PKG, and IGS_AS_NON_ENR_STDOT_PKG. Utility dependencies on APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, IGS_GE_MSG_STACK, and STANDARD indicate that the package raises messages through the standard Oracle EBS message stack and derives session context from FND_GLOBAL.

Typical invocation is from the Oracle Student System course maintenance forms, from concurrent programs that load or maintain the course catalogue, and from custom PL/SQL that must manipulate course records without bypassing the validation logic. Because the body is not referenced by any other database object, callers are expected to invoke it directly rather than relying on database triggers. Direct DML against IGS_PS_COURSE should be avoided in favour of these documented entry points, and any customization should be applied through the recommended CUSTOM library extensions rather than by modifying the package body itself.