Results for “instructor_id”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_PS_USO_INSTRCTRS is a legacy Oracle EBS Student System (IGS) table that stores the assignment of instructors to unit section occurrences. In Oracle EBS 12.1.1 and 12.2.2, the IGS product family is classified as obsolete; the ETRM metadata explicitly notes "Not implemented in this database," meaning the table is retained for reference and historical/upgrade purposes rather than active delivery in current installations. Its role is to resolve the many-to-many relationship between an instructor (a party recorded in HZ_PARTIES) and a specific scheduled occurrence of a unit section (recorded in IGS_PS_USEC_OCCURS_ALL).

From a Data Vault modeling perspective, the FK structure suggests a link classification. The table carries no descriptive attributes beyond the two foreign keys and standard audit columns, so it functions as a pure association (link) between two business entities rather than a hub or a satellite. The unique constraint on UNIT_SECTION_OCCURRENCE_ID and INSTRUCTOR_ID enforces the natural business rule that a given instructor appears at most once per occurrence.

Key Information Stored

The documented physical schema comprises eight columns in the IGS schema. The most significant are:

  • USO_INSTRUCTOR_ID — the surrogate primary key (IGS_PS_USO_INSTRCTRS_PK). It uniquely identifies each instructor-to-occurrence assignment and is also a business-key candidate via unique index IGS_PS_USO_INSTRCTRS_U1.
  • UNIT_SECTION_OCCURRENCE_ID — foreign key to IGS_PS_USEC_OCCURS_ALL, identifying the scheduled occurrence being taught.
  • INSTRUCTOR_ID — foreign key to HZ_PARTIES, identifying the instructor party assigned to that occurrence.
  • CREATED_BY, CREATION_DATE — standard audit columns capturing who created the assignment and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns tracking the most recent modification and the login session responsible.

Two unique indexes are documented: IGS_PS_USO_INSTRCTRS_U1 on USO_INSTRUCTOR_ID (the surrogate key) and IGS_PS_USO_INSTRCTRS_U2 on the composite (UNIT_SECTION_OCCURRENCE_ID, INSTRUCTOR_ID), which is the true business-key candidate preventing duplicate instructor assignments. There are no descriptive or date-effectivity columns, confirming the link-style role.

Common Use Cases and Queries

The primary reporting use case is producing instructor timetables and workload reports by joining to occurrence and party data. A representative query pattern follows:

  • Instructor teaching load: join IGS_PS_USO_INSTRCTRS to IGS_PS_USEC_OCCURS_ALL on UNIT_SECTION_OCCURRENCE_ID to retrieve scheduled occurrences, and to HZ_PARTIES on INSTRUCTOR_ID to resolve instructor names.
  • Occurrence staffing checks: identify occurrences with zero or multiple instructors by aggregating counts grouped by UNIT_SECTION_OCCURRENCE_ID.
  • Instructor schedules: filter assignments by INSTRUCTOR_ID and correlate occurrence dates to build calendar or conflict reports.
  • Audit and data-quality scans: use CREATION_DATE and LAST_UPDATE_DATE to detect stale or recently modified assignments.

Because the module is obsolete, these queries are typically confined to historical extraction, migration validation, or reference during upgrade assessment rather than live operational reporting.

Related Objects

The following objects are directly referenced through the documented foreign keys and are the most significant for joining and dependency analysis:

  • IGS_PS_USEC_OCCURS_ALL — referenced by UNIT_SECTION_OCCURRENCE_ID; the parent occurrence table that defines the scheduled class instances.
  • HZ_PARTIES — referenced by INSTRUCTOR_ID; the Oracle Trading Community Architecture registry holding party (instructor) records.
  • IGS_PS_USO_INSTRCTRS_PK — the primary key constraint/index on USO_INSTRUCTOR_ID.
  • IGS_PS_USO_INSTRCTRS_U1 and IGS_PS_USO_INSTRCTRS_U2 — unique indexes enforcing surrogate and composite business keys.

Any dependent views, APIs, or reporting packages in the IGS schema that join to this table inherit its two FK relationships; because the metadata records the table as not implemented, such dependencies should be verified against the specific installation before use.