Results for “activity_type_id”

50+ results




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

Overview

IGS_PS_USEC_ACT_TYPE is a reference (lookup) table within the Oracle E-Business Suite Student System product family, owned by the IGS schema. In the ETRM 12.1.1 and 12.2.2 documentation, it is described as holding information about Unit Section Activity Types — the classification values that describe the nature of an activity scheduled against a unit section (for example, lecture, laboratory, tutorial, or seminar delivery formats). The table therefore serves as the master definition list that downstream scheduling and enrolment transactions reference rather than duplicate.

The object is flagged as obsolete and, critically, is documented in ETRM with the note "Not implemented in this database." This means the table may exist only in legacy or partially provisioned environments and should not be assumed present in a standard 12.1.1 or 12.2.2 installation. Practitioners should confirm existence in ALL_TABLES before writing dependent code.

From a Data Vault modeling perspective, the mined relationship data classifies this object as hub-leaning. That is a heuristic suggestion: ACTIVITY_TYPE_ID behaves as a durable business key around which descriptive attributes (code, description, closed indicator, audit columns) are attached. In a Data Vault design this would typically be modelled as a hub with an adjacent satellite, rather than as a link, because no many-to-many resolution is implied by the current foreign key footprint.

Key Information Stored

The documented physical schema comprises nine columns. The most significant are:

The presence of two distinct unique constraints — one on the surrogate key and one on the code — is the defining structural characteristic: joins may legitimately be written against either identifier, but ACTIVITY_TYPE_ID is the referential anchor used by foreign keys.

Common Use Cases and Queries

Typical usage centres on decoding activity type identifiers into readable labels for scheduling reports, validating incoming interface data against the code list, and identifying which activity types remain selectable. A representative join pattern follows:

  • SELECT a.ACTIVITY_TYPE_CODE, a.ACTIVITY_TYPE_DESCRIPTION FROM igs_ps_usec_act_type a WHERE NVL(a.closed_ind,'N') = 'N'; — populates a list of values with only active types.
  • SELECT u.ACTIVITY_TYPE_ID, a.ACTIVITY_TYPE_DESCRIPTION FROM igs_ps_us_unsched_cl u, igs_ps_usec_act_type a WHERE u.ACTIVITY_TYPE_ID = a.ACTIVITY_TYPE_ID; — resolves unscheduled class records to their activity type descriptions.
  • Aggregate reporting on unscheduled class volumes grouped by activity type, useful for capacity and timetabling analysis.
  • Data migration and interface validation, matching inbound ACTIVITY_TYPE_CODE values against the unique business key before load.

Because the object is documented as not implemented in the reference database, every query should be guarded with an existence check or conditional compilation in PL/SQL.

Related Objects

The documented foreign key metadata identifies a single dependent object:

  • IGS_PS_US_UNSCHED_CL — references this table through the column ACTIVITY_TYPE_ID, indicating that unscheduled class records are categorised by activity type.

Beyond the supplied relationship data, related IGS Student System objects that conventionally participate in this functional area include unit section scheduling entities and their associated activity or delivery-mode reference tables. These should be verified in the target instance before reliance, given the obsolete status of IGS_PS_USEC_ACT_TYPE. No public API or view is documented in the ETRM metadata for this object.