Search Results rep_entity_id_txt




Overview
Explore in AI Chat

Overview

IGF_GR_REP_RS_V is a reporting view in the Oracle E-Business Suite (EBS) Grants Management (IGF) module, owned by the APPS schema. Its name — Grants Reporting Entity / Result Set — indicates its role as a deduplicated reference source for grant-related document and reporting entity identifiers. Rather than storing data itself, the view derives a distinct, whitespace-normalized list from the underlying transaction table and presents it for consumption by reporting, integration, and lookup surfaces.

The view exposes exactly two columns: DOCUMENT_ID_TXT and REP_ENTITY_ID_TXT. Both are textual identifiers, and both are passed through TRIM() before being returned. This design places the view squarely in the integration layer: it allows downstream components (concurrent programs, BI Publisher report data models, OAF pages, or external interfaces) to query a clean, deduplicated identifier set without re-implementing the trimming and grouping logic themselves.

Underlying Base Objects

According to the documented view text, IGF_GR_REP_RS_V is defined over a single base object: IGF_GR_COD_DTLS. The definition is:

SELECT TRIM(DOCUMENT_ID_TXT) DOCUMENT_ID_TXT, TRIM(REP_ENTITY_ID_TXT) REP_ENTITY_ID_TXT FROM IGF_GR_COD_DTLS GROUP BY TRIM(DOCUMENT_ID_TXT), TRIM(REP_ENTITY_ID_TXT)

Two structural facts follow from this definition. First, the view is a projection and aggregation over IGF_GR_COD_DTLS — it adds no joins and no external tables. Second, the GROUP BY on the trimmed expressions collapses duplicate identifier pairs into a single row, so the view returns a set of distinct (document, reporting entity) combinations rather than the full detail rows of the base table. No additional referenced base objects are documented in the ETRM 12.2.2 metadata.

Key Columns

  • DOCUMENT_ID_TXT — The trimmed document identifier. This is the column most commonly searched by name, and it is the primary lookup key exposed by the view. Because the source values are trimmed, leading and trailing whitespace variations in IGF_GR_COD_DTLS are normalized away, and records that differ only by padding are merged into one.
  • REP_ENTITY_ID_TXT — The trimmed reporting entity identifier. It pairs with DOCUMENT_ID_TXT to form the grouping grain of the view. The suffix “_TXT” confirms the values are stored and returned as character strings rather than numeric IDs.

No other columns, expressions, or derived attributes are exposed. The view’s contract is deliberately minimal: two normalized identifier columns, one distinct row per combination.

Common Use Cases and Queries

The view is typically used to populate selection lists, drive report parameters, or validate that a given document/entity pair exists in the grants data before processing. A typical retrieval of all distinct identifiers is:

SELECT document_id_txt, rep_entity_id_txt FROM apps.igf_gr_rep_rs_v;

A targeted lookup by document identifier — the pattern implied by the search term “document_id_txt” — would be:

SELECT document_id_txt, rep_entity_id_txt FROM apps.igf_gr_rep_rs_v WHERE document_id_txt = :p_document_id;

Because the view already deduplicates and trims, callers should not add their own DISTINCT or TRIM around these columns; doing so adds cost without changing the result. For reporting, the view is well suited as a parameter LOV source or as the driving query for a listing report of reporting entities associated with documents. When troubleshooting mismatches between expected and returned identifiers, query IGF_GR_COD_DTLS directly to inspect the pre-trim values, since the view will hide padding differences that may explain why a raw comparison in the base table failed while the view returns a match.