Results for “b_first_name”

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

Overview

IGF_SL_DL_MANIFEST is a reporting view within the Oracle E-Business Suite IGF (Financial Aid) application, historically associated with the Student Loan (SL) and Direct Loan (DL) processing functionality. In the ETRM documentation set for Oracle EBS 12.1.1 and 12.2.2 it appears under the product designation "IGF – Financial Aid (Obsolete)," meaning the module is no longer actively supported or installed in current environments. The metadata explicitly records that the object is "Not implemented in this database," confirming that the view is documented for historical and reference purposes rather than for active operational use.

Functionally, the view presents a consolidated manifest of loan records that were staged for origination or submission to a lending authority. It exposes borrower identity attributes, loan identifiers, batch sequencing, and standard Oracle audit and multi-org columns. Because the manifest concept centered on reconciling loan batches against downstream disbursement and Common Origination and Disbursement (COD) feeds, the view served reporting, extraction, and integration roles rather than transactional data entry.

Underlying Base Objects

The view text shows that it is defined over a single base table, IGF_SL_DL_MANIFEST_ALL, aliased PNMN. The ETRM metadata records no other referenced base objects, and the SELECT statement does not include any joins to additional tables. The "_ALL" suffix follows the standard Oracle multi-org convention, indicating that the underlying table stores rows partitioned by ORG_ID and that a corresponding org-striped synonym or view would restrict results to the operating unit of the session.

IGF_SL_DL_MANIFEST therefore acts as the reporting layer over IGF_SL_DL_MANIFEST_ALL, applying row-level multi-org security while exposing the same column set. The presence of a ROWID column in the SELECT list is a legacy pattern used to support certain Oracle Forms or updatable-view behaviors.

Key Columns

• ROW_ID (ROWID) – Physical row identifier from the base table; used for row-level addressing in legacy forms.
• PNMN_ID – Primary key of the loan manifest record within IGF_SL_DL_MANIFEST_ALL.
• BATCH_SEQ_NUM – Sequence number grouping loan records into submission batches.
• LOAN_ID / LOAN_NUMBER – Internal loan identifier and the external loan number used by the lender.
• B_SSN, B_FIRST_NAME, B_LAST_NAME, B_MIDDLE_NAME – Borrower (B_) identification attributes.
• STATUS – Processing state of the manifest record (e.g., staged, transmitted, accepted).
• ORG_ID – Operating unit identifier driving multi-org security.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard who-columns for audit.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent program context columns indicating which request generated or last modified the record.

Common Use Cases and Queries

The primary historical use case was reconciliation of loan batches prior to transmission, and reporting on manifest status by operating unit. Because the view applies multi-org filtering through USERENV('CLIENT_INFO'), queries return only records visible to the current operating unit context.

SELECT PNMN_ID,
       BATCH_SEQ_NUM,
       LOAN_NUMBER,
       B_SSN,
       B_LAST_NAME,
       STATUS,
       CREATION_DATE
FROM   IGF_SL_DL_MANIFEST
WHERE  STATUS = 'STAGED'
ORDER  BY BATCH_SEQ_NUM, LOAN_NUMBER;

A second pattern retrieves concurrent program provenance for audit or troubleshooting:

SELECT REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, COUNT(*)
FROM   IGF_SL_DL_MANIFEST
GROUP  BY REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE
ORDER  BY PROGRAM_UPDATE_DATE DESC;

Because the product is obsolete and the object is not implemented in the referenced database, these queries are provided for documentation and migration analysis only. Organizations migrating off IGF should confirm whether IGF_SL_DL_MANIFEST_ALL still exists in their schema and, if so, extract data before decommissioning the module.