Search Results import_record_type

Overview

IGF.IGF_AW_LI_AGR_INTS is a public interface (staging) table in the Oracle E-Business Suite Financial Aid / Student Aid product family (IGF), classified under the Lifecycle as active and spanning both Oracle EBS 12.1.1 and 12.2.2. It holds inbound aggregate award data — that is, per-student, per-fund aggregate award amounts — prior to validation and loading into the base award structures. Its FND Design Data identifier is IGF.IGF_AW_LI_AGR_INTS, and its display name is "Legacy - Aggregate Award Data Import Process." Records are written into this table by batch, marked with a status, and then consumed by a concurrent import program that moves them into the system of record.

The physical storage is the APPS_TS_INTERFACE tablespace, with PCTFREE 10. As a pure interface/staging object, it carries no foreign keys into business entities; the only documented relationship is a reference from its BATCH_NUM to IGF.IGF_AP_LI_BAT_INTS. In Data Vault terms, this table behaves like a satellite-leaning structure — a transactional staging object attached to a batch hub — rather than an independent hub or link. This classification is a heuristic modeling suggestion, not a documented EBS constraint.

Key Information Stored

The table is documented with 19 columns. The most significant ones for import processing are:

• AGRINT_ID — the primary key (IGF_AW_LI_AGR_INTS_PK, a unique NORMAL index), uniquely identifying each interface record. It is a surrogate key, not a business key.
• BATCH_NUM — batch identifier used to group the set of records processed together; documented as referencing IGF.IGF_AP_LI_BAT_INTS.
• PERSON_NUMBER — the student identifier to which the aggregate award applies.
• CI_ALTERNATE_CODE — the award year.
• FUND_CODE — the fund code under which the award is held.
• OFFERED_AMT, ACCEPTED_AMT, PAID_AMT — the offered, accepted, and paid monetary amounts for the aggregate award.
• IMPORT_STATUS_TYPE — the record's import status, governing whether it is pending, processed, or errored.
• IMPORT_RECORD_TYPE — determines whether the record updates the corresponding system record when found; documented permitted values are U or NULL.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program Who columns identifying the import run that touched the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who audit columns.

Users searching on import_record_type are typically troubleshooting why a batch did or did not overwrite an existing award; the U/NULL flag is the operative control for that behavior.

Common Use Cases and Queries

The primary scenario is diagnosing a stuck or partially processed import. A status inquiry filters by batch and status type:

• SELECT BATCH_NUM, AGRINT_ID, PERSON_NUMBER, FUND_CODE, IMPORT_STATUS_TYPE, IMPORT_RECORD_TYPE FROM IGF.IGF_AW_LI_AGR_INTS WHERE BATCH_NUM = :batch ORDER BY AGRINT_ID;

To isolate rows flagged for update against the system:

• SELECT AGRINT_ID, PERSON_NUMBER, FUND_CODE FROM IGF.IGF_AW_LI_AGR_INTS WHERE IMPORT_RECORD_TYPE = 'U' AND IMPORT_STATUS_TYPE IS NULL;

Amount reconciliation across offered, accepted, and paid values is a frequent reporting pattern, aggregated by fund and award year. Error handling centers on rows whose IMPORT_STATUS_TYPE indicates rejection after a run, which are corrected and re-submitted under the same or a new batch. Deleting processed batches against REQUEST_ID is a standard housekeeping operation, but only after the base award records are confirmed.

Related Objects

• IGF.IGF_AP_LI_BAT_INTS — the batch header interface table, joined on IGF_AW_LI_AGR_INTS.BATCH_NUM = IGF_AP_LI_BAT_INTS.BATCH_NUM. This is the sole documented foreign key relationship and the reference point for the satellite-leaning classification.
• IGF_AW_LI_AGR_INTS_PK — the unique index enforcing AGRINT_ID uniqueness on APPS_TS_INTERFACE.
• Base IGF award tables (the system records updated when IMPORT_RECORD_TYPE = 'U') — the eventual load targets of the import process.
• IGF aggregate award base and history tables — the persisted counterparts of the staged amounts.
• The Legacy Aggregate Award Data Import Process concurrent program — identified through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.
• FND concurrent request and log tables — used together with REQUEST_ID to trace run outcomes.

Because the interface table is batch-scoped and processed once, joins are typically made to the batch header and the concurrent program metadata rather than to person or fund master tables directly.