Search Results atd_entity_id_txt




Overview
Explore in AI Chat

Overview

The view IGF_GR_REP_AS_V belongs to the IGF — Financial Aid product family within Oracle E-Business Suite. In both release 12.1.1 and 12.2.2, the IGF module is documented by ETRM as obsolete, and the metadata explicitly records that this view is not implemented in the database. It is therefore a legacy object that may appear in ETRM reference material, patch scripts, or migration inventories, but it will not resolve at runtime in a standard installation.

Functionally, the view exposes a deduplicated list of document identifiers and the entity references associated with them. Its naming convention (_GR_ and _AS_V) reflects a Grantor/Reporting context used by U.S. federal financial aid processing, where student award records must be reported against a Reporting Entity and an Awarding/Associated Entity. The view was intended to serve as a lightweight reporting and integration surface for extracting these triples without joining to the full transaction detail table.

The user search term rep_entity_id_txt corresponds directly to the second column of the view and is the reporting-entity identifier stored as character text.

Underlying Base Objects

The view is defined over a single base object: IGF_GR_COD_DTLS (Grantor COD Details). The ETRM metadata records no other referenced base objects. The defining SQL is a straightforward projection with aggregation:

  • Projection: three text columns are selected, each wrapped in TRIM() to remove padding whitespace.
  • Grouping: a GROUP BY clause on the same three trimmed expressions effectively performs an implicit distinct on the result set, eliminating duplicate document/entity combinations.
  • No joins, filters, or predicates are present, so the view returns all distinct combinations of the trimmed values found in the base table.

Because IGF_GR_COD_DTLS is itself part of the obsolete Financial Aid data model, the view should be treated as historical. Where the object does exist in an upgraded or customized environment, the base table is the authoritative source and any schema change on it will propagate directly to this view.

Key Columns

  • DOCUMENT_ID_TXT — Character identifier of the source document (typically a COD or reporting file identifier) associated with the record.
  • REP_ENTITY_ID_TXT — The reporting entity identifier as text. This is the column most frequently referenced in searches and is the primary linkage key for reporting-entity-level aggregation.
  • ATD_ENTITY_ID_TXT — The awarding (or associated/attending) entity identifier as text, distinguishing the institution or entity responsible for the award.

All three columns are character-typed despite representing identifiers, which is consistent with legacy ETRM integration files where COD identifiers were exchanged as fixed-width text and then trimmed on load.

Common Use Cases and Queries

The typical use case is auditing or reconciling the set of distinct reporting-entity identifiers captured in the grantor detail data. A representative query filters on the reporting entity and lists the associated documents:

SELECT document_id_txt,
       rep_entity_id_txt,
       atd_entity_id_txt
  FROM igf_gr_rep_as_v
 WHERE rep_entity_id_txt = :p_rep_entity
 ORDER BY document_id_txt;

To enumerate the distinct reporting entities present in the data:

SELECT DISTINCT rep_entity_id_txt
  FROM igf_gr_rep_as_v
 ORDER BY 1;

Because the view is documented as not implemented, any interface or report still referencing IGF_GR_REP_AS_V should be reviewed for removal or replacement before an upgrade to 12.2.2. Validation queries should first confirm object existence via ALL_VIEWS before attempting to select from it.