Results for “fund_description”

50+ results




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

Overview

IGS_PE_FUND_EXCL_V is an Oracle E-Business Suite view owned by the APPS schema and delivered as part of the IGS (Student System) product family. It carries a VALID status in the ETRM repository for both 12.1.1 and 12.2.2. The view is described as "Person Hold Effect Fund Exclusion Details," which positions it as a reporting and integration surface over records that govern how person-level holds affect the exclusion of specific funds from encumbrance processing.

Functionally, the view denormalizes fund exclusion rows by joining each exclusion record to the fund catalog so that a human-readable fund description is available alongside the raw code. This makes it suitable for operational reporting, data validation, and downstream extracts where a fund code alone would be insufficient. Because the object is a view rather than a table, it holds no data of its own; it is a read-only projection assembled at query time from the underlying base objects.

Underlying Base Objects

The view is defined over two base objects. The driving table is IGS_PE_FUND_EXCL, aliased as E, which supplies the exclusion transaction rows. The lookup side is IGF_AW_FUND_CAT, aliased as L, which supplies the fund description. The join is an equality on FUND_CODE, expressed as E.FUND_CODE = L.FUND_CODE.

  • IGS_PE_FUND_EXCL — the primary base table holding person hold effect fund exclusion records. All key business columns except the description originate here.
  • IGF_AW_FUND_CAT — the fund catalog table, which the user searched for directly under the name "igf_aw_fund_cat." It contributes the DESCRIPTION column, projected as FUND_DESCRIPTION.

The join is an inner join, so an exclusion row is returned only when a matching fund code exists in the catalog. Both base objects are referenced through the APPS schema. The ETRM metadata records no additional referenced base objects beyond these two.

Key Columns

The view exposes the following columns, in the order defined by the view text:

Common Use Cases and Queries

The principal use case is reporting on which funds a given person is excluded from and for what period. Because the view already resolves the fund description, it is convenient for extracts and for BI Publisher or OBIEE style reporting without an extra lookup join.

  • Listing active exclusions for a person, filtered by expiry date.
  • Auditing the relationship between encumbrance types and excluded funds.
  • Joining to person and fund catalog reporting objects for name-level detail.
SELECT fund_excl_id,
       person_id,
       fund_code,
       fund_description,
       pfe_start_dt,
       expiry_dt
  FROM apps.igs_pe_fund_excl_v
 WHERE person_id = :p_person_id
   AND (expiry_dt IS NULL OR expiry_dt >= SYSDATE);

A second common pattern validates that every exclusion references a valid catalog entry:

SELECT a.fund_code, a.fund_description, COUNT(*) exclusions
  FROM apps.igs_pe_fund_excl_v a
 GROUP BY a.fund_code, a.fund_description
 ORDER BY exclusions DESC;

Because the view performs an inner join on FUND_CODE, exclusion rows whose fund code is absent from IGF_AW_FUND_CAT will not appear. Analysts seeking orphaned exclusions should therefore query IGS_PE_FUND_EXCL directly and use an outer join to the fund catalog.