Results for “location_desc”

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

Overview

The view IGSFV_BUILDINGS is a reporting and integration construct within the Oracle E-Business Suite (EBS) Student System module, identified by the product code IGS. As documented in the ETRM metadata, this entity "contains building information associated to a location." It exposes a denormalized projection of building and location data so that downstream consumers — reports, concurrent programs, interfaces, and third-party integrations — can resolve human-readable building codes and location descriptions without joining the underlying transactional tables directly.

The view is explicitly declared with a WITH READ ONLY clause, meaning it cannot be used as the target of DML. It is intended strictly for query access. The ETRM metadata further indicates that the object is flagged as "Obsolete" and is "Not implemented in this database" in the documented environment. Practitioners should therefore treat IGSFV_BUILDINGS as a legacy or dormant object that may exist only in certain historical EBS 12.1.1 / 12.2.2 installations where the Student System product was licensed and deployed, and should verify its presence in the data dictionary before relying on it.

Underlying Base Objects

The documented view text defines IGSFV_BUILDINGS over two base tables joined on the location code:

• IGS_AD_BUILDING_ALL — aliased as BLD; the primary source of building records.
• IGS_AD_LOCATION_ALL — aliased as LOC; the source of location descriptions.

The join predicate is BLD.LOCATION_CD = LOC.LOCATION_CD, linking each building to its parent location. The two _ALL tables follow the standard multi-org pattern in Oracle EBS, in which the base table holds the data and a corresponding _ALL object exposes it across operating units. Although the ETRM metadata lists no referenced base objects under "Documented view metadata," the view text itself establishes these two tables as the authoritative dependencies.

Key Columns

The view exposes ten columns. The most significant for the user's search term building_code is the first:

• BUILDING_CODE — derived from BLD.BUILDING_CD; the alphanumeric code uniquely identifying a building. This is the column most often used in filters and lookups.
• LOCATION_CODE — from BLD.LOCATION_CD; the location to which the building belongs.
• DESCRIPTION — the building description from BLD.DESCRIPTION.
• CLOSED_INDICATOR — from BLD.CLOSED_IND; denotes whether the building is administratively closed.
• LOCATION_DESC — from LOC.DESCRIPTION; the parent location's descriptive name, useful for display in reports.
• BUILDING_ID — the surrogate primary key from the building table, used for joins.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns recording who created and last modified the building row.

Common Use Cases and Queries

Typical scenarios include validating building codes during data conversion, listing active buildings per location, and enriching student location data for reporting. Because the view is read-only and, per the metadata, likely unimplemented in most environments, all queries should guard against its absence.

A representative lookup by building code:

• SELECT building_code, location_code, description, location_desc, closed_indicator FROM igsfv_buildings WHERE building_code = :p_building_code;
• SELECT building_code, description FROM igsfv_buildings WHERE closed_indicator = 'N' ORDER BY building_code;
• SELECT b.building_code, b.description, b.location_code, b.location_desc FROM igsfv_buildings b WHERE b.location_code = :p_location_code;

These queries return the resolved building and location information in a single pass, eliminating the need for callers to join IGS_AD_BUILDING_ALL and IGS_AD_LOCATION_ALL manually. Given the obsolete status noted in ETRM, developers are advised to confirm availability and consider the base tables as a fallback source.