Search Results lor_resp_num




Overview

IGF.IGF_SL_DL_LOR_CRRESP_ALL is an Oracle E-Business Suite table owned by the IGF schema, deployed under the Financial Aid module for the Direct Loan processing flow. It is registered in FND Design Data as IGF.IGF_SL_DL_LOR_CRRESP_ALL with a status of VALID. The table maintains the loan origination's credit history for a parent response originating from the loan origination center. In practical terms, each row captures the credit decision and Master Promissory Note (MPN) attributes returned by the loan origination servicer and links that credit response back to a submission batch.

The object resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its unique index IGF_SL_DL_LOR_CRRESP_ALL_U1 lives in APPS_TS_TX_IDX. From a Data Vault modeling perspective, the schema shape — a single business key, a foreign key to a batch parent, and change-dated descriptive attributes — suggests a satellite-leaning classification. This is a heuristic suggestion rather than a documented Data Vault designation: the record describes the state of an originating business entity (the credit response) over time, keyed by LOR_RESP_NUM and dependent on IGF_SL_DL_BATCH_ALL.

Key Information Stored

The table is defined with 21 columns. The primary key is IGF_SL_DL_LOR_CRRESP_ALL_PK, enforced on LOR_RESP_NUM, a NUMBER(15) that identifies the Direct Loan loan origination credit response record. A second unique index, IGF_SL_DL_LOR_CRRESP_ALL_U1, is also defined on LOR_RESP_NUM, confirming it as the single business-key candidate in the documented schema.

Common Use Cases and Queries

Typical usage centers on reconciling credit responses received from the loan origination center against batches and on reporting MPN and credit decision outcomes. Because LOR_RESP_NUM is the primary key, lookups by response identifier are the most efficient access path.

  • Retrieve all credit responses belonging to a batch:
    SELECT LOR_RESP_NUM, LOAN_NUMBER, CREDIT_DECISION_DATE, STATUS FROM IGF_SL_DL_LOR_CRRESP_ALL WHERE DBTH_ID = :p_batch_id;
  • Fetch a single credit response:
    SELECT * FROM IGF_SL_DL_LOR_CRRESP_ALL WHERE LOR_RESP_NUM = :p_lor_resp_num;
  • Report credit decisions within a date range for an operating unit:
    SELECT LOAN_NUMBER, CREDIT_OVERRIDE, CREDIT_DECISION_DATE FROM IGF_SL_DL_LOR_CRRESP_ALL WHERE ORG_ID = :p_org_id AND CREDIT_DECISION_DATE BETWEEN :p_from AND :p_to;
  • Track MPN issuance status across responses:
    SELECT LOAN_NUMBER, MPN_ID, MPN_STATUS, MPN_TYPE, MPN_INDICATOR FROM IGF_SL_DL_LOR_CRRESP_ALL WHERE MPN_STATUS IS NOT NULL;

Related Objects

The documented foreign key relationship ties this table to the batch parent, which is the primary integration point for joins and referential integrity.

  • IGF.IGF_SL_DL_BATCH_ALL — referenced via IGF_SL_DL_LOR_CRRESP_ALL.DBTH_ID → IGF_SL_DL_BATCH_ALL; join on DBTH_ID to associate each credit response with its originating submission batch.
  • IGF.IGF_SL_DL_LOR_CRRESP_ALL_PK — the primary key constraint on LOR_RESP_NUM.
  • IGF.IGF_SL_DL_LOR_CRRESP_ALL_U1 — the unique index on LOR_RESP_NUM in APPS_TS_TX_IDX.

Queries joining the credit response to its batch should key on DBTH_ID and preserve the MOAC filter on ORG_ID to respect operating unit security.