Search Results igs_ps_usec_x_usec_v




Overview
Explore in AI Chat

Overview

IGS_PS_USEC_X_USEC_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered with the IGS (Student System) product family. It exposes cross-unit (parent-child) relationships that are configured between scheduled unit offerings in an institution's curriculum structure. Specifically, the view flattens the hierarchical membership stored in the cross-unit listed group tables so that a report or integration can join a parent unit offering directly to each of its child unit offerings in a single row.

The view is read-only by convention and is intended for reporting, data extraction, and interface development rather than for transactional maintenance. Because it is defined in the APPS schema against the base Student System tables, it is accessible to any responsibility that has been granted the standard IGS read privileges. The view carries a CHILD_ALTERNATE_CODE column, which is frequently referenced in reporting requirements that need the institution-defined alternate identifier for the child unit occurrence rather than the internal unit code.

Underlying Base Objects

The view is defined over seven base objects, joined on their natural keys:

The metadata does not document these objects as separately registered dependencies, but the view text shows them explicitly.

Key Columns

Common Use Cases and Queries

Typical uses include validating cross-unit configuration before teaching period rollover, reporting which units are delivered together as cross-unit pairs, and feeding downstream scheduling or room-booking extracts.

SELECT child_unit_cd,
       child_alternate_code,
       child_title,
       start_dt,
       end_dt,
       child_location_cd
FROM   apps.igs_ps_usec_x_usec_v
WHERE  child_cal_type = :p_cal_type
AND    child_ci_sequence_number = :p_seq
ORDER  BY child_unit_cd;

A second common pattern lists all children of a known parent offering:

SELECT child_uoo_id,
       child_unit_cd,
       child_alternate_code
FROM   apps.igs_ps_usec_x_usec_v
WHERE  parent_uoo_id = :p_uoo_id;

Because the view performs no filtering beyond the PARENT flag, additional WHERE predicates on calendar type, location, or dates are normally required to constrain result sets in production reporting.