Results for “reject_code”

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

Overview

IGF_AP_REJECT_CD_ALL is a reference configuration table within the Oracle E-Business Suite Financial Aid (IGF) module, which Oracle has classified as obsolete in both Release 12.1.1 and 12.2.2. The table stores ISIR (Institutional Student Information Record) reject codes and their associated human-readable descriptions. In the U.S. federal student aid process, the Central Processing System assigns reject codes to ISIRs that contain conflicting, missing, or unverifiable data; institutions must resolve each reject condition before awarding or disbursing Title IV funds. This table serves as the lookup that maps those numeric or alphanumeric reject codes to descriptive text and to the corrective action the financial aid office should perform.

The metadata records that the object is not implemented in the current database, meaning the table may exist structurally in some installations while remaining unused, or be absent entirely depending on the IGF patch level. From a dimensional modeling perspective, the mined key structure suggests classifying this object as a hub candidate: it carries a stable, business-defined composite identifier with descriptive attributes attached. Because the metadata lists no foreign-key dependencies, the Data Vault heuristic classification is standalone, so no dependent link or satellite tables are implied.

Key Information Stored

The documented physical schema contains ten columns owned by the IGF schema. The most significant are:

• SYS_AWARD_YEAR — the award year for which the reject code definition is valid. Reject code definitions are year-sensitive because the federal ISIR edit rules and code assignments change annually.
• REJECT_CODE — the code value itself, as transmitted on the ISIR (for example, codes indicating conflicting SSN, citizenship, or grade level data).
• REJECT_REASON_DESC — the descriptive text explaining the condition that triggered the reject.
• ACTION_DESC — the prescribed resolution or follow-up action the aid administrator must take.
• DISCONTINUED_FLAG — indicates whether the code is no longer active for the award year, supporting history retention without deletion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage for row creation and modification.

The surrogate primary key is defined by the unique index IGF_AP_ISIR_REJECT_REASONS_PK, which covers the composite business key (SYS_AWARD_YEAR, REJECT_CODE). This composite uniquely identifies one code definition per award year and is the natural join path for any dependent ISIR processing logic.

Common Use Cases and Queries

Typical usage centers on decoding reject codes during ISIR load and on reference reporting. A verification query retrieves the description and action text for a given code and year:

SELECT reject_code, reject_reason_desc, action_desc, discontinued_flag FROM igf_ap_reject_cd_all WHERE sys_award_year = :award_year AND reject_code = :code;

Reporting patterns include listing all active codes for the current award year (WHERE discontinued_flag = 'N'), comparing code definitions across two award years to detect newly introduced or retired codes, and joining reject codes returned by ISIR import processes to produce exception worklists for aid counselors. Because the table is small and static, it is a common candidate for caching in the mid-tier during batch ISIR validation.

Related Objects

The ETRM metadata documents no foreign-key relationships, consistent with its standalone classification. In practice, the objects most closely associated with this reference table are the ISIR and student aid processing entities that consume reject codes, including the ISIR data tables and message/comment tables within the IGF schema such as IGF_AP_ISIR_* and IGF_AP_* student aid runtime structures, along with the ISIR import concurrent programs and the Financial Aid ISIR processing APIs. Because no validated joins are documented in the source metadata, join columns should be confirmed against the installation schema before use; the reliable, documented access path is the composite key (SYS_AWARD_YEAR, REJECT_CODE) on IGF_AP_ISIR_REJECT_REASONS_PK.