Search Results pnote_accept_amt




Overview

APPS.IGF_SL_DL_LOR_RESP is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Financials/Student systems schema (IGF), part of the Oracle Financial Aid module's Student Loan (SL) "Direct Loan" (DL) processing area. The view exposes Letter of Responsibility (LOR) response data captured from the Common Origination and Disbursement (COD) interface used by Title IV federal student aid processing. Its FND Design Data reference (IGF.IGF_SL_DL_LOR_RESP) indicates it is a registered, translatable design object within the IGF application. The object is documented as VALID and carries a "multi-org" view type designation, meaning queries against it are automatically restricted by the operating unit (ORG_ID) of the current session.

The view is a thin projection over the underlying _ALL table and is intended primarily for reporting, inquiry, and integration lookups rather than for transactional data entry. The ORIG_STATUS_FLAG column, which featured in the user's search, is a VARCHAR2(30) field carrying the originating (COD-side) status indicator for the LOR response — typically values distinguishing accepted, rejected, pending, or awaiting-action states returned by the federal processor.

Underlying Base Objects

According to the documented dependency information, APPS.IGF_SL_DL_LOR_RESP references exactly one base object: APPS.IGF_SL_DL_LOR_RESP_ALL. The _ALL table is the multi-org-enabled master table, storing records for all operating units. The view applies the standard multi-org security predicate, effectively filtering _ALL rows to those matching the session's ORG_ID, so the view presents operating-unit-scoped data while the underlying table retains the full enterprise dataset.

Downstream, the view is referenced by two dependency components: IGF_SL_DL_ORIG_ACK and IGF_SL_REJ_WF. This confirms the view participates in both the origination acknowledgement processing logic and the loan rejection workflow logic, making ORIG_STATUS_FLAG and the related PNOTE/ORIG columns directly relevant to those functional areas.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling COD acknowledgement statuses, identifying rejected LOR responses requiring workflow action, and reporting accepted loan amounts by batch or borrower.

SELECT LOR_RESP_NUM, LOAN_NUMBER, ORIG_BATCH_ID,
       ORIG_STATUS_FLAG, ORIG_ACK_DATE, STATUS
FROM   APPS.IGF_SL_DL_LOR_RESP
WHERE  ORIG_STATUS_FLAG = 'R';
SELECT ORIG_BATCH_ID, COUNT(*) AS RESPONSES,
       SUM(LOAN_AMOUNT_ACCEPTED) AS ACCEPTED_AMT
FROM   APPS.IGF_SL_DL_LOR_RESP
WHERE  ORIG_ACK_DATE >= :from_date
GROUP  BY ORIG_BATCH_ID;

Because the view is multi-org filtered, ORG_ID need not be supplied explicitly when querying within a properly initialized session; the ORG_ID column remains available for verification and reporting. Queries should be directed to the view rather than the _ALL table to inherit operating-unit security.