Results for “igs_ps_unit_ofr_opt”

50+ results




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

Overview

The view IGS_PS_UNIT_OFR_OPT belongs to the IGS (Student System) product family within Oracle E-Business Suite, a module that is now classified as obsolete in the ETRM documentation set spanning releases 12.1.1 and 12.2.2. Functionally, the view exposes the record set behind the Unit Offering Option entity — the child-level, section-specific configuration of a unit offering that institutions use to control how a particular teaching instance is offered, enrolled into, graded, and reported. Each row represents a discrete offering option identified by the UOO_ID surrogate key, tied to a parent unit, version, calendar type, and location.

In reporting and integration terms, IGS_PS_UNIT_OFR_OPT served as a flattened, read-oriented projection suitable for enrollment rules, quota reporting, financial-aid flag analysis, and downstream extracts feeding student self-service or third-party schedulers. Because it collapses many offering-control attributes into a single denormalized row, it was commonly referenced by concurrent programs, discoverer reports, and interface staging logic rather than by transactional forms.

Underlying Base Objects

The ETRM metadata explicitly records that this object is not implemented in this database and lists no documented referenced base objects. The view text, however, is a straightforward SELECT ... FROM TAB projection, where the alias TAB resolves nominally to the underlying Unit Offering Option entity table, corresponding to the product's base entity carrying the UOO_ID primary key. No joins, unions, or derived expressions appear in the view text — every projected column maps one-to-one to a physical column on the base entity.

Because the object is obsolete and undocumented at the 12.2.2 level, DBAs should treat the base table association as historical. Verification should be performed against the installation's data dictionary (DBA_VIEWS, DBA_DEPENDENCIES) before relying on the mapping in a live environment.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which unit offerings allow self-service enrollment, reconciling quota against actual enrollment, and confirming grading-schema assignments ahead of results processing.

  • Inspect offering options for a given unit and version.
  • Report on open sections with remaining quota.
  • Audit financial-aid and self-service flags.
SELECT uoo.unit_cd,
       uoo.version_number,
       uoo.cal_type,
       uoo.location_cd,
       uoo.uoo_id,
       uoo.offered_ind,
       uoo.unit_section_status,
       uoo.unit_quota,
       uoo.enrollment_actual,
       uoo.ss_enrol_ind
  FROM igs_ps_unit_ofr_opt uoo
 WHERE uoo.unit_cd = :unit_cd
   AND uoo.offered_ind = 'Y'
 ORDER BY uoo.location_cd, uoo.uoo_id;

Given the obsolete classification, any production query should first confirm the view exists in the target schema; if absent, equivalent data must be sourced from the corresponding base entity or a supported successor view.