Search Results igs_as_doc_fee_stup_s

Overview

IGS_AS_DOC_FEE_STUP_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the IGS (Student Systems / Student Records) product family. The package encapsulates the server-side DML logic for the IGS_AS_DOC_FEE_STUP entity, which stores the setup of document fees applied to student assessment records. Its role is to provide a controlled, reusable layer through which forms, concurrent programs, and other PL/SQL components insert, update, lock, and delete document fee setup rows without interacting directly with the base table.

The package body is documented in ETRM as VALID at both 12.1.1 and 12.2.2. It is classified as OTHER rather than as an open interface or public API, and it is referenced by zero other database objects, indicating that it functions as a private implementation backing a specific maintenance screen rather than a shared integration point. The companion specification IGS_AS_DOC_FEE_STUP_PKG and the sequence IGS_AS_DOC_FEE_STUP_S appear among its dependencies, consistent with the standard table-handler pattern used throughout the IGS schema.

Key Procedures and Functions

The package exposes eight documented program units, which together implement a conventional Oracle Forms table handler:

• INSERT_ROW — Performs the physical insert of a new document fee setup row, populating the primary key from the sequence and applying standard WHO columns.
• UPDATE_ROW — Applies changes to an existing row identified by its primary key.
• DELETE_ROW — Removes a document fee setup record from the base table.
• LOCK_ROW — Acquires a row-level lock so that concurrent maintenance sessions cannot modify the same setup record simultaneously.
• ADD_ROW — Handles the pre-insert assignment of the surrogate key, typically by calling the sequence, before delegating to INSERT_ROW.
• GET_PK_FOR_VALIDATION — Returns the primary key values required by the validation logic so that uniqueness and referential checks can be performed.
• GET_UK_FOR_VALIDATION — Returns the unique key attribute values used to verify that a duplicate document fee setup does not already exist.
• BEFORE_DML — A pre-DML hook that centralises validation and derivation, invoking the key-retrieval routines and enforcing business rules before any insert, update, or delete proceeds.

No parameter lists are exposed in the documented metadata; callers should therefore treat these routines as internal to the form-owning module and reference the package specification for exact signatures.

Tables Accessed

Three objects are referenced through APPS synonyms:

• IGS_AS_DOC_FEE_STUP — The base table holding document fee setup definitions. All insert, update, delete, and lock operations target this table.
• IGS_AS_DOC_FEE_STUP_S — The sequence supplying surrogate primary key values during ADD_ROW and INSERT_ROW.
• DUAL — Used for single-row queries and sequence value retrieval within PL/SQL expressions.

Additional dependencies include APP_EXCEPTION and FND_MESSAGE/IGS_GE_MSG_STACK for structured error raising and message token substitution, and IGS_FI_FEE_TYPE_PKG for fee type validation against the fee type definition.

Usage Notes

Because the package is referenced by no other database object, it is invoked exclusively from the Oracle Forms module that maintains document fee setup data, where the standard table-handler triggers (KEY-CREREC, KEY-DELREC, KEY-UPDATABLE, and similar) call the corresponding package procedures. The BEFORE_DML routine is driven from the block-level pre-insert and pre-update triggers, ensuring validation occurs once regardless of the DML path taken.

Custom code should not call this package directly; it is not a published API and offers no documented interface guarantees. Integrations or data loads that must create document fee setup records should either use the supported open interfaces for the Student Systems product or, where none is available, insert into IGS_AS_DOC_FEE_STUP with explicit sequence references, taking care to respect the same uniqueness rules enforced by GET_UK_FOR_VALIDATION. Any direct manipulation bypasses the validation performed in BEFORE_DML and may produce setup rows that the application forms subsequently reject.