Results for “uv_version_number”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_PS_ANL_LOAD_U_LN is a Student System (IGS) table that associates an individual unit offering with an annual load figure, enabling the calculation of Equivalent Full-Time Student Units (EFTSU). The entity captures the linkage between a unit version and the annual load record for a specific program (course) version and year. For example, a unit may be attached to the load defined for the first year of a program, allowing the institution to weight or attribute that unit's contribution to the annual EFTSU total. The product module is flagged as obsolete within Oracle EBS 12.1.1 and 12.2.2, and the documentation notes that the object is not implemented in this database, meaning it persists in the ETRM data model inventory primarily for historical, upgrade, or migration reference rather than active use.

Mined from its foreign key structure, the heuristic Data Vault classification for this object is link. This suggests the table behaves as an associative (many-to-many resolution) entity, connecting two independent hubs: the annual load hub (IGS_PS_ANL_LOAD) and the unit version hub (IGS_PS_UNIT_VER_ALL). It carries no descriptive payload beyond standard WHO audit columns, which reinforces the link interpretation.

Key Information Stored

The table's documented physical schema contains 11 columns. Its business identity is expressed through a six-column composite that also forms the primary key constraint, IGS_PS_ANL_LOAD_U_LN_PK, and the unique index IGS_PS_ANL_LOAD_U_LN_U1.

There is no single-column surrogate key; identity is entirely composite. The six business-key columns appear in both the primary key and the unique index, so the documented surrogate/business-key distinction collapses here — the PK is the business key.

Common Use Cases and Queries

Because the table is obsolete and unimplemented, its principal uses are data lineage tracing, legacy reporting reconstruction, and upgrade assessment. A typical query joins the unit link to its parent load and unit version records to reproduce EFTSU attribution for a given program, year, and unit:

  • Annual load breakdown: SELECT l.course_cd, l.yr_num, u.unit_cd, u.uv_version_number FROM igs_ps_anl_load_u_ln u, igs_ps_anl_load l, igs_ps_unit_ver_all v WHERE u.course_cd = l.course_cd AND u.crv_version_number = l.crv_version_number AND u.yr_num = l.yr_num AND u.effective_start_dt = l.effective_start_dt AND u.unit_cd = v.unit_cd AND u.uv_version_number = v.uv_version_number.
  • EFTSU contribution reporting: aggregate linked units per course/year to reconcile computed EFTSU totals against load figures.
  • Migration validation: confirm that every legacy unit-to-load association resolves to a valid unit version before converting data into replacement structures.

Effective-dated filtering on EFFECTIVE_START_DT is essential to obtain the correct point-in-time association.

Related Objects

The most significant objects connected to this table are its two referenced parents, supplemented by related student-system reference tables.

  • IGS_PS_ANL_LOAD — parent annual load hub, joined on COURSE_CD, CRV_VERSION_NUMBER, YR_NUM, and EFFECTIVE_START_DT.
  • IGS_PS_UNIT_VER_ALL — unit version hub, joined on UNIT_CD and UV_VERSION_NUMBER.
  • IGS_PS_ANL_LOAD_U_LN_PK — the primary key constraint enforcing composite uniqueness.
  • IGS_PS_ANL_LOAD_U_LN_U1 — the unique index supporting the composite business key.
  • IGS_PS_ANL_LOAD_U_LN related audit-trail references via standard WHO columns.

Consumers should treat the table as a deprecation candidate and consult ETRM guidance for the recommended replacement when building new integrations.