Search Results pnote_ack_date

Overview

IGF_SL_DL_PNOTE_RESP is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and delivered under the IGF – Financial Aid product family. Its status is VALID, and it is available in both the 12.1.1 and 12.2.2 releases. The view exposes Promissory Note (PNOTE) response data associated with the Federal Direct Loan (DL) processing flow used by institutions that participate in the William D. Ford Direct Loan Program.

The view presents a multi-organization (ORG_ID) filtered projection of the underlying response records, meaning it is designed to show only the rows that belong to the organization currently established in the session context. Its principal purpose in the EBS reporting and integration layer is to provide a secure, convenient data source for concurrent programs, OBIEE/BI Publisher reports, and interface extracts that need to reconcile promissory note acknowledgments, rejections, and accepted amounts returned from the Direct Loan servicer (COD). Because it filters through ORG_ID, it functions as a reporting convenience layer over the "_ALL" table and prevents cross-organization data leakage in multi-org enabled installations.

Underlying Base Objects

The view is defined over a single base object: IGF_SL_DL_PNOTE_RESP_ALL (aliased DLPNR). No additional joins, lookup tables, or reference objects are documented in the ETRM metadata. The "_ALL" suffix is significant: the base table stores promissory note response records for all organizations, and the view applies the standard Oracle multi-org security predicate to restrict results.

The filtering predicate compares the ORG_ID column to a value decoded from the USERENV('CLIENT_INFO') session parameter. When the first character of CLIENT_INFO is a space, the decoded value is NULL; the NVL chain defaults unmatched values to -99. This is the conventional EBS multi-org view pattern and confirms that the view should be queried within an initialized applications session (FND_GLOBAL / multi-org initialization) to return correct results. Querying it outside an initialized session can yield empty result sets.

Key Columns

• DLPNR_ID – Primary key surrogate for the promissory note response row.
• DBTH_ID – Identifier linking the response to the associated Direct Loan disbursement or borrower/loan record.
• LOAN_NUMBER – The Direct Loan number as assigned by the servicer.
• PNOTE_STATUS – Status of the promissory note response (e.g., accepted, rejected, acknowledged).
• PNOTE_ACK_DATE – Date the promissory note acknowledgment was received.
• PNOTE_BATCH_ID – Batch identifier for the inbound response file that delivered this record.
• PNOTE_REJ_CODES – Rejection code(s) returned when a note is not accepted.
• PNOTE_ACCEPT_AMT – Accepted loan amount associated with the response.
• MPN_IND / ELEC_MPN_IND – Flags indicating whether the record relates to a Master Promissory Note and/or an electronic MPN.
• STATUS – General record status.
• ORG_ID – Operating unit / organization identifier enforced by the view predicate.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Concurrent program columns – REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE for traceability of the load process.

Common Use Cases and Queries

Typical uses include reconciling Direct Loan promissory note responses for a given batch, producing financial aid compliance reports, and driving downstream disbursement release logic. A representative query lists rejected notes within the current organization:

SELECT loan_number, pnote_status, pnote_rej_codes, pnote_ack_date
FROM igf_sl_dl_pnote_resp
WHERE pnote_status = 'R';

To reconcile a specific inbound batch:

SELECT loan_number, pnote_accept_amt, pnote_ack_date, elec_mpn_ind
FROM igf_sl_dl_pnote_resp
WHERE pnote_batch_id = :batch_id;

Because ORG_ID filtering is applied automatically, developers should not add an explicit ORG_ID predicate unless intentionally crossing organizations; instead, ensure the session is multi-org initialized. For cross-organization extracts, the underlying IGF_SL_DL_PNOTE_RESP_ALL table should be queried directly.