Search Results igs_ps_tch_resp_uoo_v

Overview

IGS_PS_TCH_RESP_UOO_V is a view within the Oracle E-Business Suite Student System (IGS) module, which carries the obsolete product designation in ETRM metadata for releases 12.1.1 and 12.2.2. The view was created to expose the teaching responsibility that applies to a given unit offering option. Within the IGS data model, teaching responsibility defines which organizational unit — typically an academic department or school — is accountable for delivering a specific unit offering, along with the percentage of that responsibility. Because responsibility can be assigned at the unit offering level and subsequently overridden at the more granular unit offering option level, the view consolidates both sources into a single, query-friendly result set. The resolution logic is conditional: for any unit offering option that has no corresponding override record, the view returns the standard teaching responsibility; where an override exists, the override takes precedence. This makes the view the authoritative reporting interface for teaching responsibility as it applies at the option level, insulating downstream consumers from the need to understand or replicate the override precedence rules.

Underlying Base Objects

The view is defined over three documented IGS base tables. The primary driving table is IGS_PS_UNIT_OFR_OPT (aliased UOO), which stores unit offering option records. Teaching responsibility data is drawn from IGS_PS_TCH_RESP (aliased TR), keyed to the unit by UNIT_CD and VERSION_NUMBER. Override data is drawn from IGS_PS_TCH_RESP_OVRD (aliased TRO), keyed by UOO_ID. The view text is implemented as a UNION ALL of two branches. The first branch joins IGS_PS_UNIT_OFR_OPT to IGS_PS_TCH_RESP and includes a NOT EXISTS subquery against IGS_PS_TCH_RESP_OVRD, ensuring that only options without an override fall through to the standard responsibility. The second branch joins IGS_PS_UNIT_OFR_OPT directly to IGS_PS_TCH_RESP_OVRD on UOO_ID, returning override rows. Because the two branches are mutually exclusive, UNION ALL introduces no duplicate risk. ETRM records no owner and no separately documented referenced base objects for the view; the base tables are evident from the view text itself.

Key Columns

• UNIT_CD — the unit (course) code to which the offering option belongs.
• VERSION_NUMBER — the unit version, used with UNIT_CD to align responsibility records.
• CAL_TYPE and CI_SEQUENCE_NUMBER — calendar type and calendar instance sequence identifying the teaching period.
• LOCATION_CD and UNIT_CLASS — delivery location and unit class attributes of the option.
• ORG_UNIT_CD — the organizational unit holding teaching responsibility; sourced from either the standard or override table.
• OU_START_DT — the start date associated with the responsibility assignment.
• UOO_ID — the unique identifier of the unit offering option; the pivot for override resolution.
• PERCENTAGE — the share of teaching responsibility attributed to the organizational unit.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns propagated from the unit offering option record.

Common Use Cases and Queries

Typical uses include validating responsibility coverage for offerings, reporting departmental teaching load by calendar instance, and feeding integration extracts that require a single resolved responsibility per option. A representative query lists responsibility for a unit version:

SELECT uoo_id, unit_cd, version_number, cal_type, location_cd, org_unit_cd, percentage
FROM igs_ps_tch_resp_uoo_v
WHERE unit_cd = :unit_cd AND version_number = :version_number;

Aggregated responsibility by organizational unit and calendar instance:

SELECT org_unit_cd, cal_type, ci_sequence_number, SUM(percentage) total_pct
FROM igs_ps_tch_resp_uoo_v
GROUP BY org_unit_cd, cal_type, ci_sequence_number;

Options lacking any resolved responsibility are best identified by driving from IGS_PS_UNIT_OFR_OPT with a NOT EXISTS against this view on UOO_ID. Because the view already encapsulates override precedence, consumers should query it rather than the base tables directly when a single authoritative responsibility value is required.