Search Results ou_description




Overview
Explore in AI Chat

Overview

IGS_OR_UNIT_FUNDSRC_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and belonging functionally to the Oracle Student System / Higher Education component within the ETRM (E-Business Tax and Related Modules) documentation set. The view joins organizational unit party records to funding source definitions, allowing reporting on which organizational units are associated with which funding sources. It exposes the organizational unit's description through the column alias OU_DESCRIPTION, which is the reason users searching for "ou_description" are routed to this object. Because the view presents a denormalized, read-only projection of party and funding source data, it is typically consumed by institution reporting, extract routines, and downstream integrations requiring a flattened set of organization unit and funding source attributes without directly querying the underlying TCA (Trading Community Architecture) and student system base tables. The view carries the standard audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) sourced from HZ_PARTIES, supporting conformance with common EBS auditing expectations.

Underlying Base Objects

The view is defined over three underlying objects referenced in its SQL text:

  • HZ_PARTIES HZ — The TCA party master table, supplying the party identifier, party number, party name, and the audit columns.
  • IGS_PE_HZ_PARTIES PEP — The student system extension table linking party records to organization unit attributes such as OSS_ORG_UNIT_CD, start/end dates, organization status, type, member type, and institution code, restricted by INST_ORG_IND = 'O'.
  • IGS_FI_FUND_SRC FS — The funding source definition table, supplying funding_source, description, government funding source indicator, and closed indicator.

The join is performed between HZ_PARTIES.PARTY_ID and IGS_PE_HZ_PARTIES.PARTY_ID, with the IMG_ORG_IND filter limiting results to organization-type parties. Although the ETRM metadata lists no formally documented base objects, the view text explicitly names these three tables, and they constitute its actual data lineage.

Key Columns

  • TCA_PARTY_NUMBER — The TCA party number, a unique identifier for the organization party.
  • ORG_UNIT_CD — The organizational unit code (OSS_ORG_UNIT_CD) identifying the unit.
  • OU_DESCRIPTION — The organization unit description, rendered from HZ_PARTIES.PARTY_NAME. This is the column most commonly requested by users searching for "ou_description".
  • OU_START_DT / OU_END_DT — Effective start and end dates for the organizational unit association.
  • OU_ORG_STATUS, OU_ORG_TYPE, OU_MEMBER_TYPE — Classification attributes describing the unit's status, organization type, and member type.
  • INSTITUTION_CD — The institution code to which the unit belongs.
  • FUNDING_SOURCE / FS_DESCRIPTION — The funding source code and its description.
  • GOVT_FUNDING_SOURCE / CLOSED_IND — Indicators for whether the source is governmental and whether it is closed.

Common Use Cases and Queries

Typical scenarios include producing institution-level reports of organization units and their funding sources, validating funding source assignments, and extracting data for downstream financial or student systems. A representative query retrieving the organizational unit description and associated funding sources is:

SELECT org_unit_cd,
       ou_description,
       funding_source,
       fs_description,
       govt_funding_source,
       closed_ind
FROM   apps.igs_or_unit_fundsrc_v
WHERE  institution_cd = :p_institution
AND    NVL(closed_ind,'N') = 'N';

Another common pattern is a lookup of a single organizational unit by its description:

SELECT org_unit_cd, ou_description, funding_source
FROM   apps.igs_or_unit_fundsrc_v
WHERE  ou_description = :p_ou_description;

Because the view is created in the APPS schema and references TCA and student system tables, access should be granted through standard EBS responsibility and menu configuration rather than direct grants, and queries should be limited by institution or organization unit to control result set size.