Results for “prom_note_accepted_amount”

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

Overview

IGFBV_DL_PROM_NOTE_RESPONSES is a base view owned by the APPS schema in the IGF (Financial Aid) product module of Oracle E-Business Suite. It exposes the entity that holds Financial Aid Direct Loan Promissory Note Responses, providing a consolidated, read-only presentation of promissory note acknowledgment data joined with disbursement detail responses. The view is defined WITH READ ONLY, meaning it cannot be used as the target of DML statements and is intended strictly for query, reporting, and integration consumption.

The view plays a supporting role in the Direct Loan processing flow, where promissory note responses returned from the Common Origination and Disbursement (COD) process must be reconciled against expected disbursements. Because the view flattens the relationship between promissory note responses and their associated disbursement response records, it is well suited to reporting layers, extracts, and downstream interfaces that need loan-level note status alongside gross disbursement amounts without navigating multiple base tables.

Underlying Base Objects

The view text is defined over two base tables joined on the DLPNR_ID key:

• IGF_SL_DL_PNOTE_RESP_ALL — the promissory note response table (aliased PNOTERESP), supplying note acknowledgment dates, batch identifiers, loan numbers, note status codes, rejection reason codes, MPN indicators, and accepted amounts.
• IGF_SL_DL_PDET_RESP — the disbursement detail response table (aliased PDETRESP), supplying gross disbursement amounts and the DLPDR_ID/DLPNR_ID linkage, together with audit columns.

The join condition is PDETRESP.DLPNR_ID = PNOTERESP.DLPNR_ID, so each row represents a promissory note response combined with its associated disbursement detail response. The view performs no aggregation; cardinality depends on the number of disbursement detail responses tied to each promissory note response. Although ETRM documents no referenced base objects explicitly, the view SQL confirms the two tables above as the physical sources, with lookup-driven columns resolved through IGF_LOOKUPS_VIEW against lookup types such as IGF_SL_DL_PNOTE_STATUS, IGF_SL_PNOTE_REJ_CODES, and IGF_SL_DL_RESP_STATUS.

Key Columns

The view exposes both physical columns and virtual lookup-description columns (prefixed _LA:) used by Oracle's descriptive flexfield-style lookup resolution. Notable columns include:

• MASTER_PROM_NOTE_INDICATOR (physical column MPN_IND) — indicates whether the promissory note is a Master Promissory Note. This is the column most commonly targeted by users searching "master_prom_note_indicator."
• ELEC_MPN_INDICATOR (ELEC_MPN_IND) — flags electronic MPN processing.
• PROM_NOTE_ACK_DATE — date the promissory note was acknowledged.
• PROM_NOTE_BATCH_ID and BATCH_ID — batch identifiers for the note and disbursement response respectively.
• LOAN_NUMBER — the Direct Loan identifier.
• PROM_NOTE_ACCEPTED_AMOUNT and DISBURSEMENT_GROSS_AMOUNT — accepted note amount versus gross disbursement amount.
• "_LA:PROM_NOTE_STATUS", "_LA:PNOTE_REJECTION_REASONS", "_LA:RECORD_STATUS" — decoded lookup meanings for status, rejection codes, and record status.
• RESPONSE_RECORD_ID (DLPNR_ID), DISBURSEMENT_NUMBER (DLPDR_ID), BATCH_ID (DBTH_ID) — internal identifiers linking back to the base entities.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include reconciling COD promissory note acknowledgments, reporting MPN versus non-MPN loans, and identifying rejected notes. A representative query listing MPN loans with accepted amounts is:

• SELECT loan_number, prom_note_batch_id, master_prom_note_indicator, prom_note_accepted_amount, prom_note_ack_date FROM igfbv_dl_prom_note_responses WHERE master_prom_note_indicator = 'Y';
• SELECT loan_number, "_LA:PROM_NOTE_STATUS" note_status, disbursement_gross_amount FROM igfbv_dl_prom_note_responses WHERE "_LA:RECORD_STATUS" IS NOT NULL;
• SELECT prom_note_batch_id, COUNT(*) FROM igfbv_dl_prom_note_responses GROUP BY prom_note_batch_id;

Because the view is read-only and joins note responses to disbursement responses, queries should account for potential multiple disbursement rows per note. Filtering on MASTER_PROM_NOTE_INDICATOR is the standard method for isolating MPN-related records sought by users of this object.