Search Results reference_type_description




Overview
Explore in AI Chat

Overview

The IGS_PS_USEC_OCUR_REF_V view resides in the APPS schema of Oracle E-Business Suite and belongs to the IGS (Student System) product family. It presents reference information attached to unit section occurrences — the scheduled delivery instances of a teachable unit within a program offering. In the EBS data model, reference codes provide extensible classification of student system entities, allowing institutions to tag occurrences with institution-defined values such as delivery mode, attendance pattern, campus variant, or other site-specific identifiers.

The view exists primarily to denormalize a foreign-key lookup. The base occurrence reference table stores only the reference code type — a short, coded value — while the human-readable label for that type lives in the shared reference code type table. By joining the two, the view exposes REFERENCE_TYPE_DESCRIPTION, the descriptive text for the reference code type. This makes the view directly consumable in reports, concurrent programs, Discoverer workbooks, and integration extracts without requiring downstream developers to re-implement the join or resolve the code through a lookup query.

Underlying Base Objects

The view is defined over two base tables in the APPS schema:

  • IGS_PS_USEC_OCUR_REF — aliased UOR, the driving table holding unit section occurrence reference rows.
  • IGS_GE_REF_CD_TYPE — aliased RCT, the reference code type table providing the descriptive text.

The join is an equi-join between UOR.REFERENCE_CODE_TYPE and RCT.REFERENCE_CD_TYPE. Because the view is not documented as an outer join, records whose reference code type has no corresponding row in the reference code type table are excluded from the result set. The view is read-only, has no documented database triggers, and inherits standard EBS audit columns from the base table rather than maintaining its own. The view's ROW_ID column is the base table's native ROWID, exposed for tools that require a physical row identifier.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_PS_USEC_OCUR_REF row.
  • UNIT_SEC_OCCUR_REFERENCE_ID — primary key of the occurrence reference record.
  • UNIT_SECTION_OCCURRENCE_ID — foreign key to the unit section occurrence to which the reference applies.
  • REFERENCE_CODE_TYPE — the coded type identifier used to join to the reference code type table.
  • REFERENCE_TYPE_DESCRIPTION — the descriptive label for the reference code type; this is the column most frequently targeted by users searching for reference type text.
  • REFERENCE_CODE — the specific reference value assigned to the occurrence.
  • REFERENCE_CODE_DESCRIPTION — the descriptive text stored against the assigned reference code.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns carried through from the base table.

Common Use Cases and Queries

Typical usage includes occurrence-level reporting that must show descriptive reference text rather than codes, validation of reference assignments before term rollover, and extract feeds to timetabling or student records systems.

Retrieve all reference information for a single occurrence:

  • SELECT reference_code_type, reference_type_description, reference_code, reference_code_description FROM igs_ps_usec_ocur_ref_v WHERE unit_section_occurrence_id = :p_occurrence_id;

Find all occurrences carrying a given reference type:

  • SELECT unit_section_occurrence_id, reference_code, reference_code_description FROM igs_ps_usec_ocur_ref_v WHERE reference_type_description = :p_description;

Join the view to IGS_PS_USEC_OCCURRENCES when occurrence context such as start and end dates or location is also required. Because the underlying reference code type table is shared across the student system, filters on REFERENCE_TYPE_DESCRIPTION should always be paired with the relevant occurrence restriction to avoid returning rows from unrelated occurrences. As with all EBS views, query through the APPS schema or a synonym, and apply the standard security profile or operating unit predicates mandated by the institution's access model.