Search Results igs_ad_cd_pkg




Overview
Explore in AI Chat

Overview

IGS_AD_CD_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API type rather than a public, fully-supported API. It belongs to the Oracle Student System (formerly Oracle Student Administration, hence the IGS_ prefix) family of packages and serves as the primary data-access layer for the IGS_AD_CD entity, which stores admissions "code" reference data used across the admissions subsystem. The package encapsulates the standard Oracle Forms-style table handler pattern: insert, update, delete, lock, and pre-DML validation logic, along with foreign-key lookup helpers and primary-key retrieval routines. It is not a business-process API in the sense of a workflow or concurrent-program entry point; rather, it is a low-level internal DML utility invoked by other admissions packages and by the forms that maintain the underlying table. Its status is VALID in both 12.1.1 and 12.2.2, and it references only SYS.STANDARD among external objects, confirming that it relies on core PL/SQL built-ins and the IGS_AD_CD table via an APPS synonym.

Key Procedures and Functions

The package exposes ten documented procedures and functions, organized around the DML lifecycle of the IGS_AD_CD table.

  • INSERT_ROW — Inserts a new record into IGS_AD_CD, applying the package's standard column defaulting and validation rules.
  • UPDATE_ROW — Updates an existing record in IGS_AD_CD based on the primary key supplied by the caller.
  • DELETE_ROW — Removes a record from IGS_AD_CD, subject to the package's referential-integrity checks.
  • LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) on the target record to serialize concurrent modifications from multiple forms sessions.
  • ADD_ROW — A wrapper-style entry point that coordinates insertion logic, typically invoked from Forms trigger code.
  • GET_PK_FOR_VALIDATION — Returns the primary key value for a given record so that validation logic in calling packages can confirm existence before proceeding.
  • CHECK_CONSTRAINTS — Enforces the package's business and referential constraints prior to DML, raising errors when validation fails.
  • BEFORE_DML — A pre-DML hook executed before insert, update, or delete operations; centralizes mandatory-column checks and audit stamping.
  • GET_FK_IGS_AD_BASIS_FOR_AD — Foreign-key lookup returning the basis-for-admission code associated with a given record.
  • GET_FK_IGS_AD_TAC_AD_CD — Foreign-key lookup returning the TAC (Transfer Admission Code) reference associated with a given record.

No parameter lists are documented in the ETRM metadata; callers should obtain signature details from the package source or the Oracle Student System data model documentation.

Tables Accessed

The only table documented as accessed through APPS synonyms is IGS_AD_CD. This table stores the admissions code values that other admissions entities reference. The package reads from it in the GET_FK_* and GET_PK_FOR_VALIDATION routines, and writes to it in INSERT_ROW, UPDATE_ROW, DELETE_ROW, and ADD_ROW. LOCK_ROW and BEFORE_DML operate against the same table. Because the package performs full CRUD against this single entity and exposes foreign-key getters, it functions as the canonical maintenance point for the IGS_AD_CD reference data set within the admissions module.

Usage Notes

IGS_AD_CD_PKG is referenced by three other packages: IGS_AD_BASIS_FOR_AD_PKG, IGS_AD_PS_APPL_PKG, and IGS_AD_TAC_AD_CD_PKG. This dependency pattern indicates that the package is invoked indirectly whenever those higher-level admissions packages need to validate or retrieve IGS_AD_CD records—for example, during applicant processing, basis-for-admission determination, and transfer-admission-code assignment. In practice, the primary direct caller is the Oracle Forms application that maintains the admissions code setup screens, where LOCK_ROW, INSERT_ROW, UPDATE_ROW, and DELETE_ROW are wired into standard block triggers and BEFORE_DML is invoked in the pre-insert/pre-update trigger. Custom code and extension developers should treat this as an internal, unsupported API: it is not published in the Oracle Integration Repository as a supported interface, and the ETRM classification "OTHER" confirms it lacks the stability guarantees of a public API. Direct modification of IGS_AD_CD outside this package risks bypassing the constraint checks centralized in CHECK_CONSTRAINTS and BEFORE_DML. When troubleshooting admissions reference-data issues in 12.1.1 or 12.2.2, developers should inspect the package body and trace callers through the three dependent packages rather than assuming documented parameter signatures, since the ETRM entry lists procedure names only.