Results for “dbth_id”

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

Overview

IGF_SL_DL_CHG_RESP_ALL is a Financial Aid module table within Oracle E-Business Suite, belonging to the IGF (Financial Aid) product family. As reflected in the ETRM metadata, this product area is classified as obsolete, meaning the object is documented for historical and migration reference rather than for active functional use. The table stores the error codes generated when changed values for Direct Loan records are processed. Each row captures the outcome of a change response associated with a Federal Direct Loan, allowing the application to track which modifications were accepted, which were rejected, and why.

Based on the foreign key structure and the presence of a single surrogate-style primary key, the heuristic Data Vault classification for this object is satellite-leaning. This suggests the table behaves as a dependent descriptor attached to a parent batch entity (IGF_SL_DL_BATCH_ALL) rather than functioning as an independent hub or link. In practice, treat it as a detail table whose lifecycle is bound to the batch record it references.

Key Information Stored

The primary key is defined by the constraint IGF_SL_DL_CHG_RESP_ALL_PK over the single column RESP_NUM, a system-generated surrogate identifier. The principal business-key and foreign-key candidate is DBTH_ID, which joins to the parent batch table IGF_SL_DL_BATCH_ALL. Key columns include:

• RESP_NUM — surrogate primary key uniquely identifying each change response row.
• DBTH_ID — foreign key linking the response to its parent Direct Loan batch.
• BATCH_ID — business batch identifier associated with the processing run.
• LOAN_NUMBER and LOAN_IDENT_ERR_CODE — the loan identifier and any identifier-level error code returned.
• CHG_CODE — the code describing the type of change applied to the loan.
• REJECT_CODE — the error or rejection code returned for the changed value.
• NEW_VALUE — the changed value submitted for the loan.
• STATUS — processing disposition of the response record.
• ORG_ID — multi-org operating unit context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and request lineage columns.

Common Use Cases and Queries

This table is typically queried to audit Direct Loan change processing, diagnose rejected modifications, and reconcile responses against originating batches. A representative query joining to the parent batch is:

• SELECT r.RESP_NUM, r.LOAN_NUMBER, r.CHG_CODE, r.REJECT_CODE, r.NEW_VALUE, r.STATUS FROM IGF_SL_DL_CHG_RESP_ALL r WHERE r.DBTH_ID = :batch_id;
• Filtering by REJECT_CODE or LOAN_IDENT_ERR_CODE to isolate failed changes for remediation reporting.
• Joining DBTH_ID to IGF_SL_DL_BATCH_ALL to correlate responses with batch-level processing metadata.

Reporting scenarios include error-code frequency analysis, batch success-rate dashboards, and historical audit extracts for compliance review.

Related Objects

• IGF_SL_DL_BATCH_ALL — parent batch table; join on IGF_SL_DL_CHG_RESP_ALL.DBTH_ID = IGF_SL_DL_BATCH_ALL.DBTH_ID.
• IGF_SL_DL_CHG_RESP_ALL_PK — the primary key constraint enforcing uniqueness of RESP_NUM.

Because the module is obsolete, dependent views and APIs are limited; migration and archival scripts typically reference the parent batch table as the sole documented foreign-key relationship.