Search Results igf_sl_reqd_fields_u2

Overview

IGF.IGF_SL_REQD_FIELDS is a seed data table in the Oracle E-Business Suite Financial Aid (IGF) product family. It stores the definition of fields that are mandatory for processing a student loan through the external loan processor interface. The table is the authoritative rule source used during the validation step, when the system confirms that a value has been supplied for every field transmitted to the external processor. Rows are organized by loan file specification version, loan type, transaction type, and processing type code, so that a single specification release can carry different mandatory-field rules for different loan scenarios.

The object resides in the APPS_TS_SEED tablespace, consistent with its role as reference or setup data that is seeded at implementation and refreshed when specification versions change. The metadata records no foreign keys, and the heuristic Data Vault classification is standalone. Under that classification, the table behaves as a self-contained satellite or reference set: its business meaning is carried entirely by its own descriptive columns rather than by links to parent entities.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• LRF_ID (NUMBER, 15) — Surrogate primary key, unique identifier for the rule row, enforced by IGF_SL_REQD_FIELDS_PK and by the unique index IGF_SL_REQD_FIELDS_U1.
• SPEC_VERSION (VARCHAR2, 30) — Loan file specification version. Direct Loan examples include 2001-2002 and 2002-2003; CommonLine examples include RELEASE-5 and RELEASE-6.
• FIELD_NAME (VARCHAR2, 28) — Database field name that is subject to validation.
• LOAN_TYPE (VARCHAR2, 30) — Loan category such as DLS, DLU, DLP, FLS, FLP, or ALT.
• TRANSACTION_TYPE (VARCHAR2, 10) — CommonLine transaction type; may be null for Direct Loan records.
• PRC_TYPE_CODE (VARCHAR2, 30) — Processing type for the loan, used primarily by CommonLine. Documented values include GO, GP, PG, DISB, PO, and NA. This is the column referenced by the search term prc_type_code.
• STATUS (VARCHAR2, 30) — Indicates whether the field is required, strongly recommended, or optional. Processing for the affected loan stops only when a value is missing for a field whose status is required.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit lineage.

The second unique index, IGF_SL_REQD_FIELDS_U2, covers SPEC_VERSION, FIELD_NAME, LOAN_TYPE, TRANSACTION_TYPE, and PRC_TYPE_CODE. That composite key is the natural business key: no two mandatory-field rules may be duplicated within the same specification, field, loan, transaction, and processing context.

Common Use Cases and Queries

The most frequent use case is diagnosing why a loan transmission failed validation. A support or integration query retrieves the rule rows that apply to a specific record so the missing field can be identified:

• Identify all required fields for a processing type: select FIELD_NAME, LOAN_TYPE, TRANSACTION_TYPE, STATUS from IGF_SL_REQD_FIELDS where PRC_TYPE_CODE = :prc_type_code and STATUS = 'required'.
• Resolve rules for a specification release: select SPEC_VERSION, FIELD_NAME, STATUS from IGF_SL_REQD_FIELDS where SPEC_VERSION = :spec_version and LOAN_TYPE = :loan_type.
• Compare releases: select SPEC_VERSION, FIELD_NAME, STATUS, PRC_TYPE_CODE from IGF_SL_REQD_FIELDS where FIELD_NAME = :field_name order by SPEC_VERSION, LOAN_TYPE, PRC_TYPE_CODE.
• Enumerate configuration for a given CommonLine processing type: select distinct LOAN_TYPE, TRANSACTION_TYPE, FIELD_NAME from IGF_SL_REQD_FIELDS where PRC_TYPE_CODE in ('GO','GP','PG','DISB','PO','NA') order by 1, 2, 3.

Reporting typically extracts the full rule matrix by specification version for review during an upgrade, or joins the rule set against actual interface payloads to confirm that every required field arrived populated.

Related Objects

The documented metadata identifies IGF_SL_REQD_FIELDS as standalone with no foreign key relationships. The following objects are the most relevant reference points in the same solution area:

• IGF_SL_REQD_FIELDS_PK and IGF_SL_REQD_FIELDS_U1 — the primary key and unique index on LRF_ID.
• IGF_SL_REQD_FIELDS_U2 — the composite unique index on SPEC_VERSION, FIELD_NAME, LOAN_TYPE, TRANSACTION_TYPE, and PRC_TYPE_CODE, which defines uniqueness for the validation rule set.
• Loan interface and validation packages in the IGF schema — the runtime consumers that read these rules before transmitting to the external loan processor; joins are made on SPEC_VERSION, LOAN_TYPE, TRANSACTION_TYPE, and PRC_TYPE_CODE rather than on LRF_ID.
• Specification definition tables in the IGF schema — reference SPEC_VERSION values shared with this table.
• CommonLine and Direct Loan transmission staging tables — compared against FIELD_NAME and STATUS to determine whether every required value is present.

Because the table is seed data, changes are normally applied through the standard setup or patching mechanisms rather than through direct DML.