Search Results igs_ps_own




Overview
Explore in AI Chat

Overview

The IGS_PS_OWN table is a core data entity within the Oracle E-Business Suite's now-obsolete Student System (IGS). It formally models the concept of program ownership, defining the specific organizational units responsible for administering an academic program and quantifying their respective ownership stakes. Its primary role is to establish and maintain a many-to-many relationship between academic programs (courses) and the organizational units that govern them, enabling complex administrative structures where a single program may be jointly owned and managed by multiple departments or schools. This data is critical for accurate reporting, resource allocation, and responsibility assignment within the student lifecycle management framework of the legacy system.

Key Information Stored

The table's structure is designed to uniquely identify a program, an organizational unit, and the specific ownership relationship between them. The primary key is a composite of four columns, ensuring a unique record for each ownership assignment. The core columns include:

  • COURSE_CD and VERSION_NUMBER: Together, these fields uniquely identify the academic program (course version) being owned, forming a foreign key reference to the IGS_PS_VER_ALL table.
  • ORG_UNIT_CD and OU_START_DT: These columns uniquely identify the organizational unit that holds an ownership stake in the program. The inclusion of a start date suggests the organizational unit's effective dating is part of its key.
  • A critical piece of data implied by the table's description is a percentage ownership column (not explicitly named in the provided metadata), which would store the proportional ownership division among multiple owning units for a single program.

Common Use Cases and Queries

This table supports several key administrative and reporting functions. A common operational use case is determining all responsible organizational units for a given program to route approvals or financial transactions. For reporting, it enables the analysis of program portfolios by department. Sample SQL patterns include retrieving the full ownership breakdown for a specific program or listing all programs owned by a particular organizational unit. An example query to find all owners of a program would be:

SELECT org_unit_cd, ownership_percentage FROM igs_ps_own WHERE course_cd = :p_course AND version_number = :p_version;

Conversely, to audit a department's responsibilities, one might execute:
SELECT course_cd, version_number FROM igs_ps_own WHERE org_unit_cd = :p_ou_cd;

Related Objects

The IGS_PS_OWN table has a defined foreign key relationship with the primary program definition table, establishing its dependency. The documented relationships are:

  • Foreign Key to IGS_PS_VER_ALL: The table IGS_PS_OWN references the IGS_PS_VER_ALL table. The join is performed on the columns IGS_PS_OWN.COURSE_CD and IGS_PS_OWN.VERSION_NUMBER, which correspond to the primary key of IGS_PS_VER_ALL. This ensures that every ownership record is linked to a valid, existing academic program version.

It is important to note the metadata explicitly states this table is "Not implemented in this database," indicating it may exist in the data model but not be populated or actively used in all deployments of the obsolete Student System.