Results for “base_id”

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

Overview

IGF_AP_HIST_TEXT_V is a seeded Oracle E-Business Suite view owned by the APPS schema and associated with the IGF (Financial Aid) product family. In both Release 12.1.1 and 12.2.2 the object is shipped with a VALID status, meaning it is a supported, upgradeable database object maintained by Oracle rather than a customer-defined artifact. The view presents historical correspondence text records that are no longer active. Its defining characteristic is the filter predicate WHERE ACTIVE LIKE 'N', which restricts the result set to rows that have been retired from active use within the Financial Aid correspondence framework.

Because it exposes inactive text only, the view functions as an archival or history-facing read layer. Reporting and integration consumers use it to retrieve superseded custom text associated with a given base identifier, most commonly for audit trails, reprint of previously issued letters, or reconciliation of correspondence content across processing cycles. It is not an operational view for driving live communications; it complements the active counterpart data held in the underlying text table.

Underlying Base Objects

The documented view text establishes that IGF_AP_HIST_TEXT_V is defined over a single base object: IGF_AP_ST_CORR_TEXT. The view is a projection with a filter, not a join. It selects a defined column list from that table and applies the ACTIVE LIKE 'N' restriction.

The base table name, IGF_AP_ST_CORR_TEXT, follows the IGF Student/Financial Aid naming convention and stores correspondence text entries. The view introduces one derived column, ROW_ID, produced by selecting the table's ROWID pseudocolumn and aliasing it. No other transformation, aggregation, grouping, or concatenation is applied. Consequently, the view inherits the table's partitioning, indexing, and row-level behavior, and query performance is governed by the availability and selectivity of indexes on the ACTIVE column and on BASE_ID within the base table.

The ETRM metadata lists no additional referenced base objects for this view, and none should be inferred; the single-table definition is authoritative.

Key Columns

• ROW_ID — The ROWID of the underlying IGF_AP_ST_CORR_TEXT row, aliased for convenience. Provides a unique physical row locator and is the only derived column in the view.
• BASE_ID — The identifier linking the inactive text record to its parent correspondence entity. This is the primary join key when correlating historical text to other Financial Aid data.
• CUSTOM_TEXT — The stored correspondence text content for the inactive record. This is the payload most consumers retrieve.
• RUN_DATE — The date associated with the run that produced the record. This is the column most frequently referenced in user searches and is central to chronological ordering and period-based retrieval of historical text.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO columns capturing the most recent modification user and timestamp.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, supporting session-level audit.

The ACTIVE column of the base table is not projected into the view, since the predicate fixes its value to 'N' for every returned row.

Common Use Cases and Queries

Typical scenarios include retrieving historical correspondence text for a specific base entity, ordering archived text chronologically by RUN_DATE, and auditing WHO columns to determine when text was superseded. The following query returns all inactive text for a given base identifier, most recent first:

• SELECT BASE_ID, CUSTOM_TEXT, RUN_DATE, LAST_UPDATE_DATE FROM apps.igf_ap_hist_text_v WHERE base_id = :p_base_id ORDER BY run_date DESC;
• SELECT BASE_ID, RUN_DATE, CUSTOM_TEXT FROM apps.igf_ap_hist_text_v WHERE run_date BETWEEN :p_from AND :p_to;
• SELECT ROW_ID, BASE_ID, CREATED_BY, LAST_UPDATED_BY FROM apps.igf_ap_hist_text_v WHERE base_id = :p_base_id;

Because filtering occurs on a low-cardinality flag, queries should always constrain on BASE_ID or RUN_DATE to avoid full scans of the base table.