Results for “response_status_code”

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

Overview

IGF_SL_CLCHSN_DTLS_V is an APPS-owned database view in the Oracle E-Business Suite Financial Aid (IGF) product family. Its stated purpose is to store, and expose for reporting, all change records associated with a student loan record for the CommonLine Release 4 specification. CommonLine is the industry-standard electronic data exchange format used between schools, lenders, guarantors, and servicers for the origination and disbursement of Title IV loan funds, and Release 4 governs the schema and semantics of the change transactions exchanged between those parties.

Because the object is a view rather than a table, it does not itself store data; it presents a denormalized, report-friendly projection of the underlying change transaction table together with decoded lookup descriptions. This design shields downstream reports, extracts, and interfaces from having to join the Change Send base table to the lookup tables manually. The view retains the ROWID of the driving base table as its first select-list item, which is significant for Oracle Forms-based maintenance blocks and for any update-through-view behavior.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2. The 12.2.2 online patching architecture, which relies on editioning views over tables, does not change the definition or semantics of a standard APPS reporting view such as this one; the object remains visible in the APPS schema and is queried in the same manner in either release.

Underlying Base Objects

The view text references two principal base tables: IGF_SL_CLCHGSND (aliased CLCHGSND), which is the driving table holding the individual change send records, and IGF_SL_CLCHRTS (aliased CLCHRTS), which supplies change code and record type descriptions. The view also invokes the stored function IGF_AW_GEN.LOOKUP_DESC on several occasions to translate coded values into human-readable descriptions using the lookup types required by the CommonLine change record: IGF_SL_CL_CHG_ISSUE_CODES, IGF_SL_CL_CHANGE_FIELDS, IGF_SL_CL_CHG_REINST_CODES, IGF_SL_CL_CHG_REISSUE_CODES, IGF_SL_CL_DB_FUND_DISB_METH, IGF_SL_CL_CHG_RESP_STATUS, and IGF_SL_CL_CHG_REC_STATUS.

The view therefore inherits the grain of IGF_SL_CLCHGSND — one row per change detail line tied to an award, loan number, and disbursement number. Because the decode logic is encapsulated in the function call rather than in a join, the lookup tables themselves are not exposed as referenced base objects, which explains why the ETRM metadata records no documented base objects for this view.

Key Columns

Identifying columns include CLCHGSND_ID (primary key surrogate), CL_VERSION_CODE, AWARD_ID, LOAN_NUMBER_TXT, DISBURSEMENT_NUMBER, and DISBURSEMENT_DATE. Change semantics are carried by CHANGE_ISSUE_CODE and its decoded description, CHANGE_CODE_TXT with CHANGE_CODE_DESCRIPTION, CHANGE_FIELD_CODE with its decoded description, and CHANGE_RECORD_TYPE_TXT with RECORD_DESCRIPTION_TXT.

Before-and-after values are stored in paired columns: OLD_VALUE_TXT / NEW_VALUE_TXT for character changes, OLD_AMT / NEW_AMT for monetary changes, and OLD_DATE / NEW_DATE for date changes. The column NEW_DATE is precisely the field returned when a user searches for "new_date"; it holds the post-change value of whichever date field was modified (for example a revised disbursement date or anticipated disbursement date).

Disbursement-level adjustment columns include DISBURSEMENT_CANCEL_AMT, DISBURSEMENT_CANCEL_DATE, DISBURSEMENT_REINST_CODE, DISBURSEMENT_REISSUE_CODE, DISBURSEMENT_RETURN_AMT, DISBURSEMENT_RETURN_CODE, DISBURSEMENT_RETURN_DATE, DISBURSEMENT_REVISED_AMT, and DISBURSEMENT_REVISED_DATE. Each code column is paired with a decoded lookup description. Process and audit columns include RESPONSE_STATUS_CODE, STATUS_CODE, STATUS_DATE, SEND_RECORD_TXT, VALIDATION_EDIT_TXT, plus the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID.

Common Use Cases and Queries

Typical uses include auditing loan disbursement changes for a given award, validating that a change was transmitted and acknowledged, and building CommonLine change extracts. A query scoped to a single award and the new date value would resemble:

• SELECT award_id, loan_number_txt, disbursement_number, change_field_code, old_date, new_date FROM igf_sl_clchsn_dtls_v WHERE award_id = :award_id ORDER BY disbursement_number;
• SELECT clchgsnd_id, new_date FROM igf_sl_clchsn_dtls_v WHERE new_date BETWEEN :from_date AND :to_date;
• SELECT change_issue_code, change_code_description, new_amt, new_date, status_code FROM igf_sl_clchsn_dtls_v WHERE status_code = 'NEW';

Reports joining the view to IGF_AW_AWARDS on AWARD_ID, or filtering on RESPONSE_STATUS_CODE to isolate unacknowledged changes, are equally common. All queries should qualify the APPS schema or rely on the standard APPS synonym resolution.