Search Results igf_aw_fisap_batch




Overview
Explore in AI Chat

Overview

IGF_AW_FISAP_BATCH is a Financial Aid application table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the IGF schema. It stores FISAP (Fiscal Operations Report and Application to Participate) batch details. FISAP is the annual reporting vehicle through which institutions of higher education report prior-year expenditures of federal campus-based aid funds (Federal Work-Study, Federal Supplemental Educational Opportunity Grant, and Federal Perkins Loan) and apply to participate in those programs for the coming award year. Each row in this table represents one batch — a discrete processing or reporting unit — through which FISAP data is grouped, tracked, and submitted.

Under a heuristic Data Vault classification derived from the foreign-key structure, this table is hub-leaning. It is referenced by IGF_AW_FISAP_REP via a BATCH_ID foreign key, meaning the batch acts as a parent entity whose details are captured by dependent records. In modeling terms, BATCH_ID functions as the hub business key, and the descriptive and audit columns behave as hub-adjacent attributes rather than a fully normalized satellite.

Key Information Stored

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

  • BATCH_ID — The surrogate primary key, enforced by IGF_AW_FISAP_BATCH_PK. It uniquely identifies each FISAP batch and is the join key to dependent tables. No alternate unique index is documented, so BATCH_ID is the only confirmed unique identifier.
  • CI_CAL_TYPE and CI_SEQUENCE_NUMBER — Calendar type and sequence number identifying the academic or reporting calendar instance the batch belongs to. In EBS, calendar type and sequence together form the composite calendar instance key used throughout student and financial aid modules.
  • DESCRIPTION — Free-text description of the batch, used for identification in forms and reports.
  • REPORTED_TIME_TXT — Textual representation of the time associated with the reported batch, typically capturing when the FISAP data was reported or extracted.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context columns. REQUEST_ID ties the batch to the concurrent request that generated or processed it; PROGRAM_APPLICATION_ID and PROGRAM_ID identify the owning application and program, and PROGRAM_UPDATE_DATE records the last programmatic update.

Common Use Cases and Queries

Typical use cases include identifying batches for a given reporting cycle, auditing which concurrent request produced a batch, and joining batch records to their report details. A representative query listing recent batches with their calendar context and audit trail:

  • SELECT b.batch_id, b.description, b.ci_cal_type, b.ci_sequence_number, b.reported_time_txt, b.creation_date, b.request_id FROM igf.igf_aw_fisap_batch b WHERE b.ci_cal_type = :cal_type AND b.ci_sequence_number = :seq_num ORDER BY b.creation_date DESC;
  • Auditing programmatic origins: query by REQUEST_ID against FND_CONCURRENT_REQUESTS to determine which job generated a batch and its completion status.
  • Reconciling batch-to-report counts: join to IGF_AW_FISAP_REP grouped by BATCH_ID to confirm that each batch carries the expected number of report rows.
  • Extract validation for FISAP submission: list batches whose REPORTED_TIME_TXT falls outside the expected filing window.

Related Objects

The documented relationships anchor this table to the following significant objects:

  • IGF_AW_FISAP_REP — The principal dependent table. Its BATCH_ID column is a foreign key to IGF_AW_FISAP_BATCH, so each report row is tied to a parent batch. This is the primary join path in almost all reporting queries.
  • IGF_AW_FISAP_BATCH_PK — The primary key constraint on BATCH_ID, guaranteeing batch uniqueness.
  • FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — Referenced indirectly through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for concurrent processing lineage.
  • FND_APPLICATION — Resolves PROGRAM_APPLICATION_ID to the owning application.
  • FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user identities for audit reporting.

The dependency chain is straightforward: batches are created as processing containers, report-level detail is written to IGF_AW_FISAP_REP, and the batch record supplies the calendar, descriptive, and audit context needed to manage and submit the FISAP filing.