Search Results hrfv_us_locations




Overview
Explore in AI Chat

Overview

HRFV_US_LOCATIONS is a business view template owned by the APPS schema in Oracle E-Business Suite, defined under the PER (Human Resources) product family. As the description states, it is a "business view template from which the flexfield view is generated." This means the view is not a transactional entity but a reporting and integration construct: it flattens the US-specific location flexfield structure into named, human-readable columns so that downstream reports, interfaces, and external systems can consume location data without resolving flexfield segment semantics manually. The view supports the US (United States) location flexfield context, which is one of several country-specific location key flexfield structures in Oracle HRMS. In both 12.1.1 and 12.2.2, the object is delivered as a VALID view in the APPS schema, and its structure is stable across these releases, making it a reliable source for custom reporting and outbound integration in US-based or multi-national implementations.

Underlying Base Objects

The view is defined over a documented set of base objects: HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL (synonyms for the business group and inventory organization names), HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL (the core location and translated location tables), and PER_PEOPLE_X (used for the designated receiver's name). It also references the HR_BIS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. HR_BIS.BIS_DECODE_LOOKUP is invoked inline to translate the REGION_2 code into the STATE_NAME via the US_STATE lookup, while HR_SECURITY and HR_GENERAL are typically referenced in the view's WHERE clause to enforce row-level security and language handling. The joins link HR_LOCATIONS_ALL to its _TL translation table on LOCATION_ID with LANGUAGE = USERENV('LANG'), and outer-join to the business group organization unit tables so that locations without a business group still appear.

Key Columns

The view exposes a comprehensive set of descriptive and coded columns. BUSINESS_GROUP_NAME and BUSINESS_GROUP_ID identify the owning business group; LOCATION_NAME and LOCATION_DESCRIPTION carry the short and long location labels. Address attributes include ADDRESS_LINE_1 through ADDRESS_LINE_3, CITY, COUNTY, STATE_NAME (decoded) and STATE_CODE, COUNTRY, and ZIP_CODE. Contact fields include TELEPHONE_NUMBER_1 to _3. Flag columns BILL_TO_SITE_FLAG, INTERNAL_SITE_FLAG, RECEIVING_SITE_FLAG, OFFICE_SITE_FLAG, and SHIP_TO_LOCATION_FLAG are exposed as decoded YES/NO meanings sourced from HR_LOOKUPS. Additional columns include DEFAULT_TAX_CODE, SHIP_TO_LOCATION (with SHIP_TO_LOCATION_ID), DESIGNATED_RECEIVER (with DESIGNATED_RECEIVER_ID), INVENTORY_ORGANIZATION (with INVENTORY_ORGANIZATION_ID), ADDRESS_STYLE, INACTIVE_DATE, and LOCATION_ID as the primary key. The two special tokens '._LA' and '._DF' are flexfield-view placeholders used by the view generator.

Common Use Cases and Queries

Typical uses include shipping, receiving, and tax setup reporting, location-based interfaces to third-party logistics or EDI systems, and validation screens. A representative query is:

  • SELECT LOCATION_ID, BUSINESS_GROUP_NAME, LOCATION_NAME, CITY, STATE_CODE, COUNTRY, ZIP_CODE, SHIP_TO_LOCATION_FLAG FROM APPS.HRFV_US_LOCATIONS WHERE COUNTRY = 'US' AND INACTIVE_DATE IS NULL;

  • SELECT INVENTORY_ORGANIZATION, LOCATION_NAME, DESIGNATED_RECEIVER FROM APPS.HRFV_US_LOCATIONS WHERE RECEIVING_SITE_FLAG = 'Yes';

  • SELECT a.LOCATION_NAME, a.DEFAULT_TAX_CODE FROM APPS.HRFV_US_LOCATIONS a WHERE a.BILL_TO_SITE_FLAG = 'Yes' ORDER BY a.LOCATION_NAME;

Because row-level security is generally enforced through the HR_SECURITY package referenced in the defining query, results are filtered automatically according to the querying user's HR security profile, which should be considered when granting direct SELECT privileges to the view.