Search Results igs_as_doc_dlvy_typ_pkg

Overview

IGS_AS_DOC_DLVY_TYP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Student Systems (IGS) product family and supports the Academic Support / Admissions functional area, where the suffix "AS" denotes the academic support subsystem and "DOC_DLVY_TYP" denotes document delivery type. The package encapsulates the business logic and data access routines associated with the IGS_AS_DOC_DLVY_TYP entity, which defines the categories by which documents such as transcripts, enrollment verification letters, and admission decision notifications are delivered to students, applicants, or third parties.

Institutionally, document delivery types classify delivery channels and fulfillment modes — for example, printed mail, courier, secure electronic download, or in-person pickup. Because these classifications drive downstream fee calculation and fulfillment processing, the package is also referenced by IGS_AS_DOC_DLVY_FEE_PKG, which manages the fee structures attached to each delivery type. The package is classified as an OTHER API in the ETRM metadata, indicating that it is an internal maintenance package rather than a fully published, externally supported integration API. Its object status is VALID in the documented 12.1.1 environment.

Key Procedures and Functions

The package exposes seven documented procedures, which together form a complete single-row maintenance API against the underlying entity.

• INSERT_ROW — Performs the initial insertion of a new document delivery type record, populating the base row and its associated attributes.
• ADD_ROW — The traditional Oracle Forms "add row" handler, invoked when a user creates a new record in a block maintaining document delivery type data.
• UPDATE_ROW — Applies modifications to an existing document delivery type record, typically invoked when a user commits changes in the maintenance form.
• DELETE_ROW — Removes a document delivery type record, subject to the referential constraints enforced against dependent fee and delivery records.
• LOCK_ROW — Obtains a row-level lock on the target record to serialize concurrent updates and prevent lost-update conditions in multi-user maintenance.
• GET_PK_FOR_VALIDATION — Returns the primary key needed by the validation infrastructure, allowing the framework to validate the record identity during processing.
• BEFORE_DML — An internal pre-DML hook that populates WHO columns (creation and update audit attributes) and applies standard validation prior to insert, update, or delete operations.

The metadata does not document explicit parameter lists for these procedures; consumers should inspect the package specification in the target environment before invoking them directly.

Tables Accessed

The package operates against a single base table, accessed through an APPS synonym:

• IGS_AS_DOC_DLVY_TYP — The master table of document delivery types. The package reads this table for validation and primary key resolution, and writes to it through INSERT_ROW, ADD_ROW, UPDATE_ROW, and DELETE_ROW. LOCK_ROW also issues a locking read against this table.

No additional base tables are documented in the ETRM metadata. Dependency analysis shows the package references SYS.STANDARD, reflecting standard PL/SQL constructs rather than any external application dependency.

Usage Notes

IGS_AS_DOC_DLVY_TYP_PKG is designed for the Oracle Forms-based maintenance of document delivery type setup data. The presence of ADD_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW alongside BEFORE_DML is characteristic of a Forms block-level API, where the form's trigger logic delegates DML to these packaged procedures rather than issuing DML directly. Administrators and implementers typically reach this package indirectly by navigating to the document delivery type setup form in the Student Systems responsibility.

The package is referenced by IGS_AS_DOC_DLVY_FEE_PKG, confirming that fee setup for document delivery depends on the delivery type definitions maintained here. It does not appear to be referenced by concurrent programs in the documented metadata. Customizations should avoid direct INSERT or UPDATE statements against IGS_AS_DOC_DLVY_TYP and instead call the packaged procedures, so that the BEFORE_DML audit population and validation logic remain consistent. Because the object is classified as OTHER rather than PUBLIC, Oracle does not guarantee API stability, and behavior should be re-verified when upgrading between 12.1.1 and 12.2.2.