Search Results hr_locations_all_v




Overview
Explore in AI Chat

Overview

HR_LOCATIONS_ALL_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. It provides a reporting and integration layer over the location definition data maintained in Oracle HRMS. In EBS 12.1.1 and 12.2.2, locations represent physical sites — offices, plants, warehouses, ship-to and bill-to addresses — that are associated with organizations, business groups, and inventory or receiving functions. The view exposes the operational and descriptive attributes of these locations in a single, denormalized result set, allowing concurrent programs, Oracle Reports, OAF pages, and third-party integrations to retrieve location information without joining the underlying tables manually.

The object is listed as VALID in the ETRM metadata for both releases, confirming that no compilation or dependency errors affect its availability at the time of documentation. Because it is a view rather than a table, it carries no storage of its own; all data is read from the base tables at query time.

Underlying Base Objects

The documented view text defines HR_LOCATIONS_ALL_V as a join between two objects: HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL. The former holds the operational location record — addresses, site flags, tax name, inventory organization references, and the DFF/global DFF attribute columns — while the latter is the translation table, supplying the LOCATION_CODE and DESCRIPTION values in the session's language. The view therefore resolves the base location row plus its translated descriptive text in one pass.

The documented base objects also list HR_GENERAL (PACKAGE), HR_LOCATIONS_ALL (SYNONYM), and HR_LOCATIONS_ALL_TL (SYNONYM). The two tables are referenced through public synonyms, which is standard for APPS-owned views. HR_GENERAL is a PL/SQL package that supplies HRMS security and utility logic; the view's WHERE clause in the full definition typically restricts rows using HR_GENERAL security predicates (for example, business group and security profile checks) so that only locations the querying user is authorized to see are returned.

Key Columns

Note that the constant literal 'HR' is projected as a column, distinguishing HR-sourced locations from other location sources in union-style consumers.

Common Use Cases and Queries

Typical scenarios include listing active locations for an organization, validating ship-to or bill-to sites during order or receipt processing, extracting address data for interfaces, and driving HRMS reports and OAF location LOVs. The DISTINCT-free structure supports straightforward filtering by business group and active status.

Example — active locations for a business group:

SELECT location_id, location_code, description,
       town_or_city, country, postal_code
FROM   apps.hr_locations_all_v
WHERE  business_group_id = :p_business_group_id
AND    inactive_date IS NULL
ORDER  BY location_code;

Example — retrieving ship-to sites for an integration extract:

SELECT location_id, location_code, description,
       ship_to_location_id, address_line_1, town_or_city
FROM   apps.hr_locations_all_v
WHERE  ship_to_site_flag = 'Y'
AND    inactive_date IS NULL;

Because the view applies HRMS security through HR_GENERAL, queries executed under a restricted security profile return only the locations that profile permits, which makes the view suitable for self-service and delegated reporting without additional row-level filtering by the developer.