Search Results igf_sl_dl_batch




Overview
Explore in AI Chat

Overview

IGF_SL_DL_BATCH is a reporting and integration view within the Oracle E-Business Suite IGF (Financial Aid) module, historically associated with the Student Loan (SL) and Direct Loan (DL) processing footprint. In Oracle EBS 12.1.1 and 12.2.2, the IGF product family is classified as obsolete, meaning the objects survive for upgrade and historical reference purposes but are not part of the current shipped functionality. The view presents batch header information for student loan disbursement and origination batch processes, exposing the message class, batch status, rejection codes, and standard EBS audit and multi-organization columns. Because it is a view rather than a table, it does not store data; it projects a filtered, MOAC-aware result set from its base table and is intended primarily for reporting, data extraction, and legacy integration that must respect the same organization security semantics as the underlying entity.

Underlying Base Objects

The view is defined over a single documented base object: IGF_SL_DL_BATCH_ALL. The ETRM metadata lists no additional referenced base objects, which indicates the view performs no joins. The defining query aliases the base table as DBTH and selects ROWID along with the full set of batch header columns. The critical distinction between the view and its base table is the ORG_ID predicate applied in the WHERE clause. Using USERENV('CLIENT_INFO'), the view derives the current organization context and matches it against DBTH.ORG_ID through a nested NVL construction that resolves to -99 when no organization context is available. This implements the standard EBS Multi-Org Access Control (MOAC) pattern. The _ALL suffix on the base table confirms that records are partitioned by operating unit or organization, and the view enforces that separation at query time. The metadata notes that the object is "Not implemented in this database," meaning it was not instantiated in the documented environment; on a live instance the view exists only where the IGF Financial Aid schema was installed or retained.

Key Columns

  • ROW_ID — the physical row identifier of the underlying batch header record in IGF_SL_DL_BATCH_ALL.
  • DBTH_ID — the primary key of the batch header record.
  • BATCH_ID — the business identifier assigned to the batch, used to group related loan transactions.
  • MESSAGE_CLASS — classifies the batch message type relevant to the student loan interface.
  • BTH_CREATION_DATE — the date the batch was created, distinct from the standard Creation_Date audit column.
  • BATCH_REJ_CODE — the rejection code returned when a batch fails processing.
  • END_DATE — the termination or completion date associated with the batch.
  • BATCH_TYPE — indicates the batch category or processing purpose.
  • SEND_RESP — flag controlling whether a response is transmitted for the batch.
  • STATUS — the current processing state of the batch.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for audit traceability.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request that created or last modified the record.
  • ORG_ID — the operating unit or organization that owns the batch, and the column driving the MOAC filter.

Common Use Cases and Queries

Typical scenarios include auditing batch processing outcomes, extracting rejected batches for remediation, and reconciling loan batch activity by operating unit. Because the view applies the MOAC predicate automatically, callers see only batches for the organization in their current session context, which is the intended behavior for reporting tools and interfaces.

Listing all batches with their status:

  • SELECT dbth_id, batch_id, batch_type, status FROM igf_sl_dl_batch;

Identifying rejected or failed batches:

  • SELECT batch_id, batch_rej_code, status FROM igf_sl_dl_batch WHERE batch_rej_code IS NOT NULL;

Reviewing batch volume by creation date:

  • SELECT TRUNC(bth_creation_date) batch_day, COUNT(*) FROM igf_sl_dl_batch GROUP BY TRUNC(bth_creation_date);

Correlating batches to their originating concurrent request:

  • SELECT batch_id, request_id, program_id FROM igf_sl_dl_batch WHERE request_id IS NOT NULL;

Because IGF is obsolete in 12.1.1 and 12.2.2, these queries apply only to environments where the Financial Aid schema remains, and users should confirm the view is implemented before relying on it.