Search Results igs_ps_usec_x_usec_pk

Overview

The IGS_PS_USEC_X_USEC table is a core Student System (IGS) entity in Oracle E-Business Suite 12.1.1 and 12.2.2, designed to capture the Cross Listed Unit Sections. In the academic structure of Oracle Student System, a unit offering option (unit section) can be cross listed against one or more other offering options, allowing a single teaching activity to be shared across multiple programs, plans, or organisational units while remaining a distinct academic record. This table stores those parent-to-child cross-listing relationships.

The table resides in the IGS schema and holds eight documented columns at the 12.1.1 physical level. Based on the documented foreign key structure, in which the table's only substantive attributes are relationships to IGS_PS_UNIT_OFR_OPT_ALL, the data vault classification is a link (associative) table. This is a heuristic modelling suggestion: the table resolves a many-to-many association between a parent unit section and a child unit section, and it carries no independent descriptive satellite context of its own beyond standard audit columns. Administrators and developers should treat it as the authoritative cross-reference record for cross-listed unit sections.

Key Information Stored

The documented column set comprises eight columns, of which the following are material to the academic relationship:

• UNIT_SEC_CROSS_UNIT_SEC_ID — the surrogate primary key, defined by constraint IGS_PS_USEC_X_USEC_PK. It uniquely identifies each cross-listing record and is referenced by downstream integration and scheduling tables.
• PARENT_UOO_ID — the parent unit offering option identifier. Together with CHILD_UOO_ID it forms the unique business-key index IGS_PS_USEC_X_USEC_U2, preventing duplicate cross-listing pairs.
• CHILD_UOO_ID — the child unit offering option identifier. It is the counterpart of the parent in the cross-listed relationship.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns that record who created and last amended the record and when.

A distinct unique index, IGS_PS_USEC_X_USEC_U1, is defined on UNIT_SEC_CROSS_UNIT_SEC_ID, reinforcing the surrogate key. The business-key candidate is therefore the U2 index on the PARENT_UOO_ID and CHILD_UOO_ID pair. Both identifiers resolve to IGS_PS_UNIT_OFR_OPT_ALL, which makes the table a pure relationship link between unit sections rather than a descriptive entity.

Common Use Cases and Queries

Typical usage includes reporting on cross-listed teaching, validating that a unit section is not cross-listed to itself, and providing the link record consumed by scheduling and enrolment processes. A representative query to retrieve cross-listing pairs is:

• SELECT x.unit_sec_cross_unit_sec_id, x.parent_uoo_id, x.child_uoo_id FROM igs_ps_usec_x_usec x WHERE x.parent_uoo_id = :parent_id;
• Join to the unit offering option table to resolve descriptions: SELECT p.uoo_id parent, c.uoo_id child FROM igs_ps_usec_x_usec x, igs_ps_unit_ofr_opt_all p, igs_ps_unit_ofr_opt_all c WHERE x.parent_uoo_id = p.uoo_id AND x.child_uoo_id = c.uoo_id;
• Audit queries filtering on last_update_date or created_by to identify recently created cross-listings.

Reporting scenarios include timetable clash analysis, cross-listed census extracts, and reconciliation between the base cross-listing record and the scheduling integration tables that reference it.

Related Objects

The most significant related objects, drawn from the documented constraints, are:

• IGS_PS_UNIT_OFR_OPT_ALL — the master unit offering option table, referenced twice: PARENT_UOO_ID and CHILD_UOO_ID both point to it, providing the parent and child section descriptions.
• IGS_PS_SCH_INT_ALL — a scheduling integration table whose UNIT_SEC_CROSS_UNIT_SEC_ID column references this table's primary key.
• IGS_PS_SCH_X_USEC_INT_ALL — a second scheduling cross-use integration table that likewise references UNIT_SEC_CROSS_UNIT_SEC_ID.
• IGS_PS_USEC_X_USEC_PK / _U1 / _U2 — the primary key and unique indexes that enforce record identity and prevent duplicate parent-child pairs.

Because both the parent and child references terminate at IGS_PS_UNIT_OFR_OPT_ALL, any change to a unit offering option's definition can affect the cross-listing records that point to it, and referential integrity should be considered when purging or reorganising offering options.