Search Results igs_da_purge




Overview

The IGS_DA_PURGE table belongs to the IGS (Student System) product family within Oracle E-Business Suite. In release 12.1.1 and 12.2.2 it is documented as obsolete and is not implemented in the standard database, meaning it is a legacy or end-of-life object that persists only in certain historical environments. Its stated purpose is the storage of Degree Audit Requests that have been purged from the active system, effectively acting as an archive or retention table for records that have been removed from the operative degree audit processing tables.

From a dimensional modeling perspective, the mined Data Vault classification for this object is standalone, suggesting it functions as an independent hub with no dependent link or satellite relationships. The absence of foreign-key-derived relationships reinforces that this table was maintained as a self-contained staging or archive construct rather than a transactional entity participating in the broader IGS relational web.

Key Information Stored

The table is documented with 16 columns in the ETRM 12.1.1 physical schema. The most significant attributes are:

The surrogate primary key is IGS_DA_PURGE_PK, defined over PUR_REQ_ID and BATCH_ID. A unique index, IGS_DA_PURGE_U1, covers the same two columns and represents the business-key candidate, reinforcing that the combination uniquely identifies a purged audit request.

Common Use Cases and Queries

Because the table is obsolete, primary usage centers on historical audit, compliance reporting, and data-retention verification. Typical queries retrieve purged requests for a given batch or requestor:

  • Identify all purged requests tied to a batch: SELECT * FROM IGS_DA_PURGE WHERE BATCH_ID = :batch_id;
  • Trace the purge history for a specific requestor: SELECT PUR_REQ_ID, REQUEST_MADE_DATE, PURGE_STATUS FROM IGS_DA_PURGE WHERE REQUESTOR_SURNAME = :surname;
  • Reconcile purge volumes by status: SELECT PURGE_STATUS, COUNT(*) FROM IGS_DA_PURGE GROUP BY PURGE_STATUS;
  • Audit records created within a date range: SELECT * FROM IGS_DA_PURGE WHERE CREATION_DATE BETWEEN :start_date AND :end_date;

Reporting use cases include compliance evidence for data purging, trend analysis of purge activity, and verification that retention policies were applied.

Related Objects

The mined relationship data classifies IGS_DA_PURGE as standalone, with no documented foreign-key dependencies. Consequently, related objects are inferred from functional context rather than enforced constraints. The most significant are the active degree audit request tables (analogous IGS_DA_* request tables) that feed this archive, joined on PUR_REQ_ID and BATCH_ID; the IGS batch processing tables referenced through BATCH_ID; and the requestor/student master tables referenced through REQUESTOR_TYPE and requestor name fields. Because the object is not implemented in the standard database, no shipped views or public APIs depend on it, and any dependency would be environment-specific and developer-maintained.