Results for “relationship_code”

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

Overview

IGS_PE_FUND_SOURCE_V is a reporting and integration view within the Oracle E-Business Suite IGS (Student System) module. As documented in ETRM metadata for release 12.2.2, the IGS product line is flagged as obsolete, and this object explicitly carries the annotation "Not implemented in this database" within the supplied documentation. Practically, this means the view is a legacy artifact inherited from the historic Oracle Student System (or an equivalent student/party data model) and may not exist in a standard current EBS installation. Where it does exist, it presents the fund source details recorded against a person (party), denormalizing lookup meaning values onto the base rows for simpler consumption by forms, concurrent programs, and downstream interfaces. For a user searching on "fund_source_code," this view is the documented access path through which that code, together with its decoded meaning, is surfaced for a person's record.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view text reveals its definition. It is built on IGS_PE_FUND_SOURCE (aliased FS), the base table that stores the person fund source records, joined with two lookup sources through outer joins:

• IGS_LOOKUPS_VIEW (aliased L1) supplies the fund source meaning, filtered by LOOKUP_TYPE = 'PE_FUND_TYPE'.
• FND_LOOKUP_VALUES (aliased L2) supplies the relationship meaning, filtered by LOOKUP_TYPE = 'PARTY_RELATIONS_TYPE', VIEW_APPLICATION_ID = 222, the session LANGUAGE, and SECURITY_GROUP_ID = 0.

The outer-join notation (+) throughout means a fund source row is returned even when no matching lookup meaning exists, which is important for data completeness in reporting. Because the metadata records no base objects, the view should be treated as low-confidence for dependency analysis until validated against a live instance.

Key Columns

The view exposes the following columns, drawn from the underlying fund source table and the joined lookups:

• ROW_ID — the ROWID of the base fund source row, useful for direct row addressing.
• FUND_SOURCE_ID — primary identifier for the fund source record.
• PERSON_ID — the person/party to whom the fund source belongs.
• FUND_SOURCE_CODE — the lookup code driving the fund type, and the column most commonly queried.
• FUND_SOURCE_M — the decoded meaning of FUND_SOURCE_CODE from the PE_FUND_TYPE lookup.
• NAME — the name associated with the fund source entry.
• AMOUNT — the monetary value recorded against the fund source.
• RELATIONSHIP_CODE and RELATIONSHIP_M — the relationship lookup code and its decoded meaning.
• DOCUMENT_IND and NOTES — documentation flag and free-text notes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage involves retrieving decoded fund source information for a person, often for financial aid or sponsorship reporting. Because the lookup decodes are already embedded, queries can avoid additional joins:

• Retrieve all fund sources for a person:
  SELECT fund_source_code, fund_source_m, name, amount FROM igs_pe_fund_source_v WHERE person_id = :p_person_id;
• Filter by a specific fund type:
  SELECT person_id, name, amount FROM igs_pe_fund_source_v WHERE fund_source_code = :p_code AND amount > 0;
• Aggregate totals by decoded fund type for reporting:
  SELECT fund_source_m, COUNT(*), SUM(amount) FROM igs_pe_fund_source_v GROUP BY fund_source_m;
• Identify rows missing a valid lookup meaning:
  SELECT fund_source_code, COUNT(*) FROM igs_pe_fund_source_v WHERE fund_source_m IS NULL GROUP BY fund_source_code;

Before relying on any of these queries, confirm the view exists in the target instance and verify column availability, since the metadata states it is not implemented and the IGS module is obsolete. Where it is absent, equivalent data may reside in successor Student System tables.