Search Results calendar_type_desc




Overview
Explore in AI Chat

Overview

IGSFV_STUDENT_UNIT_TRANSFERS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under the FND Design Data application IGS (Oracle Student Systems). The view describes the link between two units involved in a program transfer — specifically, it presents the relationship between the unit attempts a student completed under an original ("from") program and the new ("to") program attempt record into which those units were transferred. It is classified in ETRM as a view of type "Business Intelligence System view," which indicates it is purpose-built for reporting and analytical consumption rather than for transactional update. In EBS 12.1.1 and 12.2.2, BIS views of this family are the supported surface for institution-facing reporting on student records, shielding report authors from the underlying normalized tables and their many foreign keys. For the search term location_code_desc, this view is significant because it exposes LOCATION_CODE_DESC alongside LOCATION_CODE, allowing the description of the location to be reported directly without a separate lookup join.

Underlying Base Objects

The supplied ETRM metadata documents no referenced base objects for this view, and the object is listed as VALID with no subobject name. In practice, IGSFV_STUDENT_UNIT_TRANSFERS is defined over the Oracle Student Systems transfer and enrollment structures — principally the student unit attempt transfer entity and its associated person, program attempt, unit, calendar, location, and unit class reference tables. The view performs the joins and decode lookups (calendar type description, location code description, unit class description) that would otherwise have to be written manually, and it denormalizes the "from" and "to" program attempt identifiers into human-readable program code and title columns. Because the metadata records no base objects, implementations should not assume a specific dependency list; the view should be treated as an interface contract, and its columns referenced by name rather than by position.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include audit of credit transfers between programs, reconciliation of transferred unit attempts by calendar instance, and location-based analysis of where transferred units were taught. A representative query filtering on the location description is:

  • SELECT person_number, person_name, transfer_program_code, program_code, unit_code, transfer_date, location_code_desc FROM apps.igsfv_student_unit_transfers WHERE location_code_desc IS NOT NULL ORDER BY transfer_date DESC;
  • SELECT program_code, COUNT(*) transfers FROM apps.igsfv_student_unit_transfers WHERE calendar_type = :cal_type GROUP BY program_code;

Because the object is a BIS view owned by APPS, it should be queried with the APPS schema or via a synonym granted to the reporting user, and no DML should be attempted against it.