Results for “pe_fund_type”

10 results




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

Overview

APPS.IGS_PE_FUND_SOURCE_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the APPS schema and delivered within the Student Systems / Enterprise Territory and Records Management (ETRM) product family. The view consolidates records from the person fund source base table and enriches them with decoded lookup meanings so that fund source information is presented in a business-friendly, human-readable form rather than as raw codes.

This view is significant for users who search on the term pe_fund_type. The lookup type PE_FUND_TYPE is embedded directly in the view's join logic, meaning the FUND_SOURCE_M column returned by the view is precisely the decoded meaning of the fund type lookup. The view therefore serves as the canonical reporting surface for fund source categorization in student and person records, and it abstracts the underlying lookup mechanics so that reports and integrations do not need to replicate lookup joins.

Underlying Base Objects

The view is defined over three objects joined in a single SELECT statement:

All lookup joins are outer joins (indicated by the (+) operator), so a fund source row is still returned even when no matching lookup meaning exists. The L2 join additionally constrains VIEW_APPLICATION_ID = 222, LANGUAGE = USERENV('LANG'), and SECURITY_GROUP_ID = 0, ensuring language-sensitive and security-group-isolated lookup decoding. No additional base objects are documented in the ETRM metadata.

Key Columns

  • ROW_ID — the row identifier derived from the base table ROWID, useful for unique identification and updates.
  • FUND_SOURCE_ID — the primary key of the fund source record.
  • PERSON_ID — the person (party) associated with the fund source.
  • FUND_SOURCE_CODE — the coded value whose lookup type is PE_FUND_TYPE.
  • FUND_SOURCE_M — the decoded meaning of the fund source code, sourced from IGS_LOOKUPS_VIEW.
  • NAME — the descriptive name of the fund source.
  • AMOUNT — the monetary value associated with the fund source.
  • RELATIONSHIP_CODE / RELATIONSHIP_M — the relationship code and its decoded meaning from PARTY_RELATIONS_TYPE.
  • DOCUMENT_IND — a flag indicating whether supporting documentation is present.
  • NOTES — free-text notes attached to the record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage includes person fund source enquiries, financial aid and sponsorship reporting, and integration extracts where decoded fund type meanings are required. The following query retrieves all fund sources for a given person:

SELECT fund_source_id, person_id, fund_source_m, name, amount, relationship_m FROM apps.igs_pe_fund_source_v WHERE person_id = :p_person_id;

To report totals by decoded fund type (the pe_fund_type lookup):

SELECT fund_source_m, COUNT(*) record_count, SUM(amount) total_amount FROM apps.igs_pe_fund_source_v GROUP BY fund_source_m ORDER BY fund_source_m;

Because lookup decoding is performed within the view, developers should avoid re-joining to lookup tables and instead consume FUND_SOURCE_M and RELATIONSHIP_M directly. This reduces query complexity and ensures consistent, language-sensitive decoding across all reporting and integration scenarios.