Search Results check_waivers




Overview

The APPS.IGS_AS_SS_DOC_REQUEST package belongs to the Oracle Student System (IGS) product family and supports the Academic Support (AS) module's self-service document request functionality. It provides the server-side PL/SQL logic used by students and staff to order academic documents such as transcripts, enrollment certificates, and other official records. The package governs fee determination, waiver evaluation, invoice generation, and the calculation of document and delivery charges associated with a document order.

As an API (ETRM classification: OTHER), the package exposes a set of public procedures and functions that encapsulate the business rules for document ordering, allowing forms, self-service pages, and concurrent programs to invoke that logic consistently. It is referenced by five other packages in the application, indicating a central role in the document request workflow.

Key Procedures and Functions

The documented interface includes 30 procedures and functions. The following are representative of the package's responsibilities, including the GET_TRANSCRIPT_FEE member that is the subject of the originating search:

Tables Accessed

The package reads and writes the core Academic Support tables through APPS synonyms. Order header and line data reside in IGS_AS_ORDER_HDR, IGS_AS_DOC_DETAILS, and IGS_AS_DOC_DETAILS_S. Fee and delivery rules are drawn from IGS_AS_DOC_FEE_STUP, IGS_AS_DOC_FEE_PMNT, IGS_AS_DOC_DLVY_FEE, and IGS_AS_DOC_DLVY_TYP. Document processing configuration comes from IGS_AS_DOCPROC_STUP, with item integration data in IGS_AS_ORD_ITM_INT and financial application data in IGS_FI_APPLICATIONS. Party and contact information is resolved via HZ_PARTIES and HZ_CONTACT_POINTS. Currency and lookup values are obtained from FND_CURRENCIES_TL and FND_LOOKUP_VALUES, and user messages from FND_NEW_MESSAGES.

Usage Notes

The package is typically invoked from the Student System self-service document request pages, administrative forms that manage document orders, and any concurrent or custom code that must reproduce order pricing or eligibility logic. Because GET_TRANSCRIPT_FEE carries PRAGMA RESTRICT_REFERENCES (WNDS, WNPS), it can be called safely from SQL and read-only contexts; callers should supply the person identifier, document type, and copy count, and may rely on the default delivery-fee handling when a delivery charge should be included. When pricing an existing order, UPDATE_ORDER_FEE should be used instead, so that changed line attributes are re-evaluated against the fee setup tables.