Search Results s_phone




Overview
Explore in AI Chat

Overview

APPS.IGF_SL_DL_PNOTE_S_P is a multi-org view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 application schema, registered under FND Design Data as IGF.IGF_SL_DL_PNOTE_S_P and holding VALID status in the ETRM repository. It belongs to the Oracle Student Financial Aid (IGF) product family and exposes promissory note (PNOTE) data associated with student loan disbursements and borrower records. The "_S_P" suffix indicates that this is a secured, multi-org filtered view — Oracle EBS creates a synonym/secure view layer over an underlying "_ALL" table so that queries automatically restrict rows to the current operating unit identified by ORG_ID, ignoring data belonging to other operating units. This design is standard for EBS entities that are partitioned by operating unit and reinforces the Multi-Org Access Control (MOAC) model.

Functionally, the view presents borrower personal data (name, SSN, date of birth, driver license attributes, permanent address, email, and phone) joined to loan and batch identifiers, making it suitable for reporting, printing, and integration scenarios involving Federal Direct Loan or similar student lending promissory notes. The presence of the request/program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) indicates the view is populated or refreshed via concurrent program processing, consistent with EBS batch loading conventions.

Underlying Base Objects

The documented dependency chain shows that APPS.IGF_SL_DL_PNOTE_S_P references the base table APPS.IGF_SL_DL_PNOTE_S_P_ALL. In EBS multi-org architecture, the "_ALL" table stores records for every operating unit, carrying an ORG_ID column, while the "_S_P" secured view applies the MOAC predicate against ORG_ID so that only the currently-selected operating unit's rows are visible. The view is further referenced by APPS.IGF_SL_DL_PNOTE_S_P_V and by the concurrent program object IGF_SL_DL_PRINT_PNOTE, indicating that the promissory note print concurrent program reads from this layered view to obtain borrower data. ETRM documents the view's query text as a straight SELECT of ROW_ID-based column list from the APPS schema, with no documented additional joins or aggregations.

Key Columns

Common Use Cases and Queries

This view is typically queried to extract borrower promissory note information for printing, reconciliation, or downstream reporting within the current operating unit. A representative query retrieving borrower phone and loan details follows:

  • SELECT PNSP_ID, LOAN_NUMBER, S_FIRST_NAME, S_LAST_NAME, S_PHONE, S_EMAIL_ADDR, STATUS FROM APPS.IGF_SL_DL_PNOTE_S_P WHERE LOAN_NUMBER = :loan_number;
  • SELECT PNSP_ID, S_SSN, S_PERMT_ADDR1, S_PERMT_CITY, S_PERMT_STATE, S_PERMT_ZIP FROM APPS.IGF_SL_DL_PNOTE_S_P WHERE PERSON_ID = :person_id;
  • SELECT PNSP_ID, BATCH_SEQ_NUM, LOAN_ID, S_PHONE FROM APPS.IGF_SL_DL_PNOTE_S_P WHERE REQUEST_ID = :request_id ORDER BY BATCH_SEQ_NUM;

Because ORG_ID filtering is implicit in the "_S_P" layer, callers do not need to add the ORG_ID predicate manually, provided the correct operating unit context is set through the EBS MOAC framework. Direct ad-hoc queries should set the client identifier or operating unit context to avoid returning misleading row sets.