Search Results maximum_credits_for_repeat




Overview

IGSBV_HIGH_ED_UNIT_VERSIONS is a reporting view within the Oracle E-Business Suite Student System (IGS) product family, delivered as part of the higher education data model. In ETRM documentation it is classified under IGS – Student System (Obsolete), indicating that the object belongs to a legacy or de-supported track of the Oracle Student System application and is not actively implemented in current database instances. The ETRM metadata explicitly records the implementation status as "Not implemented in this database."

The view presents unit version details for higher education offerings, combining descriptive title information with lifecycle dates, credit point thresholds, enrolment load characteristics, and indicator flags that govern how a unit version may be used. Its role in EBS reporting and integration is to expose a denormalised, query-friendly projection of the underlying unit version entities so that downstream reports, interfaces, and extracts can retrieve unit-level academic and financial attributes without navigating the full normalised model. Because it is a view rather than a table, it functions purely as a read construct and carries no independent storage.

Underlying Base Objects

The ETRM entry for this view documents no referenced base objects; the "Referenced base objects" field is empty. Consequently, the exact table composition cannot be confirmed from the ETRM record alone. Based on the column set and standard IGS modelling conventions, the view is built over the higher education unit and unit version tables, with joins to unit title, organisational unit ownership, and load calendar constructs. Typical candidates in the IGS schema include the unit definition and unit version entities, unit title and subtitle sources, and calendar/load type reference data used to derive enrolment and offered load calendar types and sequence numbers. Because the documentation is incomplete, any dependency analysis should be validated against the deployed database's view text using the data dictionary rather than assumed.

Key Columns

The view exposes a broad column list, several of which carry aliased, report-friendly names:

Common Use Cases and Queries

Typical uses include unit catalogue reporting, curriculum workload analysis, enrolment capacity planning, and award/funding eligibility extracts. A representative query filtering on the laboratory workload column follows:

SELECT UNIT_CODE, VERSION_NUMBER, TITLE, WORK_LOAD_CP_LECTURE, WORK_LOAD_CP_LAB, LAB_CREDIT_POINTS, POINTS_MINIMUM, POINTS_MAXIMUM FROM IGSBV_HIGH_ED_UNIT_VERSIONS WHERE WORK_LOAD_CP_LAB > 0 AND UNIT_STATUS = 'ACTIVE' ORDER BY UNIT_CODE, VERSION_NUMBER;

A second pattern retrieves current version details by date validity:

SELECT UNIT_CODE, VERSION_NUMBER, START_DATE, END_DATE, CREDIT_POINT_DESCRIPTOR, ENROLLMENT_MINIMUM, ENROLLMENT_MAXIMUM FROM IGSBV_HIGH_ED_UNIT_VERSIONS WHERE SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);

Because the ETRM record states the view is not implemented in the reference database, these queries should be validated against the target instance before operational use.