Results for “batch_rej_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGF_SL_DL_BATCH_ALL table resides in the IGF (Financial Aid) product family, which is documented as obsolete within Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to maintain Direct Loan batch information sent to or received from external loan servicing systems. It functions as the master batch header record within the Direct Loan integration flow, capturing the identity, lifecycle, and processing state of each transmission batch exchanged between Oracle EBS and the federal Direct Loan servicing infrastructure.

From a heuristic Data Vault modeling perspective, this table is classified as hub-leaning. That classification reflects its role as a keyed anchor entity: it holds the unique batch identifier (DBTH_ID), carries descriptive attributes, and is the parent of at least six child tables that reference it through the same DBTH_ID column. Each dependent record set — disbursement responses, promissory note responses, loan origination responses, credit responses, change responses, and change sends — attaches its own transactional detail to a single batch header, which is the characteristic satellite-and-link pattern surrounding a hub. The ETRM documentation notes that the object is not implemented in the current database, meaning its presence depends on whether the Financial Aid Direct Loan integration has been provisioned in a given environment.

Key Information Stored

The table is defined with nineteen columns, of which the most significant are the following.

• DBTH_ID — the surrogate primary key, enforced by IGF_SL_DL_BATCH_ALL_PK. It is also the sole documented business-key candidate, backed by unique index IGF_SL_DL_BATCH_ALL_U1. Every child table joins on this column.
• BATCH_ID — the externally meaningful batch identifier used in transmission and reconciliation against the loan servicer's records.
• BATCH_TYPE and SEND_RESP — classify the batch by purpose and by direction, distinguishing outbound submissions from inbound responses.
• MESSAGE_CLASS — groups the batch by the type of Direct Loan message carried, such as origination or disbursement activity.
• BTH_CREATION_DATE, CREATION_DATE, and LAST_UPDATE_DATE — support aging, reconciliation, and audit reporting across the batch lifecycle.
• STATUS and BATCH_REJ_CODE — record processing outcome and, where applicable, the rejection reason returned by the servicing system.
• END_DATE — marks the effective conclusion of the batch record.
• ORG_ID and REQUEST_ID — provide multi-organization and concurrent-request context, enabling attribution of each batch to a specific operating unit and batch process run.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — supply the standard EBS who-columns and concurrent program audit trail.

Common Use Cases and Queries

Typical usage centers on operational monitoring of Direct Loan transmissions and on reconciliation of batch outcomes. A representative inquiry lists recent batches by status and type:

• SELECT DBTH_ID, BATCH_ID, BATCH_TYPE, SEND_RESP, STATUS, BATCH_REJ_CODE, BTH_CREATION_DATE FROM IGF_SL_DL_BATCH_ALL WHERE TRUNC(BTH_CREATION_DATE) >= TRUNC(SYSDATE)-30 ORDER BY BTH_CREATION_DATE DESC;
• Rejection analysis: aggregate BATCH_REJ_CODE counts grouped by BATCH_TYPE and ORG_ID to isolate recurring servicer rejections.
• Directional tracking: filter on SEND_RESP to separate outbound change-send batches from inbound response batches.
• Drill-down reporting: join DBTH_ID to each dependent response table to reconstruct the full contents and results of a single batch.

Related Objects

Six dependent tables reference this table through DBTH_ID, forming the batch detail layer:

• IGF_DB_DL_DISB_RESP_ALL.DBTH_ID — disbursement responses.
• IGF_SL_DL_PNOTE_RESP_ALL.DBTH_ID — promissory note responses.
• IGF_SL_DL_LOR_RESP_ALL.DBTH_ID — loan origination responses.
• IGF_SL_DL_LOR_CRRESP_ALL.DBTH_ID — loan origination credit responses.
• IGF_SL_DL_CHG_RESP_ALL.DBTH_ID — change responses received.
• IGF_SL_DL_CHG_SEND_ALL.DBTH_ID — change requests sent.

Because the product is marked obsolete, remediation or migration work should verify whether these dependent objects remain populated before altering or retiring the batch header structure.