Search Results location_code_desc

Overview

IGSFV_STUDENT_UNIT_TRANSFERS is an APPS-owned, read-only view within the Oracle E-Business Suite Student System (IGS) product family. It exposes the link between two academic units that were involved in a program transfer, presenting a denormalized, human-readable projection of the transfer relationship recorded in the base transaction table. The view joins the transfer record to party, program version, unit version, unit offering option, calendar instance, location, and unit class reference tables, so that a single row returns the transferring student, the originating and receiving programs, the transferred unit, the unit version studied, and the calendar and location context in which the transfer occurred.

Because the view text is defined WITH READ ONLY, it is intended strictly for querying and reporting rather than for transactional data manipulation. In practice it serves as the reporting layer for institutional research, transfer articulation analysis, and student records inquiry, allowing functional users and integration developers to retrieve transfer credit relationships without reconstructing the underlying multi-table join. It is available in both 12.1.1 and 12.2.2, with the view definition and column aliases stable across those releases.

Underlying Base Objects

The ETRM metadata documents no separate base object list, but the view text identifies its constituent tables. The driving table is IGS_PS_STDNT_UNT_TRN, aliased SUT, which holds the student unit transfer transaction. Supporting joins derive descriptive attributes from:

• HZ_PARTIES (HP) — party number and party name for the student.
• IGS_EN_STDNT_PS_ATT_ALL (SCA1, SCA2) — student program attempt records, joined twice to associate the originating and transfer program versions.
• IGS_PS_VER_ALL (CRV1, CRV2) — program version titles for the two programs.
• IGS_EN_SU_ATTEMPT_ALL (SUA) — student unit attempt records, providing the unit code and version actually attempted.
• IGS_PS_UNIT_VER_ALL (UV) — unit version title.
• IGS_PS_UNIT_OFR_OPT_ALL (UOO) — unit offering option, supplying version number, location, and unit class.
• IGS_CA_INST_ALL (CI) — calendar instance start date, end date, and description.
• IGS_AD_LOCATION_ALL (LOC) and IGS_AS_UNIT_CLASS_ALL (UC) — location and unit class descriptions.

Joins are keyed on person, course, unit offering option (UOO_ID), calendar type and sequence, location code, and unit class, forming the composite key that uniquely contextualizes each transfer row.

Key Columns

The most significant exposed columns include:

• PERSON_IDENTIFIER / PERSON_NUMBER / PERSON_NAME — identify the student party.
• PROGRAM_CODE / PROGRAM_TITLE and TRANSFER_PROGRAM_CODE / TRANSFER_PROGRAM_TITLE — the originating and receiving programs.
• TRANSFER_DATE — the date the transfer was recorded.
• UNIT_CODE / UNIT_TITLE / UNIT_VERSION — the transferred unit and, critically for the user's interest in "unit_version," the version number of the unit offering option associated with the transfer.
• CALENDAR_TYPE / CAL_INST_SEQUENCE_NUMBER / CALENDAR_START_DATE / CALENDAR_END_DATE / CALENDAR_TYPE_DESC — the teaching calendar context.
• LOCATION_CODE / LOCATION_CODE_DESC / UNIT_CLASS / UNIT_CLASS_DESC / UNIT_SECTION_ID — delivery location and classification.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — audit columns mirrored from the base transaction.

Common Use Cases and Queries

Typical uses include transfer credit reporting, articulation audits, and reconciliation of student unit attempts against transferred units. A simple inquiry for a given student might read:

• SELECT person_number, person_name, program_code, transfer_program_code, unit_code, unit_version, transfer_date FROM igsfv_student_unit_transfers WHERE person_number = :p_party_number;
• SELECT unit_code, unit_version, COUNT(*) FROM igsfv_student_unit_transfers GROUP BY unit_code, unit_version ORDER BY 3 DESC;
• SELECT program_code, transfer_program_code, calendar_type, location_code FROM igsfv_student_unit_transfers WHERE transfer_date BETWEEN :start_dt AND :end_dt;

Because the view is read-only, all access should be through SELECT statements; no DML is permitted.