Search Results igs_ad_building_pk

Overview

The IGS_AD_BUILDING_ALL table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module, which is designated as obsolete in the documented releases (12.1.1 and 12.2.2). It serves as the master repository for storing physical building information within an educational institution's operational framework. Its primary role is to provide referential integrity and descriptive data for buildings, which are typically associated with specific campus locations. This table enables the system to manage and track the usage of physical spaces for academic activities, such as scheduling classes and defining unit delivery locations. The presence of the "_ALL" suffix indicates it is a multi-organization enabled table, designed to support data partitioning by a governing "ORG_ID" column for implementations with multiple business units or institutions.

Key Information Stored

While the provided ETRM excerpt does not list all columns, the primary and foreign key relationships define the table's critical structural elements. The table is uniquely identified by a surrogate key, BUILDING_ID, which is the primary column for the IGS_AD_BUILDING_PK constraint. For business logic and validation, a unique key (IGS_AD_BUILDING_U2) is enforced on the combination of LOCATION_CD and BUILDING_CD. This ensures that a building code is unique within a given location. Essential data points stored would logically include the BUILDING_CD (a short code or abbreviation), a descriptive name, address details, and potentially attributes like floor count or facility type. The LOCATION_CD column is a foreign key linking the building to a specific campus or site defined in the IGS_AD_LOCATION_ALL table.

Common Use Cases and Queries

The primary use case for this table is supporting the scheduling and location management of academic offerings. Administrators can define where a class (unit section occurrence) is scheduled to be held, either as a dedicated, preferred, or general building assignment. A common reporting requirement would be to list all buildings available at a particular campus for scheduling purposes. A typical query would join the building table to its parent location table to produce a meaningful list.

Sample SQL Pattern:
SELECT b.building_cd, b.building_name, l.location_code, l.location_name
FROM igs_ad_building_all b,
igs_ad_location_all l
WHERE b.location_cd = l.location_cd
AND b.org_id = :p_org_id
AND l.location_code = :p_campus_code
ORDER BY b.building_cd;

Related Objects

The IGS_AD_BUILDING_ALL table maintains several documented foreign key relationships with other Student System tables, primarily within the Product Specialist (IGS_PS) sub-module for scheduling and unit management:

• Parent Table: IGS_AD_LOCATION_ALL, joined via IGS_AD_BUILDING_ALL.LOCATION_CD.
• Child Tables (referencing IGS_AD_BUILDING_ALL):
  • IGS_PS_USEC_OCCURS_ALL (Unit Section Occurrences): Referenced by four columns for scheduling: DEDICATED_BUILDING_CODE, PREFERRED_BUILDING_CODE, and BUILDING_CODE.
  • IGS_PS_US_UNSCHED_CL (Unscheduled Classes): Referenced by BUILDING_ID.
  • IGS_PS_UNIT_LOCATION (Unit Delivery Locations): Referenced by BUILDING_ID.

These relationships underscore the table's integral role in the physical resource allocation and scheduling processes of the Student System.