Search Results requested_loan_amt




Overview
Explore in AI Chat

Overview

The view IGF_SL_LOR belongs to the Oracle EBS IGF – Financial Aid product family, a module now designated as obsolete within the ETRM reference set. It exposes Student Loan Origination (LOR) records, denormalizing the origination lifecycle of a student loan into a single, query-friendly projection. In functional terms, the view presents the origination transaction state of a loan: borrower and serial loan codes, promissory note (P-Note) handling, guarantor and lender status codes, disbursement and refund amounts, and the standard EBS audit trail columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus REQUEST_ID to correlate rows with concurrent request executions.

The user search term "requested_loan_amt" is significant. This view does not expose a column literally named REQUESTED_LOAN_AMT; the requested amount is stored on the parent loan record rather than the origination row. Analysts searching for that term in relation to IGF_SL_LOR are typically trying to reconcile the amount requested by the borrower against the amounts represented here (GUARANTEE_AMT, PNOTE_ACCEPT_AMT, SCH_REFUND_AMT).

The ETRM metadata states that this view is not implemented in this database, and lists no documented base objects. Reporting built against it must therefore be treated as reference/legacy only.

Underlying Base Objects

Per the ETRM documentation, no base tables are formally documented for this view. The view text itself shows a single driving alias LOR, with every projected column prefixed LOR., indicating one primary Student Loan Origination table. The literal NULL placeholders in the SELECT list (for example after ORIG_BATCH_DATE and near the credit/guarantor block) are positional stubs where the underlying table was widened over releases but the view was never republished with the newer columns. The row identifier is exposed as LOR.ROWID, and REQUEST_ID traces the row back to the originating concurrent program run.

Key Columns

Common Use Cases and Queries

Because "requested_loan_amt" is not held here, a practical pattern is to retrieve the origination context and join outward to the loan master for the requested figure.

SELECT lor.origination_id,
       lor.loan_id,
       lor.orig_status_flag,
       lor.guarantee_amt,
       lor.pnote_accept_amt,
       lor.request_id
FROM   igf_sl_lor lor
WHERE  lor.creation_date >= :start_date
ORDER  BY lor.creation_date DESC;

Additional scenarios include auditing promissory note acceptance against the lender decision date, tracing a disputed origination back to its concurrent request via REQUEST_ID, and reconciling GUARANTEE_AMT to the requested loan amount sourced from the parent loan table. All such development should confirm availability first, since the metadata records the view as unimplemented in the database.