Search Results igs_as_dup_docs




Overview
Explore in AI Chat

Overview

The IGS_AS_DUP_DOCS table is a core data object within the Oracle E-Business Suite Student System (IGS) module, specifically for versions 12.1.1 and 12.2.2. It functions as the system of record for tracking all requests for duplicate academic documents. In the context of student administration, this table is critical for managing the lifecycle of document re-issuance, whether for replacement of lost credentials, provision of additional copies to third parties, or fulfillment of other official requests. Its role is to maintain an auditable history of each duplicate request tied to an original document, capturing key transactional details such as the requester, the date of the request, and its linkage to the primary document record.

Key Information Stored

The table's structure is designed to uniquely identify each duplicate request and associate it with relevant entities. The primary key is a composite of ITEM_NUMBER and REQUESTED_DATE, ensuring multiple requests for the same document on different dates are uniquely recorded. Key columns include ITEM_NUMBER, which is a foreign key linking to the original document in the IGS_AS_DOC_DETAILS table. The REQUESTED_DATE is the timestamp of the request. The REQUESTED_BY column holds a foreign key identifier linking to the HZ_PARTIES table, which stores information about the individual or entity (e.g., student, alumnus, or organization) who submitted the request. Additional columns, implied by the table's purpose, would typically store data on the request status, fulfillment details, and any associated fees or notes.

Common Use Cases and Queries

This table supports several operational and reporting functions. A common operational use case is generating a worklist of pending duplicate document requests for administrative staff to process. For reporting, it enables analysis of duplicate request volumes over time or by requester type. Administrators may query it to verify the history of duplicates issued for a specific original document. Sample SQL patterns include retrieving all duplicate requests for a specific document item or within a date range:

  • SELECT * FROM igs.igs_as_dup_docs WHERE item_number = :p_item_num ORDER BY requested_date DESC;
  • SELECT d.item_number, d.requested_date, p.party_name FROM igs.igs_as_dup_docs d, hz_parties p WHERE d.requested_by = p.party_id AND d.requested_date BETWEEN :p_start_date AND :p_end_date;

Related Objects

The IGS_AS_DUP_DOCS table has defined foreign key relationships with two other EBS tables, establishing its place in the data model. The primary relationship is with the IGS_AS_DOC_DETAILS table via the ITEM_NUMBER column. This join retrieves the details of the original academic document for which the duplicate was requested. The second relationship is with the HZ_PARTIES table (a foundational Trading Community Architecture table) via the REQUESTED_BY column. This join provides the identity and contact information for the requester. The documented relationships are:

  • Foreign Key: IGS_AS_DUP_DOCS.ITEM_NUMBER references IGS_AS_DOC_DETAILS
  • Foreign Key: IGS_AS_DUP_DOCS.REQUESTED_BY references HZ_PARTIES