Results for “hr_locations_lov_v”

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

Overview

HR_LOCATIONS_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined against the PER (Human Resources) product module. As its description states, it is the "HR Web Offers list of values view" — a purpose-built list-of-values (LOV) presentation layer that exposes a filtered and concatenated subset of the HR_LOCATIONS data for use by web-based HR self-service pages and related offers functionality. Rather than querying the wide HR_LOCATIONS table directly, these web components reference HR_LOCATIONS_LOV_V to obtain a compact, human-readable set of location choices limited to those relevant to HR usage.

The view is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Because it is a view and not a table, it carries no storage of its own; it derives all of its content at query time from the underlying HR_LOCATIONS object. This makes it a lightweight reporting and integration surface for location list-of-values scenarios within the E-Business Suite.

Underlying Base Objects

The documented metadata identifies two referenced base objects: HR_LOCATIONS (itself a view) and the HR_GENERAL package. The view text is a direct SELECT from HR_LOCATIONS, applying a single filtering predicate, LOCATION_USE = 'HR', which restricts the result set to locations flagged for HR use. HR_GENERAL is the Human Resources general-purpose package, and it is typically associated with such LOV views through the security and validation logic that governs which locations a given user is permitted to see in an HR context.

Because HR_LOCATIONS is itself a view over the underlying HR_LOCATIONS_ALL (and related) tables, HR_LOCATIONS_LOV_V represents the top layer of a small view stack. Consumers should therefore be aware that changes at the base location tables propagate upward through HR_LOCATIONS and into HR_LOCATIONS_LOV_V.

Key Columns

• LOCATION_ID — The primary key of the location record. This is the value ordinarily returned to a calling form or page once the user selects a list entry.
• LOCATION_CODE — The short, user-defined code identifying the location, suitable for display in a compact LOV.
• ADDRESS — A concatenated address string assembled from ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, TOWN_OR_CITY, REGION_1, REGION_2, REGION_3, POSTAL_CODE, and COUNTRY, joined with period ('.') delimiters. This yields a single display-friendly address field.
• DESCRIPTION — The descriptive text associated with the location.
• INACTIVE_DATE — The date on which the location became inactive. Consumers commonly filter on this column (for example, INACTIVE_DATE IS NULL) to suppress obsolete locations from an LOV.

Common Use Cases and Queries

The view is most commonly used to populate location LOVs in HR web offers and self-service flows, and to supply location descriptions in reporting and integration queries. A straightforward retrieval of all active HR locations follows.

• SELECT location_id, location_code, address, description FROM apps.hr_locations_lov_v WHERE inactive_date IS NULL ORDER BY location_code;
• Resolving a location to its display address: SELECT address FROM apps.hr_locations_lov_v WHERE location_id = :p_location_id;
• Building a validation query when loading or interfacing location data, restricting to active HR locations.

Because the concatenated ADDRESS uses '.' separators, downstream reporting may require string parsing if discrete address components are needed; in those cases querying HR_LOCATIONS directly is preferable.