Search Results hr_locations_v




Overview
Explore in AI Chat

Overview

HR_LOCATIONS_V is an APPS-owned database view in the Oracle E-Business Suite PER (Human Resources) product module. The ETRM documentation describes its purpose succinctly: "Used to support user interface." In practice, HR_LOCATIONS_V is the presentation-layer view through which Oracle HRMS forms, list-of-values windows, and self-service pages render location records to end users. It is not a transactional table, and no data is stored in it; every column resolves at query time against the underlying HR location tables and lookup definitions.

Because it exposes decoded, user-facing values — most importantly the meaning strings for the ship-to, bill-to, office, receiving, and internal site flags — the view is widely reused as a reporting and integration surface. Developers searching on "ship_to_site" typically arrive here because HR_LOCATIONS_V carries a column of exactly that name, derived from HR_LOOKUPS rather than stored as free text. This makes the view the natural query target for address validation, ship-to site resolution, and location-driven interfaces across Order Management, Purchasing, and Receiving.

Underlying Base Objects

The documented metadata for release 12.2.2 lists the following referenced base objects:

The view text shows aliased joins: HR_LOCATIONS_ALL as L, HR_LOCATIONS_ALL_TL as TL, HR_LOOKUPS as HR1 through HR5 for the five site-flag meanings, a second reference to the location table (L2TL) to resolve SHIP_TO_LOCATION into a location code, and FND_DESCR_FLEX_CONTEXTS_TL as FND.

Key Columns

Common Use Cases and Queries

The most common requirement is to enumerate locations flagged as valid ship-to sites, often filtered to active records and joined to a ship-to location code. HR_LOCATIONS_V supports this directly, without requiring the caller to decode lookup values.

Sample query — active ship-to sites:

  • SELECT location_id, location_code, ship_to_site, ship_to_location, town_or_city, country FROM apps.hr_locations_v WHERE ship_to_site_flag = 'Y' AND (inactive_date IS NULL OR inactive_date > SYSDATE) ORDER BY location_code;

Sample query — all ship-capable sites with their decoded meanings for reporting:

  • SELECT location_id, location_code, ship_to_location, ship_to_site, bill_to_site, receiving_site, office_site FROM apps.hr_locations_v WHERE ship_to_site = 'Yes';

Typical integration scenarios include resolving a ship-to site for a sales order or purchasing document, populating address LOVs in custom OAF or Forms pages, validating that a location is enabled for receiving before a receipt is processed, and extracting location master data into a data warehouse. Because the view applies HRMS security and joins several base objects, queries should filter on LOCATION_ID or a small set of codes wherever possible, and callers should expect read-only access only. The view should never be used for DML; all maintenance of locations must be performed through HR_API and the standard HRMS forms.