Results for “igs_ad_building_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_BUILDING_ALL is a foundational reference table within the Oracle E-Business Suite Student System (IGS) module, which is documented as obsolete in ETRM metadata for releases 12.1.1 and 12.2.2. The table stores building information used throughout the institution's physical location hierarchy. It acts as the parent for rooms, unit locations, scheduled and unscheduled class occurrences, and scheduling instances, making it a central anchor for any data model concerned with where academic activity physically takes place.

From a Data Vault modeling perspective, the metadata's heuristic classification of this object is hub-leaning. The stable, unique business concept here is the building itself, identified by BUILDING_ID and qualified by LOCATION_CD and BUILDING_CD, which supports treating the table as a hub with attributes that could be modeled as satellite data.

The table is owned by the IGS schema and contains eleven documented columns in the 12.1.1 physical schema. It is important to note that the metadata records this object as "Not implemented in this database," meaning availability depends on whether the Student System module and its physical location tracking components are deployed.

Key Information Stored

The most significant columns documented for IGS_AD_BUILDING_ALL are the following:

• BUILDING_ID — Surrogate primary key and the single-column unique index IGS_AD_BUILDING_ALL_PK. This is the internal identifier referenced by dependent foreign keys.
• BUILDING_CD — Business-facing building code; part of the composite unique index IGS_AD_BUILDING_U2 when combined with LOCATION_CD.
• LOCATION_CD — The location to which the building belongs; the second member of IGS_AD_BUILDING_U2 and a foreign key to IGS_AD_LOCATION_ALL.
• DESCRIPTION — Free-text name or descriptive label for the building, suitable for reporting.
• CLOSED_IND — Flag indicating whether the building is closed or inactive, used to filter valid buildings in operational queries.
• ORG_ID — Operating unit / organization context for multi-org aware access.
• CREATED_BY, CREATION_DATE — Standard audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent change and session.

The distinction between the surrogate key (BUILDING_ID) and the business-key candidate (LOCATION_CD plus BUILDING_CD) is important: integrations and lookups typically resolve a building by code, while referential joins should use BUILDING_ID for stability.

Common Use Cases and Queries

The most common use case is resolving room and scheduling records back to the building in which they occur. For example, listing active buildings in a location:

• SELECT BUILDING_ID, BUILDING_CD, DESCRIPTION FROM IGS_AD_BUILDING_ALL WHERE LOCATION_CD = :location AND NVL(CLOSED_IND,'N') = 'N';
• Joining buildings to rooms: SELECT b.BUILDING_CD, r.ROOM_CD FROM IGS_AD_BUILDING_ALL b, IGS_AD_ROOM_ALL r WHERE r.BUILDING_ID = b.BUILDING_ID;
• Reporting scheduled activity per building: SELECT b.BUILDING_CD, COUNT(*) FROM IGS_AD_BUILDING_ALL b, IGS_PS_SCH_INT_ALL s WHERE s.BUILDING_ID = b.BUILDING_ID GROUP BY b.BUILDING_CD;
• Cross-referencing unscheduled classes: join IGS_PS_US_UNSCHED_CL to IGS_AD_BUILDING_ALL on BUILDING_ID.

Typical reporting scenarios include facility utilization analysis, class-scheduling location reports, and validation feeds that map legacy building codes to the canonical BUILDING_ID.

Related Objects

Several dependent tables reference IGS_AD_BUILDING_ALL, and it in turn references location data. The most significant related objects are:

• IGS_AD_LOCATION_ALL — Parent location; joined via IGS_AD_BUILDING_ALL.LOCATION_CD = IGS_AD_LOCATION_ALL.LOCATION_CD.
• IGS_AD_ROOM_ALL — Rooms belonging to a building; joined via BUILDING_ID.
• IGS_PS_UNIT_LOCATION — Delivered unit locations; joined via BUILDING_ID.
• IGS_PS_SCH_INT_ALL — Scheduling instances; joined via BUILDING_ID.
• IGS_PS_US_UNSCHED_CL — Unscheduled classes; joined via BUILDING_ID.
• IGS_PS_USEC_OCCURS_ALL — Occurrence usage; referenced through DEDICATED_BUILDING_CODE, PREFERRED_BUILDING_CODE, and BUILDING_CODE.

Because the module is obsolete, DBA teams should confirm physical implementation status before relying on these relationships in a given environment.