Search Results b_resp_code

Overview

APPS.IGF_SL_RESP_DTLS_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as IGF.IGF_SL_RESP_DTLS_V. It belongs to the Financial Aid / Student Loan (IGF) product family and functions as a "response details" view over Student Loan (SL) response data imported from external servicers and the Common Origination and Disbursement (COD) processing channel. Its ETRM status is VALID.

Functionally, the view flattens and labels the inbound response documents that a school receives after submitting loan origination, disbursement, or change records to the COD system. Each row represents a single response document together with the identifying data for the reporting (attending) school, the destination entity, the student, and the associated response codes. Because it exposes both document-level attributes and person-level attributes in one row, it is well suited to operational inquiry forms, reconciliation, and downstream reporting on the status of a loan response message.

Oracle explicitly documents this object as a supplementary view used to simplify forms coding, and cautions that the view should not be queried or altered for data maintenance purposes because its definition may change substantially between minor or major releases. As a result, it is best consumed as a read-only projection rather than as a stable integration contract.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects. The view is not defined as a join over a single table; consistent with the IGF_SL_%_V family, it is a selection/derivation view over the COD response staging and student loan response entities. Attributes such as REP_SCHL_RESP_ID, ATD_SCHL_RESP_ID, and STDNT_RESP_ID are surrogate identifiers carried from the base response records, while the *_TXT columns (DOCUMENT_ID_TXT, SOURCE_ENTITY_ID_TXT, DEST_ENTITY_ID_TXT, REP_ENTITY_ID_TXT, ATD_ENTITY_ID_TXT) are the external system identifiers delivered in the response file.

Because the metadata does not enumerate the base objects, columns should be treated as the authoritative interface. The identifiers named above are the practical join keys back to the student loan response base tables, and they are the correct route for any reconciliation query that must reach detail rows not exposed by this view.

Key Columns

• DOCUMENT_ID_TXT, DOC_CREATED_DATE, RECEIPT_DATE, PROCESS_DATE, DOC_TYPE_CODE, DOC_STATUS_CODE, FULL_RESP_CODE — the document envelope: which response was received, when it was created, when it was received and processed at COD, its type, its processed status, and the overall response code.
• SOURCE_ENTITY_ID_TXT, DEST_ENTITY_ID_TXT, SOFT_PROVIDER, SOFT_VERSION — routing and provenance metadata identifying the sending and receiving entities and the software that produced the file.
• REP_SCHL_RESP_ID, REP_ENTITY_ID_TXT, RS_RESP_CODE — the reporting school response record and its response code.
• ATD_SCHL_RESP_ID, ATD_ENTITY_ID_TXT, AS_RESP_CODE — the attending school response record and its response code.
• STDNT_RESP_ID, S_SSN, FIRST_NAME, S_LAST_NAME, S_DATE_OF_BIRTH, ST_RESP_CODE — the student response record and identifying demographics.

The pending leading characters on the student columns reflect an alphabetical column listing truncated in the source documentation; the columns continue beyond ST_RESP_CODE.

Common Use Cases and Queries

The principal use case is reviewing the outcome of a loan response submission. A typical query filters on the document metadata and joins to the student loan response header:

• SELECT document_id_txt, doc_type_code, doc_status_code, full_resp_code, receipt_date FROM igf_sl_resp_dtls_v WHERE doc_status_code = 'R' AND receipt_date >= SYSDATE - 30;
• SELECT destination_entity_id_txt, atd_entity_id_txt, as_resp_code, COUNT(*) FROM apps.igf_sl_resp_dtls_v GROUP BY destination_entity_id_txt, atd_entity_id_txt, as_resp_code;
• SELECT rep_schl_resp_id, rep_entity_id_txt, rs_resp_code FROM apps.igf_sl_resp_dtls_v WHERE doc_type_code = :p_doc_type;
• SELECT stdnt_resp_id, s_ssn, first_name, s_last_name, st_resp_code FROM apps.igf_sl_resp_dtls_v WHERE stdnt_resp_id = :p_resp_id;

Users searching for terms such as "dl_loan_type" generally reach this view from the response detail inquiry path: loan type is carried on the associated response or loan detail records and is resolved by joining on the response IDs exposed here (REP_SCHL_RESP_ID, ATD_SCHL_RESP_ID, STDNT_RESP_ID) rather than on a column within the view itself. All access should be read-only, and the view should not be modified.