Search Results igs_ad_tstuh_call_pkg

Overview

IGS_AD_TSTUH_CALL_PKG is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the E-Business Suite Technical Reference Manual (ETRM) as an "OTHER" API. Its name follows the IGS (Student System / Oracle Student Information System) naming convention, and the embedded header comment ($Header: IGSADA6S.pls 115.4 2002/11/28 21:48:11 nsidana ship $) identifies it as a shipped Student System database object, with the last recorded edit dating to November 2002.

The package exists to provide a user-hook extension point around the IGS_AD_TSTUH_S table, which relates to test unit/test booking header data in the Student System. Rather than embedding institution-specific logic directly in delivered code, Oracle exposes a call-point so that implementers can attach custom processing via a hook. Consistent with this design, the package is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer — a deliberate choice that allows a customer-defined hook to operate under its own security context.

Key Procedures and Functions

The ETRM documents a single procedure:

• CALL_USER_HOOK — The sole public entry point. Its documented signature accepts an input person identifier and returns a session identifier as an OUT NOCOPY parameter. The procedure is the mechanism by which the Student System invokes customer-supplied logic at the appropriate point in the test-unit processing flow; the caller supplies the person context, and the procedure communicates back a session reference for subsequent use. No additional parameters are documented, and no implementation body is exposed in the package specification, confirming its role as a thin invocation wrapper rather than a business-logic container.

Tables Accessed

The ETRM records two referenced objects, resolved through APPS synonyms:

• IGS_AD_TSTUH_S — The primary Student System table associated with this package, pertaining to test unit header records. The package reads and/or writes this table as part of the hook invocation cycle, providing the persistence context for the session identifier returned by CALL_USER_HOOK.
• USER_OBJECTS — The Oracle data dictionary view. Its presence indicates the package performs existence or validity checks against database objects at runtime, a common defensive pattern used to determine whether a customer hook object has been deployed before attempting to invoke it.

Usage Notes

CALL_USER_HOOK is not intended for direct invocation by end users or by arbitrary client code. It is a hook call-point: the delivered Student System logic calls it, and the customer is expected to override or extend the behavior through the supported customization mechanism. This is reinforced by the OUT NOCOPY session identifier, which the calling context consumes after the procedure returns, and by the fact that the package is referenced by one other package in the ETRM dependency data.

Typical invocation therefore occurs from within delivered Student System PL/SQL — for example, from a form-based test unit or test booking flow, or from a concurrent program that processes test unit header records — during runtime processing of person-specific test data. Because the package is AUTHID CURRENT_USER, any custom hook object it locates must be accessible and executable by the invoking user; grants on the customer object must be verified before deployment. Implementers using this package should treat the specification as frozen and never modify the delivered body, instead deploying their logic in the hook location the procedure resolves. Testing should confirm that USER_OBJECTS lookups succeed and that the returned session identifier is correctly persisted against IGS_AD_TSTUH_S in both single-user and concurrent processing scenarios.