Search Results igs_as_doc_details_pkg




Overview
Explore in AI Chat

Overview

IGS_AS_DOC_DETAILS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the OTHER API category. It belongs to the Student Systems product family (the IGS prefix denotes Oracle Student System / Academic Systems modules) and specifically supports the "AS" sub-product area, which relates to admissions and document tracking. The package encapsulates the core data manipulation logic for the IGS_AS_DOC_DETAILS entity, which stores the individual document requirement and receipt details associated with an applicant's admission record. Each row in the underlying table typically represents a single document line — such as a transcript, recommendation letter, or identification proof — required or received for a given admission order. The package is the primary maintenance layer between the entity's base tables and the higher-level APIs that consume document detail data. In the ETRM documentation, the object carries a status of VALID and exposes ten documented procedures and functions, confirming it is an actively deployed and supported component in both EBS 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The package provides a standard table-handler interface, including a BEFORE_DML trigger-style procedure that enforces row-level derivations and validation rules whenever a record is inserted or modified. Its principal DML entry points are INSERT_ROW, UPDATE_ROW, and DELETE_ROW, each of which performs the corresponding operation against the base table, while ADD_ROW supplies the alternate insert path used by several calling APIs. A LOCK_ROW procedure provides pessimistic concurrency control, allowing callers to obtain a row-level lock before making dependent changes. Referential integrity support is delivered through the GET_FK_* functions: GET_PK_FOR_VALIDATION derives the primary key used in validation logic, GET_FK_IGS_AS_DOC_DLVY_TYP resolves the foreign key to the document delivery type, GET_FK_IGS_CA_INST resolves the institution reference, and GET_FK_IGS_AS_ORDER_HDR resolves the link to the parent admission order header. Together these routines enforce consistency across the document detail entity and its parent admission structures.

Tables Accessed

Documented table access is performed through APPS synonyms. The package reads and writes IGS_AS_DOC_DETAILS as its primary table, with IGS_AS_DOC_DETAILS_S serving as the sequence source for surrogate keys. Validation lookups reference IGS_AS_DOC_DLVY_TYP (document delivery type), IGS_AS_DOCPROC_STUP (document processing setup), IGS_AS_ORDER_HDR (admission order header), and IGS_AS_DUP_DOCS (duplicate document identification). HZ_PARTIES is consulted to resolve the party (person or organization) associated with a document, and DUAL supports scalar queries. These reads and writes ensure that every document detail row carries a valid delivery type, institution context, order reference, and party identification.

Usage Notes

The package is not typically invoked directly by end users. Instead it is called by higher-level components, notably IGS_AS_DOCUMENTS_API, which orchestrates document maintenance, and it is also referenced by IGS_AS_DOC_DLVY_TYP_PKG, IGS_AS_ORDER_HDR_PKG, IGS_AS_PROD_DOC, and IGS_AS_SS_DOC_REQUEST. In practice, invocation occurs through Student System forms and self-service document request pages that manipulate admission document details, and through concurrent or custom PL/SQL that inserts, updates, or deletes document detail lines. Any extension or wrapper code should call the package's public procedures rather than modifying IGS_AS_DOC_DETAILS directly, so that BEFORE_DML validation and foreign key resolution remain enforced. Customizations must preserve the documented dependency chain, as several standard APIs depend on this package's behavior.