Results for “anon_unit_grading_ind”

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

Overview

IGS_PS_UNIT_VER_V is a view within the Oracle E-Business Suite Student System (IGS) product family, which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. The view exposes version-level records for academic units of study — the individual teaching and assessment components that make up a program or course offering. Each row represents a distinct version of a unit, keyed by the combination of unit code, version number, and the effective start date of that version.

Because the IGS product line is no longer actively implemented in current EBS environments, the view is typically encountered only in legacy reporting extracts, historical data migrations, or archived student-record queries. The ETRM metadata notes that the object is "Not implemented in this database," confirming that it is not present in standard 12.1.1 or 12.2.2 installations unless the Student System was separately licensed and deployed. Where it exists, the view serves as a denormalized presentation layer, joining the base unit-version table to lookup and party tables so that report writers and integration interfaces can retrieve descriptive values rather than raw codes.

Underlying Base Objects

The view text references a primary alias PUV, which corresponds to the base unit-version table (IGS_PS_UNIT_VER), and several joined objects. The LK alias supplies lookup meanings, notably CPD_DESCRIPTION derived from the credit point descriptor code. The PE alias joins to a party table (via COORD_PERSON_ID) to resolve PERSON_NUMBER. The UVS alias supplies subtitle text. The ETRM record documents no formally registered base objects, and the view is flagged as obsolete, so dependency tracing through ETRM is unreliable. Practitioners should confirm the actual base tables in the data dictionary (ALL_VIEWS, ALL_DEPENDENCIES) before building on the view.

Key Columns

• UNIT_CD, VERSION_NUMBER, START_DT, END_DT, REVIEW_DT, EXPIRY_DT — version identity and effective-dating controls.
• OWNER_ORG_UNIT_CD and OWNER_OU_START_DT — identify the owning organizational unit and the date that ownership became effective. The user's search term, owner_ou_start_dt, maps directly to the OWNER_OU_START_DT column; it is the effective-date key required to join the owning organizational unit to its own versioned record.
• TITLE, SHORT_TITLE, ABBREVIATION, SUBTITLE — descriptive naming attributes.
• UNIT_STATUS, UNIT_LEVEL, CREDIT_POINT_DESCRIPTOR/CPD_DESCRIPTION — classification and status values.
• COORD_PERSON_ID/PERSON_NUMBER — coordinator identification.
• Credit and workload columns: ENROLLED_CREDIT_POINTS, ACHIEVABLE_CREDIT_POINTS, LECTURE_CREDIT_POINTS, LAB_CREDIT_POINTS, OTHER_CREDIT_POINTS, BILLING_CREDIT_POINTS, CLOCK_HOURS.
• Indicator flags such as RESEARCH_UNIT_IND, INDUSTRIAL_IND, PRACTICAL_IND, REPEATABLE_IND, ASSESSABLE_IND.

Common Use Cases and Queries

Typical uses include producing unit catalog listings, validating version effective dates, and reconciling ownership against organizational-unit records. A representative query retrieving current versions owned by a specific organizational unit might read:

SELECT unit_cd, version_number, title, unit_status, owner_org_unit_cd, owner_ou_start_dt, start_dt FROM igs_ps_unit_ver_v WHERE owner_org_unit_cd = :org_unit AND TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, TRUNC(SYSDATE));

Analysts frequently join back to the owner organizational-unit view using both owner_org_unit_cd and owner_ou_start_dt to resolve the correct dated organizational record. Given the obsolete status, any query should be treated as read-only and validated against the installed schema before reliance in production reporting or integration.