Results for “batch_num”

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

Overview

The IGF_AW_LI_AGR_INTS table is an interface (staging) table within the Oracle E-Business Suite Financial Aid (IGF) module. It serves the Awards and Disbursements processing area, holding aggregate financial aid data inbound to the institution's core financial aid engine. In Oracle EBS 12.1.1 and 12.2.2, such interface tables are populated by external processes, batch loads, or feeder systems and are subsequently consumed by concurrent programs that validate and transfer the rows into the permanent award/disbursement transaction tables.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a normative Oracle designation: inserted rows carry descriptive attributes tied to a business key and to a batch, are not independent business entities in their own right, and depend on a parent load (via BATCH_NUM) for context and referential integrity.

The table is owned by the IGF schema and is marked VALID in the data dictionary. It contains 19 documented columns and carries the primary key IGF_AW_LI_AGR_INTS_PK, defined on the AGRINT_ID column. The object name the user searched for, "igf_aw_li_agr_ints_pk", refers precisely to this unique index/constraint rather than to the table itself.

Key Information Stored

Among the 19 documented columns, the most significant for processing and analysis are:

• AGRINT_ID — The surrogate primary key; uniquely identifies each interface row.
• BATCH_NUM — Foreign key to IGF_AP_LI_BAT_INTS, grouping rows into a load batch and providing the link to the parent batch record.
• CI_ALTERNATE_CODE and PERSON_NUMBER — Business identifiers used to resolve the student or recipient (person) against master data.
• FUND_CODE — Identifies the aid fund or award program the amount relates to.
• OFFERED_AMT, ACCEPTED_AMT, PAID_AMT — The aggregate financial amounts for the offered, accepted, and disbursed/paid stages.
• IMPORT_STATUS_TYPE and IMPORT_RECORD_TYPE — Status and classification flags governing how each row is validated and processed.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — Linkage to the program/application context and last program-driven change.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID — Standard WHO columns and the concurrent request that created or updated the row.

AGRINT_ID is the sole documented unique index and therefore the primary surrogate key. No alternate unique index is documented; PERSON_NUMBER, CI_ALTERNATE_CODE, and BATCH_NUM behave as candidate business attributes but are not documented as unique keys.

Common Use Cases and Queries

Typical usage centers on loading, error triage, and reconciliation of batches. Analysts query pending or failed rows before running the transfer program:

• Monitoring import status: SELECT IMPORT_STATUS_TYPE, COUNT(*) FROM IGF_AW_LI_AGR_INTS GROUP BY IMPORT_STATUS_TYPE;
• Batch-level totals: SELECT BATCH_NUM, SUM(OFFERED_AMT), SUM(ACCEPTED_AMT), SUM(PAID_AMT) FROM IGF_AW_LI_AGR_INTS GROUP BY BATCH_NUM;
• Locating a single record by its primary key: SELECT * FROM IGF_AW_LI_AGR_INTS WHERE AGRINT_ID = :agrint_id;
• Tracing a batch's feeder rows: SELECT * FROM IGF_AW_LI_AGR_INTS WHERE BATCH_NUM = :batch_num;

These patterns support interfaces where amounts are aggregated before ingestion, making validation and reconciliation of BATCH_NUM, status flags, and person identifiers the primary operational concerns.

Related Objects

• IGF_AP_LI_BAT_INTS — Parent batch interface table referenced by the foreign key IGF_AW_LI_AGR_INTS.BATCH_NUM → IGF_AP_LI_BAT_INTS, providing batch-level context and control.
• IGF_AW_LI_AGR_INTS_PK — The documented unique index/constraint on AGRINT_ID.

The metadata documents only the parent batch table as a related object; further award and disbursement tables may reference this data but are not documented in the supplied ETRM excerpt.