Results for “igf_sl_dl_pnote_s_p_all”

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

Overview

IGF_SL_DL_PNOTE_S_P_ALL is a Financial Aid (IGF) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the Stafford Loan identification details that have been selected for printing and populated by the Direct Loan Promissory Note Print process. The object resides in the IGF schema and is documented with thirty columns. Its primary key is IGF_SL_DL_PNOTE_S_P_ALL_PK, defined on the PNSP_ID column, and a unique index IGF_SL_DL_PNOTE_S_P_ALL_U1 also exists on PNSP_ID, confirming PNSP_ID as the sole business-key candidate. The table carries a single documented foreign key: LOAN_ID referencing IGF_SL_LOANS_ALL. Based on the foreign key structure mined from the ETRM metadata, the heuristic Data Vault classification is satellite-leaning — that is, the table is best modeled as a satellite attached to the IGF_SL_LOANS_ALL hub, since it captures descriptive, process-scoped detail about a loan rather than acting as an independent business entity.

Key Information Stored

The surrogate primary key, PNSP_ID, uniquely identifies each promissory-note print record and is enforced both by the primary key constraint and the unique index. The principal business link to the parent loan is LOAN_ID, which references IGF_SL_LOANS_ALL and is the join column that ties a print row to its loan. LOAN_NUMBER carries the human-readable loan identifier used in correspondence and reconciliation.

The table stores a snapshot of borrower identity and contact attributes needed for the promissory note form: PERSON_ID, S_SSN, S_FIRST_NAME, S_LAST_NAME, S_MIDDLE_NAME, S_DATE_OF_BIRTH, S_LICENSE_NUM, S_LICENSE_STATE, and the permanent address elements S_PERMT_ADDR1, S_PERMT_ADDR2, S_PERMT_CITY, S_PERMT_STATE, and S_PERMT_ZIP. Contact channels include S_EMAIL_ADDR and S_PHONE. Process and audit context is provided by BATCH_SEQ_NUM (print batch sequencing), STATUS (row processing state), ORG_ID (multi-org partitioning), REQUEST_ID (concurrent request that generated the row), and the standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. Academic program context is held in PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on promissory note print reporting, batch reconciliation, and borrower data verification. To list all unprinted or in-process notes for a batch:

• SELECT pnsp_id, loan_id, loan_number, batch_seq_num, status FROM igf.igf_sl_dl_pnote_s_p_all WHERE status = :status ORDER BY batch_seq_num;
• To resolve a printed note back to its loan record: SELECT p.*, l.* FROM igf.igf_sl_dl_pnote_s_p_all p, igf.igf_sl_loans_all l WHERE p.loan_id = l.loan_id AND p.loan_number = :loan_number;
• To audit activity from a specific concurrent request: SELECT pnsp_id, loan_id, status, creation_date FROM igf.igf_sl_dl_pnote_s_p_all WHERE request_id = :request_id;
• To validate borrower address completeness prior to printing: SELECT person_id, s_last_name, s_permt_city, s_permt_state, s_permt_zip FROM igf.igf_sl_dl_pnote_s_p_all WHERE s_permt_addr1 IS NULL OR s_permt_city IS NULL;

Filtering by ORG_ID is advisable in multi-organization deployments, as the column supports operating-unit partitioning.

Related Objects

The most significant related objects are those connected through the documented foreign key and the shared loan/person model:

• IGF_SL_LOANS_ALL — parent loan table joined on IGF_SL_DL_PNOTE_S_P_ALL.LOAN_ID = IGF_SL_LOANS_ALL.LOAN_ID.
• IGF_SL_DL_PNOTE_S_P_ALL_PK — primary key constraint/index on PNSP_ID.
• IGF_SL_DL_PNOTE_S_P_ALL_U1 — unique index on PNSP_ID supporting business-key resolution.
• Direct Loan Promissory Note Print concurrent program — the process that populates BATCH_SEQ_NUM, STATUS, and REQUEST_ID.
• Person/party objects keyed by PERSON_ID — used to validate borrower demographics such as S_SSN and S_DATE_OF_BIRTH.
• Program and application objects keyed by PROGRAM_ID and PROGRAM_APPLICATION_ID — used to associate notes with academic funding context.

All relationships above are documented in ETRM; joins on LOAN_ID should be treated as the authoritative linkage.