Search Results igs_da_req_batch




Overview
Explore in AI Chat

Overview

The IGS_DA_REQ_BATCH table is a data storage object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically designed to support degree audit functionality. As indicated by its description, it serves as storage for degree audits based on criteria for students within a request. This table is part of the infrastructure for processing and managing batch degree audit requests, which are systematic evaluations of a student's academic progress against program requirements. It is critical to note that the IGS module is marked as "Obsolete" in the provided ETRM metadata, indicating that this table and its associated functionality are part of a legacy system component that is no longer under active development or enhancement by Oracle. Furthermore, the documentation explicitly states it is "Not implemented in this database," which may refer to a specific reference instance, suggesting its presence and structure can vary across implementations.

Key Information Stored

The primary data element stored in this table is the batch identifier, which acts as the unique key for grouping a set of related degree audit requests. Based on standard patterns for such audit tables and the provided key information, the table's structure likely includes the following core columns:

  • BATCH_ID: The primary key column. This unique identifier links all individual student degree audit requests that are part of the same batch submission or job run.
  • REQUEST_ID (inferred): While not explicitly listed in the brief metadata, a foreign key relationship to a parent request table (IGS_DA_RQST) is documented. This would store the identifier of the overarching audit request that spawned this batch.
  • Status and control columns such as BATCH_STATUS, CREATION_DATE, and CREATED_BY, which are typical in EBS for tracking the lifecycle and origin of batch processes.
  • Parameters or criteria columns that define the scope of the batch audit, potentially storing the selection criteria used to identify the student cohort for evaluation.

Common Use Cases and Queries

The primary use case for this table is the management and tracking of batch-submitted degree audits. Administrators would use it to monitor the progress of bulk audit jobs, review historical batch runs, and troubleshoot any failures. Common reporting needs include listing all batches submitted within a date range or identifying batches with a specific status (e.g., 'PENDING', 'PROCESSING', 'COMPLETE'). A typical query would join IGS_DA_REQ_BATCH to the IGS_DA_RQST table to retrieve comprehensive request details.

Sample Query Pattern:
SELECT batch.batch_id,
batch.creation_date,
batch.batch_status,
request.program_code
FROM igs_da_req_batch batch,
igs_da_rqst request
WHERE batch.batch_id = request.batch_id
AND batch.creation_date > SYSDATE - 30
ORDER BY batch.creation_date DESC;

Related Objects

The table maintains a direct foreign key relationship with a core degree audit request table, as documented in the ETRM metadata. This relationship is fundamental to its data integrity and purpose.

  • IGS_DA_RQST: This is the primary related table. The foreign key relationship is defined on the BATCH_ID column. The IGS_DA_REQ_BATCH table acts as a parent, with IGS_DA_RQST storing the individual student audit instances that belong to a given batch. This structure allows a single batch request to generate multiple individual student audit records.

Given the obsolete status of the IGS module, integration with newer EBS components or alternative student information systems would typically involve custom interfaces or data migration, rather than standard Oracle-delivered APIs.