Search Results transfer_program_title




Overview
Explore in AI Chat

Overview

The APPS.IGSFV_STUDENT_PRG_TRANSFERS view is a Business Intelligence System (BIS) view registered in the E-Business Suite under the APPS schema, with FND Design Data identifier IGS.IGSFV_STUDENT_PRG_TRANSFERS. It belongs to the Oracle Student Systems (IGS) product family and exposes information about student program attempt transfers — that is, records describing when a student's program attempt has been transferred from one program to another. The view has a documented status of VALID and is classified explicitly as a Business Intelligence System view, meaning it is intended primarily for operational reporting, extract, and downstream analytical consumption rather than for OLTP transaction processing.

Because the view presents denormalized, human-readable attributes — person name, person number, program titles, and effective term descriptions — it is well suited for ad hoc queries, BI Publisher reports, OBIEE/OTBI-style extracts, and integration feeds where a user-friendly representation of transfer activity is required. The view carries the standard WHO audit columns, confirming it is a reporting projection layered over the underlying IGS base entities rather than a primary transactional table.

Underlying Base Objects

The ETRM documentation for this object does not enumerate the referenced base objects; the metadata lists "Referenced base objects: none documented." In practice, as a BIS view in the IGS schema, it is defined over the student program attempt transfer entity and its related person, program, and term calendar entities. The column set indicates that it joins the program attempt transfer record to person identification data (to derive PERSON_NUMBER and PERSON_NAME), to program definitions (to derive PROGRAM_TITLE and TRANSFER_PROGRAM_TITLE), and to term calendar instances (to derive EFFECTIVE_TERM_CAL_DESC). Because the base object list is not documented in the supplied metadata, consumers should treat the view as the supported reporting interface and avoid assuming a specific physical join path. Oracle supports querying the view through its documented columns; direct dependency on underlying tables is not part of the published contract.

Key Columns

Common Use Cases and Queries

Typical uses include auditing program transfers, reporting transfer volumes by term, and reconciling advanced-standing or discontinue-source decisions. A representative query filtering on the search term follows:

  • SELECT person_number, person_name, program_title, transfer_program_title, transfer_date FROM apps.igsfv_student_prg_transfers WHERE transfer_program_title IS NOT NULL;
  • SELECT effective_term_cal_desc, COUNT(*) FROM apps.igsfv_student_prg_transfers GROUP BY effective_term_cal_desc;