Results for “curriculum_description”

8 results




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

Overview

The APPS.IGSFV_HIGH_ED_UNIT_VERSIONS view is a reporting and integration object within the Oracle E-Business Suite Student System (IGS) product family. It exposes unit version records for higher education institutions, combining unit title information, lifecycle dates, credit point rules, and enrolment configuration into a single denormalized projection. The object type is VIEW and its status is VALID in the APPS schema, which confirms it is an Oracle-delivered, supported read-only interface rather than a customer-maintained object.

Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying unit version data at query time. This makes it suitable for concurrent program extracts, Discoverer or BI Publisher reports, and inbound/outbound interface staging where consumers require a flattened view of unit version attributes without navigating the normalized entity model directly. The view is documented for ETRM 12.1.1 and 12.2.2, and the implementation details below are drawn from the ETRM metadata supplied for this object.

Underlying Base Objects

The supplied ETRM metadata does not enumerate referenced base objects for this view, and the documented Referenced base objects list is empty. The view text nevertheless reveals a single driving source aliased as PSV, from which every projected column is derived. In the IGS schema the conventional source for unit version data is the IGS_PS_UNIT_VERSIONS (or equivalent unit version) entity, which stores version-level attributes such as UNIT_CD, VERSION_NUMBER, and the various indicator and points columns.

Consumers should treat the view as a one-row-per-unit-version projection over that base entity. No aggregation, join fan-out, or outer join is evident in the exposed column list, so cardinality is expected to match the underlying unit version table. Because the reference metadata documents no other base objects, any enrichment (for example, calendar type or sequence number descriptions referenced in the description) is either handled within the omitted portion of the view text or resolved by the calling report.

Key Columns

Common Use Cases and Queries

Typical scenarios include unit catalogue reporting, credit point auditing, and enrolment-rule validation. The following example retrieves active unit versions with their credit point parameters:

  • SELECT unit_code, version_number, title, unit_status, points_minimum, points_maximum, points_increment, enrolled_credit_points FROM apps.igsfv_high_ed_unit_versions WHERE unit_status = 'AC' AND sysdate BETWEEN start_date AND NVL(end_date, sysdate);
  • Enrolment threshold review: SELECT unit_code, version_number, enrollment_minimum, enrollment_maximum, enrollment_expected FROM apps.igsfv_high_ed_unit_versions WHERE enrollment_minimum IS NOT NULL;
  • Ownership and coordination extract: SELECT unit_code, version_number, owner_org_unit_cd, coord_person_id, approval_date FROM apps.igsfv_high_ed_unit_versions ORDER BY unit_code, version_number;

Because the view is read-only and delivered under APPS, reporting queries should always qualify it with the APPS schema and rely on the UNIT_CODE/VERSION_NUMBER pair as the logical key.