Search Results edtr_id

Overview

IGF_SL_EDIT_REPORT_ALL is a transaction-level table in the IGF (Financial Aid) product module of Oracle E-Business Suite, owned by the IGF schema. As its description indicates, the table stores edit report information — the output of validation processing applied to student loan records before they are transmitted or reconciled with external loan servicers and the federal Common Origination and Disbursement (COD) system. Each row represents a single edit condition detected against a loan, capturing the qualifying loan number, the nature of the change, and the specific field and value that triggered the edit. The table is documented in both ETRM 12.1.1 and 12.2.2 as VALID, with a stable physical schema of 17 columns in 12.1.1.

From a Data Vault modeling perspective, ETRM's heuristic classification places this object as standalone, with no foreign-key relationships mined from the schema. In modeling terms, it behaves as a satellite-like record attached to a loan business key (LOAN_NUMBER), rather than a true hub or link. The absence of enforced FK relationships suggests the table is populated and consumed largely through concurrent programs and reporting rather than through normalized referential integrity.

Key Information Stored

The surrogate primary key is EDTR_ID, which is also the sole unique index (IGF_SL_EDIT_REPORT_ALL_U1) and therefore the business-key candidate documented for the table. Beyond the key, the most significant columns fall into three groups:

• Loan identifier: LOAN_NUMBER, the natural business key that ties an edit row back to a specific student loan.
• Edit classification: ORIG_CHG_CODE (the originating change code), SL_ERROR_TYPE (the category or severity of the error), SL_ERROR_CODE (the specific error identifier), and FIELD_NAME (the attribute within the loan record that failed validation). These four columns jointly describe what the edit is and where it occurred.
• Offending value: FIELD_VALUE, the value that triggered the edit, retained for diagnosis and correction.
• Standard EBS audit and context columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and ORG_ID. The REQUEST_ID and PROGRAM_* columns are particularly useful because they identify the concurrent request and program that generated the edit record, and ORG_ID supports multi-organization data segregation.

The presence of LAST_UPDATE_DATE, CREATION_DATE, and PROGRAM_UPDATE_DATE makes the table amenable to incremental extraction in data warehouse loads.

Common Use Cases and Queries

The primary use case is error analysis and remediation: financial aid administrators query the edit report to identify which loans failed validation, why, and what value caused the failure, then correct the source data and reprocess. A second use case is operational monitoring — counting edits by type, code, or loan to prioritize workload. A representative query is:

• SELECT LOAN_NUMBER, SL_ERROR_TYPE, SL_ERROR_CODE, FIELD_NAME, FIELD_VALUE FROM IGF.IGF_SL_EDIT_REPORT_ALL WHERE LOAN_NUMBER = :p_loan;
• SELECT SL_ERROR_CODE, COUNT(*) FROM IGF.IGF_SL_EDIT_REPORT_ALL GROUP BY SL_ERROR_CODE ORDER BY 2 DESC;
• SELECT * FROM IGF.IGF_SL_EDIT_REPORT_ALL WHERE REQUEST_ID = :p_request_id; to isolate output from a single concurrent run.
• For incremental reporting: SELECT ... WHERE LAST_UPDATE_DATE >= :last_run_date.

Related Objects

Because ETRM classifies this object as standalone, no enforced FK relationships are documented. Dependencies are therefore functional rather than declarative. The most significant related objects are the loan and borrower base tables in the IGF schema that supply LOAN_NUMBER, the concurrent program and request metadata tables (FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS) referenced by REQUEST_ID and PROGRAM_ID, and the standard EBS audit columns linking to FND_USER via CREATED_BY and LAST_UPDATED_BY. Reporting views over the IGF Financial Aid loan tables and the COD transmission processes that consume the corrected loan records are the principal downstream consumers of this edit information.