Search Results message_class




Overview
Explore in AI Chat

Overview

APPS.IGF_SL_DL_BATCH is a multi-org view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment that exposes student loan disbursement batch activity managed by the Financial Aid / Student Loan module (product family IGF). The view filters records to the operating unit of the current session, automatically ignoring rows belonging to other operating units. It is owned by the APPS schema and is registered in FND Design Data under the application identifier IGF, confirming that it is a shipped, supported database object rather than a custom artifact. Its status is documented as VALID.

The view functions primarily as a reporting and integration surface. Inbound and outbound loan disbursement processes — acknowledgement, origination, reconciliation, and charge transactions — reference this object through dependent database code. Because consumer integrations and internal concurrent programs need a consistent, single-operating-unit projection of batch data, the view abstracts the multi-org partitioning that is otherwise handled inside the underlying table.

Underlying Base Objects

The documented base object for IGF_SL_DL_BATCH is APPS.IGF_SL_DL_BATCH_ALL. The "_ALL" suffix identifies the base table as the multi-org repository that stores batch rows for every operating unit; ORG_ID on that table keys each row to a specific operating unit. The view selects from the _ALL table and applies the standard multi-org filtering predicate against the session's current operating unit, which is why its metadata describes it as a multi-org view that retrieves data for the current operating unit and ignores data in other operating units.

The ETRM listing does not itemize additional referenced objects beyond IGF_SL_DL_BATCH_ALL, so the dependency set should be treated as limited to that table for documentation purposes. In the reverse direction, the view is referenced by a substantial set of IGF program units, including IGF_DB_DL_DISB_ORIG, IGF_DB_DL_ORIG_ACK, IGF_DB_DL_RECONC, IGF_SL_DL_CHG_ACK, IGF_SL_DL_CHG_ORIG, IGF_SL_DL_ORIG, IGF_SL_DL_ORIG_ACK, IGF_SL_DL_PNOTE_ACK, IGF_SL_DL_RECORD (referenced twice), and IGF_SL_REJ_WF. This dependency graph indicates that batch metadata is consumed by both disbursement processing and rejection workflow logic.

Key Columns

  • ROW_ID (ROWID) — physical row identifier for the batch record.
  • DBTH_ID (NUMBER, 15) — primary identifier for the disburse batch record.
  • BATCH_ID (VARCHAR2, 40) — externally recognizable batch identifier used by downstream systems.
  • MESSAGE_CLASS (VARCHAR2, 30) — classification of the message exchanged for the batch, used to route or categorize disbursement responses.
  • BTH_CREATION_DATE (DATE) — date the batch was created.
  • BATCH_REJ_CODE (VARCHAR2, 30) — rejection code recorded when a batch is not accepted.
  • END_DATE (DATE) — effective end date associated with the batch record.
  • BATCH_TYPE (VARCHAR2, 30) — category of batch (for example, disbursement versus change or acknowledgement activity).
  • SEND_RESP (VARCHAR2, 30) — indicates whether a response is expected or was sent.
  • STATUS (VARCHAR2, 30) — current processing state of the batch.
  • ORG_ID (NUMBER, 15) — operating unit that owns the batch row.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus concurrent manager columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes batch reconciliation reports, rejection analysis, and locating the message class assigned to a batch. The view may be queried directly in a multi-org session without additional ORG_ID predicates.

SELECT BATCH_ID,
       MESSAGE_CLASS,
       BATCH_TYPE,
       BATCH_REJ_CODE,
       STATUS,
       BTH_CREATION_DATE
FROM   APPS.IGF_SL_DL_BATCH
WHERE  STATUS = 'ERROR'
ORDER  BY BTH_CREATION_DATE DESC;

To group batches by message class for monitoring disbursement messaging volume, a standard aggregate over MESSAGE_CLASS and BATCH_TYPE is appropriate. For investigation of rejections, joining on BATCH_REJ_CODE and filtering by BTH_CREATION_DATE narrows results to a given processing window. Because the view is multi-org filtered, each session sees only the operating unit's data, making it suitable for operating-unit-specific extracts without exposing rows from other organizations.