Results for “igs_as_usec_sessns”

33 results




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

Overview

IGS_AS_USEC_SESSNS is a table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to store Unit Section Session details — that is, the individual session instances that make up a unit section occurrence within an academic term. A unit section represents a specific delivery of a unit (course) offering, and a unit section occurrence represents a scheduled instance of that section. Sessions subdivide an occurrence into discrete meetings, each carrying its own name, description, timing, and location.

The table is documented as obsolete and is explicitly recorded as "Not implemented in this database" in the ETRM metadata. Accordingly, in Oracle EBS 12.1.1 and 12.2.2 environments that do not carry the relevant IGS modules or patches, this object may be absent from the physical schema entirely. Where it does exist, it functions as a child of the unit section occurrence and offering structures, preserving the granular scheduling detail for each session.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is characterized as satellite-leaning. This is a modeling suggestion rather than a product attribute: the table's identity is anchored to parent entities through its foreign keys, while its descriptive columns (session name, description, timing, location) represent the mutable, contextual payload typical of a satellite.

Key Information Stored

The documented physical schema for release 12.1.1 records twelve columns. The primary key is defined by the unique index IGS_AS_USEC_SESSNS_PK, comprising UOO_ID and SESSION_NAME. These two columns therefore serve as the composite business-key candidates, and together they establish uniqueness for each session record.

No separate surrogate single-column primary key is documented; the identifier of record is the composite of UOO_ID and SESSION_NAME.

Common Use Cases and Queries

The principal reporting use case is reconstructing the session timetable for a unit section offering. A typical query joins the session table to the offering option and occurrence parents and filters on the composite key:

  • Session listing by offering option: select SESSION_NAME, SESSION_DESCRIPTION, SESSION_START_DATE_TIME, SESSION_END_DATE_TIME, SESSION_LOCATION_DESC from IGS_AS_USEC_SESSNS where UOO_ID = :uooid, ordered by SESSION_START_DATE_TIME.
  • Occurrence-level scheduling detail: filter on UNIT_SECTION_OCCURRENCE_ID to retrieve all sessions belonging to a single occurrence.
  • Session attendance join: the dependent table IGS_AS_SUA_SES_ATTS references this table through the pair (UOO_ID, SESSION_NAME), allowing attendance records to be joined back to session scheduling and location data.
  • Location and room utilization reporting: aggregate SESSION_LOCATION_DESC across date ranges derived from the start and end date-time columns.

Because the object is documented as obsolete, any query development should first confirm the object's presence and current usage in the specific environment. Where the table exists but is not maintained, historical extracts may still support legacy reporting.

Related Objects

The foreign key structure identifies the objects that this table references and the objects that depend on it.

  • IGS_PS_UNIT_OFR_OPT_ALL — Referenced by IGS_AS_USEC_SESSNS.UOO_ID. The parent offering option entity, supplying the first component of the composite key.
  • IGS_PS_USEC_OCCURS_ALL — Referenced by IGS_AS_USEC_SESSNS.UNIT_SECTION_OCCURRENCE_ID. The parent unit section occurrence entity, providing the scheduled context for each session.
  • IGS_AS_SUA_SES_ATTS — References IGS_AS_USEC_SESSNS through (UOO_ID, SESSION_NAME). The dependent attendance/session attribute table.

These three relationships constitute the documented dependency graph for the object. Collectively they position IGS_AS_USEC_SESSNS between the scheduled unit section occurrence on the parent side and session attendance records on the child side, which is consistent with its heuristic classification as a satellite-style entity.