Search Results unit_sec_cross_unit_sec_id




Overview
Explore in AI Chat

Overview

IGS.IGS_PS_USEC_X_USEC is a transactional table in the Oracle E-Business Suite Student System (IGS) schema that captures cross-listed unit sections. In academic terms, a cross-listed section is a single teaching event offered under more than one unit (course) code; this table records the parent-child relationship between the underlying unit offering option records that constitute such a relationship. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting a moderately update-tolerant transactional storage profile typical of IGS setup and scheduling data in both 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined relationship structure suggests classifying this object as a link. It carries no descriptive business attributes beyond identifiers and standard Who columns, and it resolves a many-to-many style association between two unit offering options. Its business keys are enforced by two unique indexes, and its foreign keys point outward to the unit offering option entity. This makes it a connective, relationship-bearing object rather than a hub of descriptive state.

Key Information Stored

The table contains eight documented columns, of which three are meaningful business columns and the remainder are standard audit columns.

Common Use Cases and Queries

The most frequent operational requirement is resolving which unit offering options are cross-listed with a given section, and reporting enrollments or scheduled components across the pair. A typical lookup by surrogate key is:

  • SELECT parent_uoo_id, child_uoo_id FROM igs.igs_ps_usec_x_usec WHERE unit_sec_cross_unit_sec_id = :p_id;
  • Reverse lookup from business key: SELECT unit_sec_cross_unit_sec_id FROM igs.igs_ps_usec_x_usec WHERE parent_uoo_id = :p AND child_uoo_id = :c;
  • Joining both sides back to the offering option table to obtain unit codes and versions, using two aliases of IGS_PS_UNIT_OFR_OPT_ALL — one on PARENT_UOO_ID and one on CHILD_UOO_ID.
  • Reporting cross-listed sections for a teaching period by joining through the scheduling integration tables that carry UNIT_SEC_CROSS_UNIT_SEC_ID.

Because the table is link-like and lightly attributed, queries are almost always join-driven; direct extracts are rarely useful without resolving the UOO identifiers to human-readable unit and version data.

Related Objects

The following objects are the most significant dependencies per the documented relationship data:

  • IGS.IGS_PS_UNIT_OFR_OPT_ALL — referenced twice by foreign keys: PARENT_UOO_ID and CHILD_UOO_ID. This is the primary join target for both endpoints of the relationship.
  • IGS.IGS_PS_SCH_INT_ALL — references this table via UNIT_SEC_CROSS_UNIT_SEC_ID, linking scheduling integration records to cross-listed sections.
  • IGS.IGS_PS_SCH_X_USEC_INT_ALL — also references this table via UNIT_SEC_CROSS_UNIT_SEC_ID, providing the cross-listed scheduling integration interface.
  • APPS.IGS_PS_USEC_X_USEC — the APPS-layer synonym or view exposing the same structure for application-level querying.
  • The two unique indexes, IGS_PS_USEC_X_USEC_U1 and IGS_PS_USEC_X_USEC_U2, are the principal access paths for both key-based and parent/child-based retrieval.

No further outbound references are documented; the table does not reference any database object other than the unit offering option entity through its child and parent identifiers.