Results for “igf_sl_edit_orig_chg_code”

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

Overview

IGF_SL_EDIT_REPORT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product family. In Release 12.1.1 and 12.2.2, this view exposes the contents of the Student Loan edit-reporting process, which validates loan data against federal and institutional edit rules before transmission to the lender or servicer. Each row in the view represents a single edit failure or change-record condition detected on a specific student loan record, together with the field that triggered the condition and the offending value.

The view is read-only by design. It carries a VALID status in the data dictionary and is classified as a VIEW object type. Its primary role is to support operational reporting, troubleshooting, and downstream file generation for the Student Loan interface. Because edit results must frequently be reviewed by financial aid administrators and extracted into correctable output, the view also serves as the logical source for concurrent programs and interfaces that consume Student Loan error data.

Underlying Base Objects

The view is defined over a single documented base object, the table IGF_SL_EDIT_REPORT (aliased as EDTR in the view text). No other base tables are documented as referenced objects. The view text is a direct projection of the table's columns, with one notable enhancement: several descriptive columns are derived at query time rather than stored. Specifically, ORIG_CHG_DESC, SL_ERROR_DESC, and FIELD_DESC are produced by calls to IGF_AW_GEN.LOOKUP_DESC, which resolves the stored code values into their corresponding lookup meanings.

This design keeps the physical table normalized to code values while presenting decoded, human-readable descriptions through the view. It also means that consumers of the view implicitly depend on the IGF_AW_GEN package and on the lookup types IGF_SL_EDIT_ORIG_CHG_CODE and IGF_SL_LOAN_FIELDS being populated with current data. Because the view performs no joins or unions against other business tables, the one-to-one relationship between the view and IGF_SL_EDIT_REPORT is preserved: every row returned corresponds to exactly one row in the base table.

Key Columns

• ROW_ID — The unique row identifier of the edit report record, used for direct row retrieval.
• EDTR_ID — The internal identifier of the edit report transaction or batch entry associated with the error.
• LOAN_NUMBER — The student loan identifier against which the edit was evaluated.
• ORIG_CHG_CODE / ORIG_CHG_DESC — The originating change code and its decoded description, indicating the source of the change or edit.
• SL_ERROR_TYPE / SL_ERROR_CODE / SL_ERROR_DESC — The error classification, the specific error code, and the lookup-resolved description of the error condition.
• FIELD_NAME / FIELD_DESC — The name of the loan field that failed validation and its decoded description from the IGF_SL_LOAN_FIELDS lookup.
• FIELD_VALUE — The actual value held in the flagged field at the time of the edit run.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified the record and when.

Common Use Cases and Queries

Typical usage centers on isolating errors for a given loan or error type, and on producing decoded output for administrators. The following query lists all edit failures for a loan, showing the field and its value:

• SELECT loan_number, sl_error_code, sl_error_desc, field_name, field_desc, field_value FROM igf_sl_edit_report_v WHERE loan_number = :p_loan_number;
• SELECT sl_error_type, sl_error_code, sl_error_desc, COUNT(*) FROM igf_sl_edit_report_v GROUP BY sl_error_type, sl_error_code, sl_error_desc ORDER BY 4 DESC;
• SELECT edtr_id, orig_chg_desc, field_name, field_value, creation_date FROM igf_sl_edit_report_v WHERE sl_error_type = :p_error_type AND creation_date >= :p_from_date;

Because the descriptive columns are computed through IGF_AW_GEN.LOOKUP_DESC, queries returning large volumes can be more expensive than direct base-table access; filtering by loan number or error type is recommended. The view should be treated as a reporting and integration surface, not as an update target, since it is a non-key-preserved projection for modification purposes.