Search Results igsfv_sub_locations




Overview
Explore in AI Chat

Overview

IGSFV_SUB_LOCATIONS is a read-only Oracle EBS view owned by the APPS schema within the IGS (Student System) product family. It describes the relationship between locations in order to determine geographical equivalence between them, exposing a sub-location hierarchy alongside the descriptive attributes of both the parent location and the sub-location. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration surface over the location relationship data stored in the IGS_AD_LOCATION_REL table, joined to the location master in IGS_AD_LOCATION_ALL. Because the view is defined WITH READ ONLY, it is intended strictly for query and extraction purposes rather than for DML.

The user search term default_indicator maps directly to the view's DEFAULT_INDICATOR column, which is the aliased form of DFLT_IND from the underlying relationship table. This flag identifies the default sub-location associated with a given location, making it central to any query that needs to resolve which sub-location is treated as the primary or default geographic equivalent for a location.

Underlying Base Objects

The view is defined over three base tables in the APPS schema:

The relationship is therefore a self-referencing join of the location master through the relationship table, producing one row per location-to-sub-location pairing with descriptive text resolved for both ends of the relationship.

Key Columns

  • LOCATION_CODE — the parent location code (aliased from REL.LOCATION_CD).
  • SUB_LOCATION_CODE — the related sub-location code (aliased from REL.SUB_LOCATION_CD).
  • DEFAULT_INDICATOR — the default flag (aliased from REL.DFLT_IND) indicating whether the sub-location is the default for the parent location. This is the column referenced by the "default_indicator" search.
  • LOCATION_DESC — description of the parent location from LOC1.
  • SUB_LOCATION_DESC — description of the sub-location from LOC2.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from the relationship table.

Common Use Cases and Queries

Typical usage includes resolving the default sub-location for a location, validating geographic equivalence mappings, and extracting location hierarchies for reporting or downstream integration.

  • Retrieve all sub-locations for a specific parent location, including the default flag and descriptive text.
  • Identify the default sub-location only (WHERE DEFAULT_INDICATOR = 'Y').
  • Audit recently changed relationships using LAST_UPDATE_DATE.

Sample query:

SELECT location_code, sub_location_code, default_indicator, location_desc, sub_location_desc
FROM apps.igsfv_sub_locations
WHERE default_indicator = 'Y'
ORDER BY location_code;