Search Results get_fk_igs_az_groups




Overview
Explore in AI Chat

Overview

IGS_AZ_ADVISORS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the advisor management functionality of the Oracle Student System (formerly Oracle iLearning/Recruiting, marketed under the Student System / ETRM enterprise education product suite). Advisors are the academic staff members assigned to students, applicants, or advisee groups within an institution's student records, and this package encapsulates the core data-manipulation and validation logic for the IGS_AZ_ADVISORS entity. It operates as a table-handler style package rather than a public business API, providing low-level row operations (insert, update, lock, delete) that the higher-level advising relationship packages and Oracle Forms blocks invoke. The package is documented as VALID in APPS and is classified under API classification OTHER, indicating it is intended primarily for internal consumption by the Student System application rather than external integration.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within the package:

  • INSERT_ROW — Inserts a new advisor record into the base table, populating the primary key and audit columns.
  • ADD_ROW — Provides an alternate insertion path, typically used when a row is added from a form block with a different initialization sequence than INSERT_ROW.
  • UPDATE_ROW — Updates the mutable attributes of an existing advisor record, including the who-columns (last updated by, last update date).
  • DELETE_ROW — Removes an advisor record from the base table.
  • LOCK_ROW — Issues a SELECT ... FOR UPDATE against the advisor row to obtain a pessimistic lock, preventing concurrent modification while a form transaction is in progress.
  • GET_PK_FOR_VALIDATION — Returns the primary key of the advisor row so parent packages and relationship handlers can validate foreign-key references before committing dependent rows.
  • GET_UK_FOR_VALIDATION — Returns the unique key of the advisor row, supporting uniqueness validation on the natural/business key of the advisor entity.
  • GET_FK_IGS_AZ_GROUPS — Resolves the foreign key that links an advisor record to the IGS_AZ_GROUPS table, enabling validation of the advisor-to-group association.
  • BEFORE_DML — A housekeeping procedure invoked before DML operations to enforce mandatory-column and who-column defaults.

Tables Accessed

The package reads and writes the advisor base table IGS_AZ_ADVISORS and its translated/attribute companion IGS_AZ_ADVISORS_S, both accessed through APPS synonyms. _S tables in the ETRM schema traditionally hold translated descriptive columns or supplementary attributes, with the base table storing the untranslated business columns and keys. Via GET_FK_IGS_AZ_GROUPS, the package implicitly references IGS_AZ_GROUPS to resolve and validate the group foreign key. SYS.STANDARD appears as a system dependency, reflecting the use of standard PL/SQL built-ins.

Usage Notes

IGS_AZ_ADVISORS_PKG is referenced by three other packages: IGS_AZ_ADVISING_RELS_PKG (which manages advising relationships), IGS_AZ_GROUPS_PKG (which manages advisee/advisor groups), and the generated package/relationship artifact IGS_AZ_GEN_001, plus a self-reference within the package body. This dependency chain confirms that the package sits at the bottom of the advisor data-access stack: it is called by group and relationship packages rather than calling them. It is characteristically invoked from Oracle Forms data blocks (via block-level triggers such as ON-INSERT, ON-UPDATE, ON-DELETE, and ON-LOCK) when users maintain advisors in the Student System administrative forms. Concurrent programs that load or migrate advisor data for the ETRM/Student System may also call the INSERT_ROW and ADD_ROW entry points. Direct custom-code invocation is generally discouraged; integrators should prefer the public advising relationship and group APIs, using the GET_* validation functions only for key resolution. The package shares the APPS schema and is therefore subject to the standard EBS editioning and synonym conventions in both 12.1.1 and 12.2.2 environments.