Search Results igs_as_doc_dlvy_typ




Overview
Explore in AI Chat

Overview

The table IGS_AS_DOC_DLVY_TYP is a core reference table within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically for versions 12.1.1 and 12.2.2. It functions as a master repository for defining the various methods by which official documents can be delivered to requestors. Its primary role is to maintain a standardized list of delivery options, such as standard mail, courier service, electronic download, or in-person pickup, which can then be associated with specific document requests and their corresponding fees. This centralized control ensures data integrity and consistency across the document fulfillment process, enabling accurate tracking, reporting, and fee assessment based on the chosen delivery method.

Key Information Stored

The table's structure is designed to be a straightforward lookup. Its primary key is the column DELIVERY_METHOD_TYPE, which stores the unique code identifying each delivery method (e.g., 'COURIER', 'EMAIL', 'STANDARD_POST'). While the provided ETRM metadata does not list additional columns, typical implementations of such a reference table in Oracle EBS would also include descriptive and control columns. These commonly comprise a meaningful name (e.g., DELIVERY_METHOD_DESC), an effective date range (START_DATE, END_DATE) to enable or disable methods, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for auditing. The core business data is the discrete list of valid delivery types, which is referenced by transactional tables throughout the document request lifecycle.

Common Use Cases and Queries

This table is central to operations involving student document requests. A primary use case is populating a list of values (LOV) in the application's user interface when a student or administrator selects how a transcript or certificate should be delivered. It is also critical for batch processes that calculate delivery fees or generate shipping labels. Common reporting queries involve joining this table to transactional data to analyze delivery method popularity or associated revenue. Sample SQL to retrieve all active delivery methods might resemble: SELECT delivery_method_type FROM igs.igs_as_doc_dlvy_typ WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);. For operational reporting, a typical join to document details would be: SELECT d.request_number, d.delivery_method_type, t.description FROM igs.igs_as_doc_details d, igs.igs_as_doc_dlvy_typ t WHERE d.delivery_method_type = t.delivery_method_type;.

Related Objects

The IGS_AS_DOC_DLVY_TYP table has defined foreign key relationships with two key transactional tables, as documented in the ETRM metadata. These relationships enforce referential integrity, ensuring that only valid delivery types from this master table can be used in downstream processes.

  • IGS_AS_DOC_DLVY_FEE: This table stores the fee amounts associated with each delivery method. It references IGS_AS_DOC_DLVY_TYP via the column IGS_AS_DOC_DLVY_FEE.DELIVERY_METHOD_TYPE. This join is essential for determining the cost of a selected delivery option during a document request.
  • IGS_AS_DOC_DETAILS: This is a primary transactional table holding the specifics of individual document requests. It references IGS_AS_DOC_DLVY_TYP via the column IGS_AS_DOC_DETAILS.DELIVERY_METHOD_TYPE. This relationship records the chosen delivery method for each request, linking it to the master definition and, indirectly, to the applicable fee.
The primary key constraint IGS_AS_DOC_DLVY_TYP_PK on the DELIVERY_METHOD_TYPE column supports these relationships.