Results for “sar_field_name”

7 results




Overview
Explore in AI Chat

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

Overview

IGF_FC_SAR_CD_MST is a configuration table within the Oracle E-Business Suite Financial Aid (IGF) module, which is documented as obsolete in the ETRM reference set. The table holds Student Aid Report (SAR) field numbers, providing the coded reference data that maps SAR field positions to lookup types used during financial aid processing. Each row is scoped to a specific award year, allowing the institution to maintain distinct SAR field definitions for each processing cycle without overwriting historical configurations.

Under the heuristic Data Vault classification derived from its foreign key structure, IGF_FC_SAR_CD_MST is modeled as a standalone object. Because it carries no outgoing foreign key dependencies to parent entities in the mined relationship data, it behaves as an independent reference or lookup table rather than a hub, link, or satellite within a conformed Data Vault model. In practice it functions as a code master: a stable, year-scoped catalog of SAR field definitions consumed by downstream aid processing logic.

Key Information Stored

The table is defined with 10 columns. The primary key, IGF_FC_SAR_CD_MST_PK, is a composite surrogate key comprising SYS_AWARD_YEAR and SAR_FIELD_NUMBER. A second unique index, IGF_FC_SAR_CD_MST_U2, covers SYS_AWARD_YEAR and SAR_FIELD_NAME, establishing an alternate business-key candidate that enforces uniqueness of field names within an award year.

  • SYS_AWARD_YEAR — the award year that scopes every configuration row; participates in both unique indexes and is the primary partitioning dimension for querying.
  • SAR_FIELD_NUMBER — the numeric identifier of the SAR field; part of the composite primary key.
  • SAR_FIELD_NAME — the descriptive name of the SAR field; the alternate unique key component alongside SYS_AWARD_YEAR.
  • SAR_LOOKUP_TYPE — the lookup type used to resolve or validate values associated with the SAR field.
  • CORRECT_TO_BLANK_FLAG — a control flag indicating whether the field should be corrected to a blank value under the applicable processing rules.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS auditable who-columns recording row creation and maintenance.

Common Use Cases and Queries

Typical usage centers on resolving SAR field metadata for a given award year, validating that a field number exists before loading aid data, and generating reference extracts for reconciliation. The following pattern retrieves the field catalog for a specific award year:

  • SELECT sar_field_number, sar_field_name, sar_lookup_type, correct_to_blank_flag FROM igf_fc_sar_cd_mst WHERE sys_award_year = :award_year ORDER BY sar_field_number;
  • Point lookup by primary key: WHERE sys_award_year = :yr AND sar_field_number = :field_no.
  • Alternate-key lookup by name: WHERE sys_award_year = :yr AND sar_field_name = :name, which leverages IGF_FC_SAR_CD_MST_U2.
  • Validation query to detect orphaned SAR field references in staged aid data by outer-joining the staging table to this master and filtering where the master key is null.

Reporting use cases include award-year comparisons of field definitions, audit reports surfacing rows whose LAST_UPDATE_DATE falls within a review window, and extracts feeding downstream SAR parsing routines.

Related Objects

Because the ETRM metadata classifies this table as standalone, it has no documented child foreign keys. Related objects are therefore identified through shared SAR field semantics and the award-year key rather than enforced referential constraints:

  • SAR processing and staging tables keyed by SYS_AWARD_YEAR and SAR_FIELD_NUMBER that consume these definitions.
  • FND lookup tables referenced by SAR_LOOKUP_TYPE, which supply the permitted values for each coded field.
  • Award-year control tables in IGF that define the valid SYS_AWARD_YEAR values.
  • Financial aid applicant and ISIR/SAR transaction tables that store the field values defined here.
  • Standard EBS audit and concurrent program objects that read and maintain this configuration.

Consumers should confirm that any such joins are validated against the actual deployment, since the absence of documented foreign keys means integrity is enforced by application logic rather than by the database.