Results for “igs_ps_tch_resp_ovrd_pk”

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

Overview

The IGS.IGS_PS_TCH_RESP_OVRD_ALL table is a core Student System (IGS) object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores teaching responsibility override records for a given unit offering option. Teaching responsibility in EBS defines the organizational units, academic staff, or cost centers that share accountability for delivering a unit (course or module) during a teaching period. Where the standard teaching responsibility distribution fails to reflect local agreements, an override row set is recorded here, and the percentages across a given unit offering option must total 100%. The table is owned by the IGS schema and is validated in the ETRM data dictionary.

In Data Vault modeling terms, the heuristic classification derived from the foreign key structure is a link. This is consistent with the table's role: it associates a unit offering option with organizational responsibility attributes rather than describing a single business entity like a hub. The UOO_ID foreign key to IGS_PS_UNIT_OFR_OPT_ALL links each override record to the offering option it qualifies, and the composite business key provides the grain.

Key Information Stored

The table contains 20 columns. The most significant are outlined below.

• UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER, LOCATION_CD, UNIT_CLASS — the composite business identifiers that, together with ORG_UNIT_CD and OU_START_DT, form the primary key IGS_PS_TCH_RESP_OVRD_PK and the unique index IGS_PS_TCH_RESP_OVRD_ALL_U1. They identify the unit, its version, calendar type, offering instance, location, and class.
• ORG_UNIT_CD — the organizational unit bearing teaching responsibility for the override row.
• OU_START_DT — the start date of the organizational unit assignment, providing validity for the override.
• UOO_ID — the surrogate foreign key referencing IGS_PS_UNIT_OFR_OPT_ALL, anchoring the record to a specific unit offering option.
• PERCENTAGE — the share of teaching responsibility allocated to the organizational unit; the sum across rows for a given offering option must equal 100%.
• ORG_ID — the Multi-Org operating unit context, supporting multi-org security and reporting.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns used for traceability of batch loads.

Common Use Cases and Queries

Typical scenarios include verifying that overrides total 100%, reporting organizational teaching load, and auditing responsibility changes for accreditation or funding returns. A validation query checks percentage totals per offering option:

SELECT uoo_id, SUM(percentage) AS total_pct
FROM   igs.igs_ps_tch_resp_ovrd_all
GROUP  BY uoo_id
HAVING SUM(percentage) != 100;

A reporting query joining to the offering option for descriptive context:

SELECT o.unit_cd, o.version_number, r.org_unit_cd, r.percentage
FROM   igs.igs_ps_tch_resp_ovrd_all r,
       igs.igs_ps_unit_ofr_opt_all o
WHERE  r.uoo_id = o.uoo_id
AND    r.org_id = :p_org_id;

These patterns support teaching workload analysis, cost allocation, and data-quality reconciliation between overrides and default responsibility records.

Related Objects

• IGS_PS_UNIT_OFR_OPT_ALL — parent offering option table, joined via UOO_ID and the composite unit/version/calendar keys.
• IGS_PS_UNIT_OFR_ALL — the unit offering header defining the delivery context.
• IGS_PS_UNIT_ALL — the unit (course) definition referenced by UNIT_CD and VERSION_NUMBER.
• IGS_PS_CAL_TYPE_ALL — the calendar type referenced by CAL_TYPE.
• IGS_PS_LOCATION_ALL — the location referenced by LOCATION_CD.
• IGS_PS_UNIT_CLASS_ALL — the unit class referenced by UNIT_CLASS.
• HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — the organizational unit context for ORG_UNIT_CD and ORG_ID.
• FND_CONCURRENT_REQUESTS — traceability for batch processes via REQUEST_ID.

These dependencies reflect the documented foreign key and business key relationships and should guide join design in custom reports and interfaces.