Search Results api_2




Overview
Explore in AI Chat

Overview

IGF_AW_COA_HIST_V is a reporting view within the Oracle E-Business Suite Financial Aid module (product code IGF). Its documented description is "Cost of Attendance History View." The view exposes an auditable, denormalized record of changes made to Cost of Attendance (COA) records for financial aid applicants. Each row represents a single historical change event on a COA base record — capturing the operation performed, the affected item, the prior value, the new value, the date of the transaction, and the identity of the user who performed it.

The object belongs to the IGF - Financial Aid (Obsolete) product line. Notably, the ETRM metadata explicitly states "Not implemented in this database," indicating that in the documented environment the view is not instantiated. Its role in EBS reporting and integration is therefore historical and reference-oriented: it supports audit reporting, change tracking, and reconciliation of COA adjustments during the period in which the Financial Aid functionality (now superseded by Oracle Student Financial Planning / Campus Solutions equivalents) was actively deployed.

The user search term "tran_date" maps directly to the view's TRAN_DATE column, which is the primary date attribute for filtering and ordering history records.

Underlying Base Objects

The documented ETRM metadata lists no referenced base objects, but the embedded view text identifies the composition of the SQL definition. The view joins the following objects:

The joins are inner joins throughout, so history rows are only returned where the associated calendar instance, base record, user, lookup, party, and current SSN record all resolve.

Key Columns

  • ROW_ID — the ROWID of the underlying IGF_AW_COA_HIST row.
  • COAH_ID — the unique identifier of the COA history record.
  • BASE_ID — the financial aid base record identifier linking to IGF_AP_FA_BASE_REC.
  • PERSON_NUMBER, PERSON_NAME, SSN — party-identifying attributes; PERSON_NAME is concatenated as last name, first name.
  • TRAN_DATE — the date the COA change transaction occurred; the column most commonly used for date-range filtering.
  • ITEM_CODE — the COA item affected by the change.
  • CI_CAL_TYPE, CI_SEQUENCE_NUMBER — the award/CI calendar context of the base record.
  • LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE — the load calendar reference and its alternate code.
  • OPERATION_TXT, OPERATION_DESC — the raw operation code and its lookup meaning (for example, insert, update, delete).
  • OLD_VALUE, NEW_VALUE — the value before and after the change.
  • REQUEST_ID — the concurrent request identifier associated with the change.
  • LAST_UPDATED_BY, LAST_UPDATED_USER — the user ID and resolved FND_USER name of the person making the change.

Common Use Cases and Queries

Typical uses include audit reporting on COA adjustments, reconstructing the lifecycle of a specific item, tracing changes to a particular user or concurrent request, and point-in-time reconciliation of COA values. The following example filters history for a given date range, ordered by transaction date:

SELECT tran_date,
       person_number,
       person_name,
       item_code,
       operation_desc,
       old_value,
       new_value,
       last_updated_user
  FROM igf_aw_coa_hist_v
 WHERE tran_date BETWEEN :start_date AND :end_date
 ORDER BY tran_date, coah_id;

A second pattern traces all changes for a specific base record and COA item:

SELECT coah_id,
       tran_date,
       operation_txt,
       old_value,
       new_value,
       request_id
  FROM igf_aw_coa_hist_v
 WHERE base_id = :base_id
   AND item_code = :item_code
 ORDER BY tran_date;

Because the view is documented as not implemented, queries against it should be preceded by a check of the local object catalogue (ALL_VIEWS / ALL_OBJECTS) to confirm availability in the target environment.