Search Results requestor_givenname

Overview

The view APPS.IGS_DA_PURGE_V is a reporting and integration layer defined in the Oracle E-Business Suite database schema. It exposes the contents of the IGS_DA_PURGE base table, which stores records relating to the purge processing of data within the Oracle Student System (formerly known as the Student Information Management System) module family. The "IGS" prefix identifies these objects as belonging to Oracle's Higher Education / Student System product line, in which DA segment tables typically relate to admissions, applicant, or student data processing activities.

The primary role of this view is to provide a stable, published interface through which purge batch requests, their processing statuses, and the identity of the person who submitted them can be queried. Because it is a simple projection over a single base table, the view imposes no filtering, join, or aggregation logic; it reproduces the rows of IGS_DA_PURGE exactly as stored, while exposing an additional synthetic ROW_ID column derived from the Oracle ROWID pseudocolumn. The view is commonly used in concurrent program logic, reporting, and integration routines that require a consistent, named reference to purge request data without depending directly on the public synonym of the base table.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single base object: the table IGS_DA_PURGE. No additional referenced base objects are documented, and the view contains no joins, subqueries, or set operators. This confirms it is a straightforward 1:1 projection view.

• IGS_DA_PURGE — the sole documented base table, holding one row per purge request or purge batch record processed by the Student System data administration routines.
• ROWID — the pseudocolumn aliased as ROW_ID, providing a uniquely addressable physical row identifier for the underlying record.

Because the view is defined with no filtering predicates, DML against the view is theoretically possible where the base table permits it; however, in Oracle EBS practice such views are typically treated as read-only query interfaces and are maintained exclusively by the module's own processing logic.

Key Columns

The view exposes the complete set of columns from the base table. Notable columns are outlined below.

• BATCH_ID — the identifier of the purge batch to which the record belongs; used to group related purge requests and to reconcile batch-level processing.
• PURGE_STATUS — indicates the current state of the purge operation for the record.
• REQUEST_STATUS, REQUEST_TYPE, and REQUEST_MODE — describe the submission status, the category of the request, and the mode in which it was processed.
• REPORT_STATUS — reflects the status of any associated report output generated by the purge process.
• REQUESTOR_SURNAME and REQUESTOR_GIVENNAME — the surname and given name of the individual who submitted the purge request. These are the columns most relevant to a search on "requestor_surname".
• REQUESTOR_TYPE — classifies the requester, for example as an internal user or an external party.
• REQUEST_MADE_DATE — the date on which the request was originally raised.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE — the standard Oracle EBS audit columns recording who created and last modified the row, and when.

Common Use Cases and Queries

The view is typically queried to locate purge requests by requester name, to monitor outstanding or failed purge batches, and to feed downstream reconciliation reports. The following examples illustrate typical usage.

• Locate purge requests submitted by a specific person surname:

SELECT batch_id, requestor_surname, requestor_givenname,
       request_status, request_made_date
  FROM apps.igs_da_purge_v
 WHERE UPPER(requestor_surname) = UPPER('SMITH');

• Review all requests in a given batch along with their statuses:

SELECT batch_id, request_type, request_mode, purge_status, report_status
  FROM apps.igs_da_purge_v
 WHERE batch_id = :p_batch_id;

• Audit recently raised requests using the standard EBS audit columns:

SELECT requestor_surname, requestor_type, request_made_date,
       created_by, last_update_date
  FROM apps.igs_da_purge_v
 WHERE request_made_date >= TRUNC(SYSDATE) - 30
 ORDER BY request_made_date DESC;

Because the view is a direct projection, all predicates are resolved against the base table, and no additional access restrictions beyond standard EBS schema privileges apply.