Search Results igf_gr_rep_rs_v

Overview

The IGF_GR_REP_RS_V view belongs to the IGF — Financial Aid product family within Oracle E-Business Suite, and is tagged in the ETRM repository (documented against 12.2.2) as Obsolete. In EBS 12.1.1 and 12.2.2 environments, the IGF module corresponds to the former Oracle Financial Aid / Grants subsystem, in which "GR" objects typically relate to grantor and grant-recipient reporting flows. The suffix _RS_V indicates a reporting (RS) view, whose purpose was to present a denormalised, presentation-ready projection of transactional detail rather than to store data.

The view therefore acted as a reporting facade: consuming rows from a single detail table and exposing trimmed, de-duplicated identifier columns for downstream reports, extracts, or integration feeds. Because it is documented as obsolete and is listed in the ETRM extract as "Not implemented in this database," it should be treated as a legacy artefact. In practice this means that on most 12.1.1 / 12.2.2 instances the view will not exist, or will exist only where historical Financial Aid objects were retained. Developers who search for igf_gr_rep_rs_v today are usually investigating a residual reference in custom code, a report definition, or a data-migration script, rather than a component that is actively maintained by Oracle.

Underlying Base Objects

The documented ETRM metadata records no referenced base objects for this view. The view text, however, makes the dependency explicit: it selects exclusively from IGF_GR_COD_DTLS (grant/grantor coding details). No other table, synonym, or intermediate view participates in the definition, making the relationship one-to-one at the structural level — every row returned by the view is derived from one or more rows of IGF_GR_COD_DTLS that survive the grouping.

The absence of documented base objects in ETRM is consistent with the object's obsolete status: metadata capture for de-supported Financial Aid objects was frequently incomplete or deliberately stripped. For practical dependency analysis in a live instance, the relationship to IGF_GR_COD_DTLS is authoritative, since it is stated verbatim in the view's SELECT text.

Key Columns

• DOCUMENT_ID_TXT — The document identifier held on IGF_GR_COD_DTLS, surfaced as text. The view applies TRIM() to remove leading and trailing whitespace, ensuring that identifiers padded in the base table compare cleanly. This is typically the key used to link the document to a report or extract run.
• REP_ENTITY_ID_TXT — The reporting entity identifier, also sourced as text and trimmed. In Financial Aid reporting, this generally denotes the organisational entity (institution, grantor, or reporting unit) responsible for the document.

Both columns are character-typed. The view performs no data-type conversion beyond trimming, so any numeric or coded semantics present in the base columns are preserved as text. Because the view groups by both trimmed columns, it returns the distinct set of document-and-entity pairs available in the detail table.

Common Use Cases and Queries

The historical use case for this view was to feed reporting or extract processes that needed a clean, de-duplicated list of document/entity pairings without scanning the full grant coding detail table. A representative query follows:

• SELECT document_id_txt, rep_entity_id_txt FROM igf_gr_rep_rs_v ORDER BY document_id_txt;
• SELECT COUNT(*) FROM igf_gr_rep_rs_v; — used to reconcile the distinct pair count against source detail.
• SELECT r.rep_entity_id_txt, COUNT(*) FROM igf_gr_rep_rs_v r GROUP BY r.rep_entity_id_txt; — an entity-level document tally for exception reporting.

Because the object is obsolete, these statements are only valid where the view has been preserved. For 12.1.1 / 12.2.2 support and upgrade work, the recommended approach is to replace references to IGF_GR_REP_RS_V with a direct, equivalent query against IGF_GR_COD_DTLS using GROUP BY TRIM(...), thereby removing dependency on an unsupported view.