Results for “requested_by_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_AS_DUP_DOCS_V view is a reporting and inquiry object within the Oracle E-Business Suite Student System (IGS) product family. Its functional purpose, as documented in the ETRM metadata for release 12.2.2, is to store and expose all duplicate requests raised for a document. A "duplicate document" in the Student System context typically refers to a request from a person (such as a student or alumnus) for a re-issued copy of an official document — for example a transcript, certificate, or award letter — where the original has already been issued. Rather than acting as a transaction-entry form, this view presents a denormalized, join-enriched projection of the underlying duplicate-document request records, which makes it suitable for operational reporting, enquiry screens, and integration extracts.

The view resides in the APPS schema and carries a VALID status in the supplied metadata, confirming that it compiles successfully against its dependencies in the tested 12.1.1 and 12.2.2 environments. Note that while the object name follows the IGS naming convention, the documented base objects are drawn from the IGS_AS (Academic Support / Student System administration) and IGS_PE (People) table families, indicating that the view bridges document-request data with person identity data.

Underlying Base Objects

The view text documented in the ETRM metadata reveals its definition. It selects from the base table IGS_AS_DUP_DOCS (aliased AD), which holds the core duplicate-document request records, and joins twice to IGS_PE_PERSON_BASE_V (the person base view in the People product) to resolve both the requesting person and the fulfilling party to a display name.

• IGS_AS_DUP_DOCS — the primary driving table containing the duplicate document request rows.
• IGS_PE_PERSON_BASE_V (HZ1) — joined on AD.REQUESTED_BY = HZ1.PERSON_ID to obtain the requester's name.
• IGS_PE_PERSON_BASE_V (HZ2) — outer-joined on AD.FULFILLED_BY = HZ2.PERSON_ID (+) to obtain the fulfiller's name where fulfilment has occurred.

The outer join on the fulfilled party is functionally significant: a request that has not yet been fulfilled will still appear in the view, with a null fulfiller name. This preserves the full lifecycle of duplicate requests in a single result set.

Key Columns

• ROW_ID — the ROWID of the base IGS_AS_DUP_DOCS row, exposed for row identification.
• ORDER_NUMBER / ITEM_NUMBER — the order and line/item identifiers associated with the duplicate document request.
• REQUESTED_BY / REQUESTED_BY_NAME — the party ID and resolved display name of the person who requested the duplicate.
• REQUESTED_DATE — the date the duplicate request was logged.
• FULFILLED_BY / FULFILLED_BY_NAME — the party ID and resolved name of the person who fulfilled the request; both are null until fulfilment.
• FULFILLED_DATE — the date on which the duplicate document was fulfilled. This is the column returned by the search term "fulfilled_date" and is central to aged/open-request reporting.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns.

Common Use Cases and Queries

Typical scenarios include monitoring outstanding duplicate requests (those with a null FULFILLED_DATE), measuring fulfilment turnaround, and feeding document-issuance extracts.

• List open duplicate requests: SELECT order_number, item_number, requested_by_name, requested_date FROM igs_as_dup_docs_v WHERE fulfilled_date IS NULL;
• Calculate turnaround: SELECT order_number, requested_date, fulfilled_date, (fulfilled_date - requested_date) days_to_fulfil FROM igs_as_dup_docs_v WHERE fulfilled_date IS NOT NULL;
• Filter by requester: SELECT * FROM igs_as_dup_docs_v WHERE requested_by_name = :name;

Because the view already resolves person names, it removes the need for ad-hoc joins to the People tables, though it should be treated as read-only for reporting purposes.