Search Results batch_year_num

Overview

IGF.IGF_AP_LI_ISIR_ACT_INTS is a legacy Oracle EBS interface table owned by the IGF (Financial Aid) product schema. Its FND display name is "Legacy - Make ISIR Active Process," and it operates in the BUSINESS_ENTITY IGF_ISIR category within the APPS_TS_INTERFACE tablespace. The table serves a single, tightly scoped purpose: it holds staged records that instruct the financial aid subsystem which Institutional Student Information Record (ISIR) has to be made the Active ISIR for a given student and award year. It is a transient, process-oriented staging area rather than a persistent transactional store; rows are loaded, consumed by a concurrent program, and status-tracked through import processing.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is satellite-leaning. In modeling terms, it is best understood as a satellite attached to a batch (hub/link) keyed by BATCH_NUM, carrying descriptive attributes about the batch's individual ISIR activation requests. Its dependency footprint confirms this: it references IGF_AP_LI_BAT_INTS through BATCH_NUM, and the ETRM record shows no downstream objects referencing it, consistent with a terminal staging table.

Key Information Stored

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

• ACTINT_ID — numeric surrogate primary key defined by the unique index IGF_AP_LI_ISIR_ACT_INTS_PK. It uniquely identifies each interface record and is the only documented business-key candidate (unique index).
• BATCH_NUM — batch identifier used to group records for processing; foreign key to IGF_AP_LI_BAT_INTS. This is the primary business grouping attribute.
• TRANSACTION_NUM_TXT — free-text transaction number for the ISIR, the column most commonly resolved from the user's search term "transaction_num_txt."
• PERSON_NUMBER — student identifier linking the activation request to the person.
• CI_ALTERNATE_CODE — award year code for the ISIR.
• BATCH_YEAR_NUM — numeric batch year associated with the request.
• IMPORT_STATUS_TYPE — processing/import status of each record, the key control column for monitoring load and consumption.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Concurrent program auditing columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, which identify the submission that populated or processed the row.

The distinction to observe: ACTINT_ID is the surrogate key, BATCH_NUM is the foreign-key business reference, and no composite business unique key beyond the primary key is documented.

Common Use Cases and Queries

Typical usage centers on monitoring the Make ISIR Active process, troubleshooting records that remain unprocessed, and confirming which transaction was submitted for activation.

A standard monitoring query retrieves pending work by batch and status:

SELECT BATCH_NUM, ACTINT_ID, PERSON_NUMBER,
       TRANSACTION_NUM_TXT, CI_ALTERNATE_CODE, IMPORT_STATUS_TYPE
FROM   IGF.IGF_AP_LI_ISIR_ACT_INTS
WHERE  IMPORT_STATUS_TYPE = 'PENDING'
ORDER BY BATCH_NUM, ACTINT_ID;

A second common pattern joins to the batch table to reconcile activation requests against their parent batch:

SELECT i.BATCH_NUM, i.PERSON_NUMBER, i.TRANSACTION_NUM_TXT,
       i.IMPORT_STATUS_TYPE, b.*
FROM   IGF.IGF_AP_LI_ISIR_ACT_INTS i,
       IGF.IGF_AP_LI_BAT_INTS    b
WHERE  i.BATCH_NUM = b.BATCH_NUM;

Reporting use cases include award-year activation counts by status, per-student transaction lookups by PERSON_NUMBER, and audit trails keyed on REQUEST_ID.

Related Objects

The documented dependency set is narrow. The significant related object is the foreign-key parent:

• IGF.IGF_AP_LI_BAT_INTS — batch master; joined via IGF_AP_LI_ISIR_ACT_INTS.BATCH_NUM = IGF_AP_LI_BAT_INTS.BATCH_NUM. This is the only documented FK relationship.

Related business entities in the IGF financial aid model include the ISIR and person/batch tables referenced indirectly through PERSON_NUMBER, CI_ALTERNATE_CODE, and BATCH_YEAR_NUM, though no additional FK constraints are documented in the ETRM record for this object.