Search Results unit_section_sponsorship_id




Overview
Explore in AI Chat

Overview

The view IGS_PS_USEC_SPNSRSHP_V belongs to the IGS — Student System product family in Oracle E-Business Suite. Within the ETRM documentation set, this object is classified as Obsolete, and the implementation metadata explicitly states that it is not implemented in the documented database. This classification is significant: it indicates that the view was shipped or referenced in earlier releases of the Student System and has since been superseded, retired, or made unavailable in the environments covered by the ETRM 12.2.2 documentation.

Functionally, the view presents a denormalized, reporting-friendly projection of unit section sponsorship data. It joins sponsorship records held in IGS_PS_USEC_SPNSRSHP to institution/organization reference data in IGS_OR_INST_ORG_BASE_V in order to expose the human-readable organization name alongside the internal organization code. In EBS reporting and integration contexts, such views are typically created so that concurrent programs, Discoverer workbooks, OBIEE extracts, or third-party interfaces can retrieve sponsorship details without re-implementing the organization-name lookup join. The presence of a ROW_ID column and the full set of WHO audit columns confirms that the view is intended to behave like a transactional entity, supporting update-through-view or row identification in Forms-based tooling.

Underlying Base Objects

The view text identifies two referenced objects:

  • IGS_PS_USEC_SPNSRSHP (alias USS) — the primary table holding unit section sponsorship records, including the sponsorship identifier, the unit offering option identifier, the sponsoring organization code, and the sponsorship percentage.
  • IGS_OR_INST_ORG_BASE_V (alias OU) — an organization base view that supplies PARTY_NAME and PARTY_NUMBER for institution organizations.

The join condition is USS.ORGANIZATION_CODE = OU.PARTY_NUMBER, meaning the sponsorship row's stored organization code is resolved against the party number of the organization to yield the descriptive party name. The ETRM metadata records no separately documented base tables for this view ("Referenced base objects: none documented") and no owner, which is consistent with its obsolete classification. Where the view has been removed from the database, queries against it will raise an invalid-object error rather than returning no rows.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_PS_USEC_SPNSRSHP row, used for row identification and update-through-view.
  • UNIT_SECTION_SPONSORSHIP_ID — primary identifier of the sponsorship record.
  • UOO_ID — identifier of the unit offering option to which the sponsorship applies.
  • ORGANIZATION_CODE — the organization (party number) providing the sponsorship, as stored on the base table.
  • ORGANIZATION_DESCRIPTION — the organization's PARTY_NAME; this is the column most commonly targeted by users searching for organization descriptions, since it replaces the cryptic code with a business-meaningful label.
  • SPONSORSHIP_PERCENTAGE — the proportion of the unit section sponsored by the organization.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns describing record creation and last modification.

Common Use Cases and Queries

Typical usage centres on reporting sponsorship coverage for unit sections with readable organization names, and on extracts feeding student funding or billing processes. A representative query is:

SELECT unit_section_sponsorship_id, uoo_id, organization_code, organization_description, sponsorship_percentage FROM igs_ps_usec_spnsrship_v WHERE uoo_id = :p_uoo_id ORDER BY sponsorship_percentage DESC;

A second pattern retrieves all sponsorships attributable to a named organization:

SELECT uoo_id, organization_code, organization_description, sponsorship_percentage FROM igs_ps_usec_spnsrship_v WHERE organization_description LIKE :p_org_name || '%';

Because the object is documented as obsolete and not implemented, these statements should be validated against the target instance's data dictionary before being embedded in production code; where the view is absent, equivalent logic must be recreated by joining IGS_PS_USEC_SPNSRSHP directly to the appropriate organization base view.