Results for “loc_description”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_AD_LOC_BLDG_V is a denormalized reporting view owned by the APPS schema within the IGS — Student System product family. Its documented purpose is to "show different buildings and their locations," combining building-level attributes from the building entity with the descriptive and status attributes of the location to which each building belongs. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenient single-row-per-building projection that exposes both building and location descriptive data without requiring the caller to join the two base entities manually. Such views are typically consumed by concurrent programs, Oracle Reports, OBIEE/XML Publisher data templates, and ad hoc SQL used by institutional reporting teams. Because the view carries the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), it can also be used to drive incremental or delta-based extracts. The view is documented as VALID in the ETRM metadata, and the primary search term associated with this object is "loc_description," confirming that the location description column is the attribute users most frequently seek when querying this view.

Underlying Base Objects

The view is defined over exactly two base tables:

The join is an equality on LOCATION_CD: WHERE BG.LOCATION_CD = LOC.LOCATION_CD. The view is therefore an inner join, meaning a building rows whose LOCATION_CD has no matching location row will be excluded from the result set. The ROWID of the building row is exposed as ROW_ID to permit row-level identification and locking behavior consistent with building-level DML. The ETRM metadata for 12.2.2 records no additional documented base objects beyond these two tables.

Key Columns

  • ROW_ID — ROWID of the IGS_AD_BUILDING row; useful for row-level identification.
  • BUILDING_ID — Primary key of the building entity.
  • BUILDING_CD — User-facing building code.
  • BLDG_DESCRIPTION — Descriptive name of the building (aliased from BG.DESCRIPTION and renamed to avoid collision with the location description).
  • BLDG_CLOSED_IND — Indicates whether the building is closed/inactive.
  • LOCATION_CD — The join key linking building to location.
  • LOC_DESCRIPTION — The location description; this is the column users search for when looking up "loc_description."
  • LOC_CLOSED_IND — Indicates whether the associated location is closed/inactive.
  • WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN carried from the building row.

Common Use Cases and Queries

Typical uses include building/location listings for campus planning, validation of active buildings assigned to open locations, and descriptive lookups for integrations that require both codes and descriptions in a single pass.

List all active buildings with their locations:

  • SELECT building_cd, bldg_description, location_cd, loc_description FROM apps.igs_ad_loc_bldg_v WHERE NVL(bldg_closed_ind,'N') = 'N' AND NVL(loc_closed_ind,'N') = 'N' ORDER BY location_cd, building_cd;

Locate a building by its location description:

  • SELECT building_cd, bldg_description, loc_description FROM apps.igs_ad_loc_bldg_v WHERE UPPER(loc_description) LIKE UPPER('%&loc_desc%');

Count buildings per location:

  • SELECT location_cd, loc_description, COUNT(*) bldg_count FROM apps.igs_ad_loc_bldg_v GROUP BY location_cd, loc_description ORDER BY bldg_count DESC;

Because the view is an inner join, building rows with a null or unmatched LOCATION_CD will not appear; reporting requirements that must include unassigned buildings should query IGS_AD_BUILDING directly or use an outer join complement. Access is granted through the APPS schema, so queries should reference APPS.IGS_AD_LOC_BLDG_V or rely on a synonym in the calling schema.