Search Results resp_err_value

Overview

IGF_SL_REJ_EDIT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered as VALID within the IGF (Financial Aid) product family. The view consolidates reject edit code definitions with the actual edit-processing results produced during Student Loan processing. It presents the descriptive metadata of each edit code — the message text, condition text, and fix text — joined to the individual outcomes recorded against that code for a given award year and record.

Functionally the view exposes the reject edit code details for all Edit Codes in the Financial Aid module. Its principal value lies in diagnosing why a loan or aid record failed validation: for each failure, the view carries both the human-readable explanation of the rule and the specific offending data element that triggered it. This makes it a natural source for operational reporting, error-resolution worklists, and downstream extracts. Because the view already resolves the join between the edit master and the edit results, it removes the need for report authors to reconstruct that relationship manually, and it can be queried directly through Oracle Reports, BI Publisher, OBIEE, or ad hoc SQL against the APPS schema.

Underlying Base Objects

Per the documented view text, IGF_SL_REJ_EDIT_V is defined over two base tables using an inner join:

• IGF_SL_ED_PRC_RSLTS — aliased ED; the edit processing results table holding the outcome rows for each evaluated edit.
• IGF_SL_FP_EDITS — aliased FP; the edit definition/master table holding the code, type, and explanatory text.

The join predicate is ED.RESP_ERR_CODE = FP.EDIT_CODE, meaning the responsible error code recorded on a result row is matched to the edit code in the edit master. The view metadata notes no separately documented referenced base objects, and the view text is the authoritative definition of these dependencies. Because the join is an equality (inner) join, result rows whose RESP_ERR_CODE has no corresponding entry in IGF_SL_FP_EDITS are not returned.

Key Columns

• SYS_AWD_YEAR — the system award year associated with the edit definition, used to scope rules to a processing cycle.
• EDIT_CODE — the edit code identifier from the edit master.
• EDIT_CODE_TYPE — classification of the edit code.
• EDIT_MESSAGE_TXT / EDIT_CONDITION_TXT / EDIT_FIX_TXT — the message presented on failure, the condition that triggers the edit, and the recommended correction.
• EDIT_ID / EDIT_REC_ID — identifiers for the edit and the specific result record.
• LEVEL_CODE — the level at which the edit applies.
• RESP_ERR_FIELD — the field responsible for the error.
• RESP_ERR_VALUE — the responsible error value, i.e., the field value that caused the reject. This is the column most commonly targeted when searching for "resp_err_value".
• REPORTED_VALUE — the value as originally reported on the incoming record, useful for comparison against RESP_ERR_VALUE.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context for the row.

Common Use Cases and Queries

A frequent scenario is locating all rejects where a particular field carries a specific offending value. The following query returns the edit explanation alongside the offending data:

• SELECT edit_code, edit_message_txt, resp_err_field, resp_err_value, reported_value FROM igf_sl_rej_edit_v WHERE resp_err_value IS NOT NULL;

To isolate failures for a single award year and edit type, filter on SYS_AWD_YEAR and EDIT_CODE_TYPE: SELECT * FROM igf_sl_rej_edit_v WHERE sys_awd_year = :year AND edit_code_type = :type;. To produce a remediation worklist, select EDIT_FIX_TXT together with RESP_ERR_FIELD and RESP_ERR_VALUE so that operations staff see both the defect and the prescribed fix. Because the view carries REQUEST_ID and PROGRAM_ID, it can also be joined to concurrent request history to trace which batch produced a given set of rejects. All queries should be issued against the APPS schema with appropriate grants.