Search Results work_load_other




Overview
Explore in AI Chat

Overview

APPS.IGSBV_HIGH_ED_UNIT_VERSIONS is a reporting view within the Oracle E-Business Suite (EBS) Student Systems / Higher Education (IGS) product family. The "BV" prefix indicates that the object is a Business View, exposing a denormalized, business-friendly projection of the underlying unit (course/subject) version entity. In EBS 12.1.1 and 12.2.2 the view presents the versioned definition of a higher-education unit, combining identity attributes, lifecycle dates, credit and points information, workload and contact-hour metrics, enrolment controls, and financial-aid and enrolment-channel flags.

The view is intended primarily for reporting, enquiry, and integration use rather than transactional DML. Because it consolidates a large number of descriptive and control attributes of a unit version into a single projection, it is well suited to operational reports, extracts, and downstream interfaces that need to read unit version data without navigating multiple normalized tables. The presence of column aliases such as UNIT_CODE (from UNIT_CD), CONTACT_HOURS_OTHER (from CONTACT_HRS_OTHER), and BILLABLE_CREDIT_POINTS (from BILLING_HRS) demonstrates that the view renames legacy short-name columns into more readable business terms.

Underlying Base Objects

The view is defined by a single SELECT over the unit version entity. The ETRM metadata does not document explicit referenced base objects for this object, so the precise FROM clause and any join predicates cannot be confirmed from the supplied excerpt. In practice, a view of this name is built over the IGS unit version base table (the IGS_PS_UNIT / unit version family in the Student Systems data model), projecting columns that map one-to-one with the underlying attributes. Because the view exposes version-key columns (VERSION_NUMBER, START_DATE, REVIEW_DATE, EXPIRY_DATE, END_DATE), it is version-aware: each row represents a specific version of a unit, distinguished by version number and effective-date range.

Consumers should treat the view as read-only and note that any filters applied to the base entity — for example, institution or unit-status restrictions — may be enforced inside the view's definition or may not be applied at all. Where the view is used for referential lookups (for example, resolving COORD_PERSON_ID or OWNER_ORG_UNIT_CD), the caller is responsible for joining to the appropriate person or organization views.

Key Columns

Common Use Cases and Queries

Typical uses include unit-catalogue extracts, credit-point and workload audits, contact-hour reporting, and enrolment-eligibility checks. To surface contact hours by category for a unit version:

  • SELECT UNIT_CODE, VERSION_NUMBER, TITLE, CONTACT_HOURS_LECTURE, CONTACT_HOURS_LABORATORY, CONTACT_HOURS_OTHER, NON_SCHED_REQUIRED_HOURS FROM APPS.IGSBV_HIGH_ED_UNIT_VERSIONS WHERE UNIT_CODE = :unit_code;

To obtain the current effective version of a unit (filtering by the validity window):

  • SELECT UNIT_CODE, VERSION_NUMBER, START_DATE, END_DATE, UNIT_STATUS FROM APPS.IGSBV_HIGH_ED_UNIT_VERSIONS WHERE UNIT_CODE = :unit_code AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);

To review credit-point composition and override indicators:

  • SELECT UNIT_CODE, VERSION_NUMBER, ENROLLED_CREDIT_POINTS, ACHIEVABLE_CREDIT_POINTS, LECTURE_CREDIT_POINTS, LAB_CREDIT_POINTS, OTHER_CREDIT_POINTS, POINTS_OVERRIDE_INDICATOR FROM APPS.IGSBV_HIGH_ED_UNIT_VERSIONS WHERE POINTS_OVERRIDE_INDICATOR = 'Y';

Because the view is read-only and may carry no built-in institution or security predicate, callers should add appropriate WHERE clauses (unit code, version, date range, status, or owning org unit) to constrain results, and should join to person or organization views to resolve COORD_PERSON_ID and OWNER_ORG_UNIT_CD where display values are required.